Use ReFS or XFS to improve merge performance and reduce space requirements for synthetic full and GFS through the Fast Clone feature.Include additional space for backup chain transformation (forward forever incremental, reverse incremental) - at least the size of a full backup multiplied by 1.25.Include additional space for one-off full backups.If there is a high percentage of databases involved, calculate with higher values like (e.g. Database servers have high change rates (up to 30-50% in worst case). Typical daily change rate is between 2% and 5% in a mid-size or enterprise environment.Data reduction thanks to compression and deduplication is usually 2:1 or more it’s common to see 3:1 or better, but you should always be conservative when estimating required space.The following figures are typical for most deployments however, it is important to understand the specific environment to figure out possible exceptions:

Is ReFS/XFS block cloning be used (recommended)Īlso, when testing is not possible beforehand, you should make assumptions on compression and deduplication ratios, change rates and other factors.

Planned backup chain type (recommended: Forward Incremental with synthetic full backups).

When estimating the amount of required disk space, you should know the following:

Add more resources if you plan to use health-checks as health checks require additional read IO.

Use ReFS/XFS with block cloning to reduce space requirements for synthetic fulls and GFS restore points and improve merge performance.

Use the Veeam Size Estimator (VSE) to estimate capacity requirements.

This section refers to the sizing of standard disk repositories.

This site uses Just the Docs, a documentation theme for Jekyll.

Restoring VMs to an HPE 3PAR with thin disks.

Backup Repository HA using Windows Storage Replica.

Veeam backup sizing calculator