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:
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)?
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?
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).