[Feature Request] Backup size reflect actual space used for object storage performance tier

[sonobob]

I worked with Veeam support recently trying to get accurate storage consumption numbers for object storage repositories in the performance tier. The "backup size" we see in backup properties listed under object storage shows a number much larger than the actual storage consumed on the repo. For example, we have a job backing up to a Nutanix object store that reports a total consumed space of about 15TB. But when we view the properties for that jobs backups, it shows a much larger value of over 30TB consumed. In Backup Infrastructure, the correct consumed space of 15TB is reported, which matches what we see in Nutanix Objects. This also applies to Azure object storage. What happens is that backup size number is used in Veeam One reports and shows that we have a much larger backup set in object storage repos than we actually do, making that number useless for any capacity planning you may have to do. If I were to rely on that number, I would over-provision my repos significantly.

Case #07917638

[david.domask]

Hi sonobob,

Thanks for sharing the case number -- give me a bit to verify a few things with Support as I'm not sure I fully understand the answer on the case regarding the discrepancy, and will update with more information.