The "Used Space" value is greater than the "Capacity" value for backup repositories

Challenge

Cause

The Used Space value may be greater than the Capacity value in the following cases:

1. You have imported backups that can be found in the Home view under the Backups > Disk (Imported) node.
   
   Such imported backups are not stored directly on disks, but the size of these backups is still considered during calculation of the Used Space value. 
   
   If duplicates of imported backups appear under the Backups > Disk (Imported) node, this may mean that the recycle bin feature is enabled for a backup repository which holds copies of .vbm files from each backup session. When the backup repository is re-scanned, each .vbm file is considered as a separate backup, and the size of such a backup chain is added to the Used Space value. Alternatively, there may be backups under the Backups > Disk (Imported) node which were manually deleted but never removed from the configuration.
    
2. You have a ReFS repository in which synthetic full backups are created using the Fast Clone technology.

Solution

1. To correct the Used Space value that is shown for imported backups, you can remove these backups from the configuration and disable the recycle bin feature. If you have a large number of imported backup duplicates, a database edit might be required in order to save time, as manual removal may become impractically slow. In such a scenario, make sure to contact Veeam technical support.
    
2. For synthetic full backups with ReFS Fast Clone, backup files will be displayed as full-sized, even though only unique blocks are stored for each full backup file. In such a scenario, it is expected that the size that is shown under the Used Space column is a combined total value of the displayed file sizes in the backup repository. Refer to the Free Space column that should have an accurate value. The Used Space value will be displayed correctly if you check the properties for the ReFS volume in Windows.