Skip to main content

Is there a way to get better reporting for usage on hardened repositories? I recently had a Wasabi issue after upgrading to 12 and our console was showing 29.7tb’s of usage which is right under our 30tb bucket. Actual bucket size was 128tb which lead to additional billing.

Have you looked in to Veeam ONE as a possible solution and test the reporting available?  The reports within the Veeam console are minimal unless you want to dive in the PowerShell or use the API.

https://helpcenter.veeam.com/docs/one/deployment/about.html?ver=120

 


Hi @Edward, several tools are capable of providing insights into your storage performance. Like Chris suggested above, I would use VeeamOne also. But you can also use PRTG or any other tool of your choice. Here is a similar question raised: 

 


Wasabi is not a hardened repository. Hardened repositories run on a linux machine and are block based backup storages, while Wasabi is an object storage based backup storage.

If no other backup server is writing to the same bucket, it may be a know issues with obsolete deletion markers or orphaned objects.

 

We can check what‘s going on and provide a solution if you open a case with our customer support.

https://www.veeam.com/kb1771

 

Best,

Fabian


@Mildur I guess I should of said immutable on Wasabi, but even our three actual hardened repositories do not report correctly in the console. i.e. first one shows capacity 41.5 tb’s, free 31.2tb’s, used 21.5tb’s. Second one capacity 41.5tb’s, free 31.3tb’s, used 28.1tb’s, and our third is the best math of all. Capacity 41.5tb’s free 24.1tb’s, used 44.3tb’s. Do you see what I am getting at? I have had tickets open in the past and they said it was how it was calculated on the backend. I guess I need to open a separate ticket now on the Veeam One as it will not connect on the same VM where it did in the past

 


Hardened repositories are using XFS as the filesystem.

XFS provides FastClone support with the help of the reflink feature. We reference existing blocks instead of duplicating them when you synthesize a full backup file. This makes synthetic full backup file almost spaceless. Less physical storage is used, but Veeam still shows the file size of all full backup files and immutable files. It‘s because the XFS filesystem on top of the volume reports us the file size of the backup files and ignores the space savings by the XFS filesystem. 

It is a known request that our customers want to see the real physical storage usage with space savings in the Veeam console. We are looking i to this request but there is no ETA when we can deliver this information.

 

Best,

Fabian


If you are a service provider, you may check out this topic in our RnD forum:

https://forums.veeam.com/post490518.html?hilit=Refs#p490518
 

Here a short guide on how to register for the private service provider usergroup:

https://forums.veeam.com/veeam-backup-replication-f2/applying-to-veeam-cloud-service-provider-forums-t55488.html
 

Best,

Fabian


Comment