Feature request - Fix the size discrepancy shown between Veeam Azure appliance and what is reported by VBR server

[ajmayala85]

Hello Veeam R&D team,

Feature request to fix the immutable repo size discrepancy shown between what is reported by the Veeam Azure appliance and what is reported by VBR server in external repositories size.

On the Veeam case, The engineer states the following:

"Azure appliance reporting pulls usage directly from the Azure storage account. This includes raw block consumption, metadata, and additional overhead created by immutability (WORM blocks, retention markers).


VBR console reporting Displays logical backup data based on Veeam’s job metadata and catalog. It focuses on the backup chain sizes (VBK, VIB, VRB) rather than the full raw storage footprint.


Because immutability adds retention overhead and Azure calculates usage at the block level, the two views are expected to differ."

So this means:

1.-The appliance reflects the direct physical consumption in Azure (blocks, metadata, immutability overhead).
2.-The VBR console displays the logical size of the backup chains according to the Veeam catalog.

As an example, the VBAZ repo size is 138 TB, but on VBR side the external repo size is around 540 TB


But for the CX Internal Audit department, they need this issue to be fixed, they want to see the same number of TB on both sides (VBAz or VBR server) so is there a way to fix this discrepancy from the R&D side?

Veeam case:
Veeam Support - Case # 08019578 - Immutable repository size discrepancy between Veeam Azure portal and VBR Server console

Best regards

Alan