Feature Request | Veeam One Report to Determine the actual used space

[pankajnp]

Hi Team,
We are using a Linux hardened repository with Fast Clone-compatible storage (XFS). As noted in Veeam KB2996, the 'Used Space' value may appear greater than the actual 'Capacity' due to how Veeam calculates transferred data for restore points.

To determine the actual used space after accounting for space savings from restore points, can Veeam one develops such a report?

"I’ve tried multiple reports such as 'Backup on Repository', 'VM Backup File Growth', 'Job History Report', and 'Data Change Rate History Report', but none of them provided the specific insights we’re looking for.
The 'Capacity Planning for Repository' report only offers high-level information about free space and does not deliver granular, workload-wise space consumption details.
We're specifically looking a report to determine the WORKLOAD WISE actual used space after accounting for space savings from restore points."

Veeam Support case number:- Case #07809401

[RomanK]

Hello Pankaj,

Thanks for the case number and the feature request. Recently it was discussed internally.

these types of storage systems often don’t report the actual space usage accurately to VBR. Instead, they return values as if the referenced blocks were physically written, which leads to misleading space consumption metrics. Veeam ONE and VBR teams have plans to address this issue, but since the solution is quite complex some numbers are still not available.

So, we already have a such requests and yours is now added to the list as well. We’ll do our best to make it happen if the platforms allow.

Thanks for the feedback.

[pankajnp]

Hi Roman,

Many thanks for the quick update.

However, I'm currently unable to access the thread — I’m getting a message saying "You are not authorised to read this forum."

[RomanK]

Hello Pankaj,

Ah, yes, I removed the link as it is internal. Didn't noticed that. The summary is in the quote above. Everything depends on the data provided by XFS and others to VBR and consequently for Veeam ONE to collect. As soon as it there, we will collect it.

Thank you.