[Feature Request] Better reporting for scale out backup repo usage in console

[Matthewh]

So I had a ticket open about this as we just started using scale out backup repositories and our primary repo and we were seeing odd numbers under the used and free space available in the console.

The engineer explained that the used space figure displays sizes before any deduplication or fast clone savings, this explained why our used space + free space did not total the capacity of the system.

I would like to request that details of fast clone/dedupe savings are split into a different data field within the console so that we have proper detail on free and used space as it actually is and any additional information about fastclone or dedupe savings are displayed in a different way, it leads to confusion and complexity when dealing with our monitoring of these systems as our first line engineers raise it as a issue as the space doesnt match properly.

[HannesK]

Hello,
first the product has to know about fastclone savings. After that we can show it (in console and other places).

It's a "classic" feature request from service providers and customers with internal chargeback and it's something we want to improve in future, yes.

Best regards,
Hannes

[Matthewh]

Okay so Veeam is not currently able to calculate the savings provided by fast clone or deduplication so it can't use it to do accurate maths, well here is hoping that you can find a way to deliver that in the future.