Maintain control of your Microsoft 365 data
Post Reply
HangTen
Service Provider
Posts: 34
Liked: 1 time
Joined: Jan 21, 2021 3:17 pm
Full Name: Hin Tang
Contact:

Possible replacement for soon to be deprecated PS command

Post by HangTen »

We are in the process of retiring some S3 compatible storage and when we looked at the storage consumed on the array and the storage reported consumed by VB365 (the storage is used solely for VB365 backups), we noticed a big discrepancy. In the console and when running Get-VBORepository in PS, we don't see any repositories starting with "n" but when we run:

Code: Select all

Get-VBOObjectStorageRepository -Name n* | Select Name
I can see the warning below and results.

Code: Select all

WARNING: The Get-VBOObjectStorageRepository cmdlet became deprecated. Use the Get-VBORepository cmdlet instead. The cmdlet may not be supported in future versions of Veeam Backup for Microsoft 365.
Without this tool, there would have been no way to know these orphaned folders were there taking up space. Is there a plan to have this functionality in another command or to allow these orphaned repositories to be accessible through the console (or both)?

Thanks,

Hin
Mildur
Product Manager
Posts: 10734
Liked: 2918 times
Joined: May 13, 2017 4:51 pm
Full Name: Fabian K.
Location: Switzerland
Contact:

Re: Possible replacement for soon to be deprecated PS command

Post by Mildur »

Hi Hin,

To be honest, this sounds more like a bug that shouldn't occur at all.
A customers shouldn't have to run a cmdlet for regular manual scans; it should "just work" and everything should be cleaned up automatically after repository removal.

Have you contacted our customer support team about your findings? If so, could you please share the case number?

Best,
Fabian
Product Management Analyst @ Veeam Software
Polina
Veeam Software
Posts: 3585
Liked: 855 times
Joined: Oct 21, 2011 11:22 am
Full Name: Polina Vasileva
Contact:

Re: Possible replacement for soon to be deprecated PS command

Post by Polina »

Hi Hin,

Such orphaned folders can be leftovers from the time of v7 and earlier versions, when to create a functional object storage backup repository, you had to manually add cloud and database parts and link them to each other. And it was possible to remove a 'database' part while its cloud part remained orphaned and unused. In v8, those unusable leftovers are intentionally hidden from the UI, and are only available via those old PowerShell cmdlets so that you could identify them and clean them up (or reuse for new object storage repositories if needed).

Makes sense?
Post Reply

Who is online

Users browsing this forum: Google [Bot] and 6 guests