Looking for Total Consumed Backup Storage for a Single VM in Deduplicated HyperScale X

Good question! To be clear: you are referring to the complete footprint of a protected instance including all it's recovery points without compression and deduplication taken into account. 

Hello ​@Onno van den Berg 

We are looking for the total amount of data that has been physically written and stored in the HSX, for a specific VM, without considering backup dates, retention periods, baseline backups or deduplication savings.

Just the actual consumed storage capacity for that VM’s backups currently present in the backup repository!

Best regards,
Nikos

Hello,

To provide more context on this: the customer’s question is —
“What is the exact capacity from HSX that the server xyz has stored until today and is still available (i.e., not deleted from storage)?”

To answer this, I reviewed the report “Jobs in Storage Policy Copies”, where it appears that the relevant field might be “Estimated Media Size” (which is a bit unexpected) rather than “Size on Media.”

I exported this report for all jobs written to HSX with “Data Status = Available.” Then, I calculated the totals for “Application Size,” “Estimated Media Size,” “Size on Media,” and “Data Written,” and also captured a screenshot from the Hyperscale storage capacity report.

From the results, the “Estimated Media Size” value seems to align most closely with the Hyperscale capacity (318 TB vs. 323 TB — a small discrepancy that I believe is normal). Based on this, the total capacity consumption on HSX for this specific server appears to be around 35 TB, which is also close to the “Total Media Size” (40.52 TB) shown in the Chargeback Details report.

That said, I still have a few open questions:

1. If “Estimated Media Size” from Jobs in Storage Policy Copies is indeed the correct value, why does the report show that the Synthetic Full job was written twice? Given the deduplication ratio (99.73%), the amount written for the second Synthetic job should have been only a few GB.

2. If the “Total Media Size” value from the Chargeback Details report is the accurate metric, how can I extract a detailed report listing the individual jobs that make up the 40.52 TB total?

3. If neither of the above interpretations is correct, which report and field should I use to accurately answer the customer’s question?

Thanks in advance for your help.

Here is also a response from Commvault support about this case:
 

Looking for Total Consumed Backup Storage for a Single VM in Deduplicated HyperScale X

To report the total backup storage footprint of a single VM in a deduplicated HyperScale X environment, you should use the Total Media Size column in the Chargeback Details report.

• Total Media Size: 
  • Represents the amount of all active data saved on storage media for the VM, across all storage policy copies and media types, excluding aged data.
  • For deduplicated copies, it is calculated as:
    Total Media Size = Application Size × Average Deduplication Ratio per copy
  • The average deduplication ratio is:
    (Total Size on Disk) / (Total Protected App Size) for the destination copy.
  • This column reflects the current storage footprint of all retained backup images for the VM, not limited by time or retention period.

Do not use the Media Size column for this purpose, as it is time-bound and may include aged/pruned data for a specific period, not the total currently retained.

Reference:
Data Views for Chargeback Details

Best regards,
Nikos