Veeam Home | Support | Downloads
Best Practices for Veeam Backup & Replication 7.0 for VMware

Veeam Management Pack Help Center  > Best Practices for Deployment & Configuration >  Resource Planning and Optimization > Planning for Repositories > Examples

Examples

Previous page Next page Print this Topic

Table of contents

The examples below explain the impact of backup method and retention policy on the estimated repository size, assuming environment is the same in all three cases.

Environment: 10 VMs, 100GB each, 80GB avg/used

2:1 Estimated Compression/Deduplication, 5% daily change

Example 1

Backup: Reverse Incremental, Daily Backup, 30 Day Retention

Estimated Full Backup Size:

10 * 80GB (Used space) * 50% (2:1 Compression) = 400GB

Estimated Reverse Incremental Size:

10 * 80GB * 50% (2:1 Comp) * 5% (Change Rate) * 29 (reverse incremental restore points) = 580GB

Estimated total Backup Size:

400GB + 580GB = 980GB

Example 2

Backup: Forward Incremental, Daily Backup, 30 Day Retention, Weekly Full

Estimated Full Backup Size:

10 * 80GB (Used space) * 50% (2:1 Compression) = 400GB

Estimated space for 6 Weekly Fulls (Max required for 30 Day Retention):

400GB * 6 = 2400GB

Estimated Forward Incremental Size Max:

10 * 80GB * 50% * 5% * 32 = 640GB

Estimated total Backup Size:

2400GB + 640GB = 3,040GB (~3TB)

Example 3

Backup: Forward Incremental, Daily Backup, 30 Day Retention, Monthly Full

Estimated Full Backup Size:

10 * 80GB (Used space) * 50% (2:1 Compression) = 400GB

Estimated space for 3 Monthly Fulls (Max req for 30 Day Retention):

400GB * 3 = 1200GB

Estimated Forward Incremental Size Max:

10 * 80GB * 50% * 5% * 60 = 1200GB

Estimated total Backup Size:

1200GB + 1200GB = 2,400GB (~2.4TB)

To summarize, when estimating the size of your repositories, use the following best practices:

Be conservative when estimating compression and deduplication ratios if actual ratios and disk content are unknown.

Use higher estimates for change rate if a significant number of servers are transactional such as SQL and Exchange.

Include enough free space to take at least one extra full backup for each job.

Table of contents