Please insert the values of your environment

Increase valueDecrease value
Increase valueDecrease value
Increase valueDecrease value
Increase valueDecrease valueUsually 50% is a good estimation
Increase valueDecrease valueUsual values are between 2% and 5%
Increase valueDecrease value
Increase valueDecrease valueRecommendation: not much more than 300
Increase valueDecrease valueRecommended values are between 40 and 80.
Increase valueDecrease value

Resources for full backup

Memory CPU Cores
Backupserver
SQL
Proxy
Repository
SUM

Resources for incremental backup

Memory CPU Cores
Backupserver
SQL
Proxy
Repository
SUM

Additional optional roles

Memory CPU Cores
Tape 2 1
WAN Accelerator 8 4
Enterprise Manager 4 1
SUM 14 6

The simple IO sizer should give you an overview how many spinning disks you need for your repository. It is designed for two situations:
- full backup
- incremental backup
Reverse incremental forever and forward incremental forever require almost the same resources.

The incremental part is designed for "classic" file systems. It is not relevant for file systems with block cloning (ReFS). If you plan to run backup copy, tape jobs etc. at the same time you do backup: you will need more resources. The calculator is "backup only"

Production storage throughput (peak performance)

Peak throughput in MB/s for full backup
Peak throughput in MB/s for incremental run
Average Throughput in MB/s for full backup
Average Throughput in MB/s for incremental run

Repository throughput (peak performance)

MByte/s full backup (write 100%)
MByte/s incremental run (write 67% / read 33%)*
Mbyte/s per disk full backup
Mbyte/s per disk for incremental
*reverse incremental or forward incremental forever

Check this graphic from VT402 "Backup Repository Best Practices". Even low end systems should be able to reach this speed, but it is always a good idea to test (see Veeam KB2014)

Repository Disk Speed

Bandwidth between Repository server and disks (incremental run)

Repository Bandwidth

This sizer gives you more detailed input about IO sizes. The 256KB IOs is the backup data. The 4KB IOs are metadata updates.

Repository sizing active full backup (peak performance)

Mbyte/s (write 100%)
256 KB IOPS
4KB IOPS
Mbyte/s per disk
IOPS per disk

Repository sizing reverse incremental / forward forever incremental backup (peak performance)

Mbyte/s (write 67% / read 33%)
256 KB IOPS
4KB IOPS
Mbyte/s per disk
IOPS per disk

Bandwidth between Repository server and disks (incremental run)

Please insert your values

Increase valueDecrease value
Increase valueDecrease value

Results

Backupserver in best practice guide
min: 1 core + 5GB RAM per 10 concurrent jobs
recommended: 2 cores + 8GB
includes 2GB RAM for console
Proxy in best practice guide
proxy calculation

  • 2GB RAM per core
  • not more than 8 cores for virtual proxies
Repository in best practice guide
1 core per concurrent job
4 GB RAM per core

repository disk io

SQL in best practice guide

Number of concurrently running jobs Resources
up to 25 2 CPU, 4 GB RAM
up to 50 4 CPU, 8 GB RAM
up to 100 8 CPU, 16 GB RAM

If you prefer a local calculator, please find almost the same calculator as Excel spreadsheet below. I used different round functions, so minimal differences are normal.

Contact & Feedback

Feedback is welcome to hannes [dot] kasparick [at] veeam [dot] com

Please use the restore point simulator to size disk space of your repository


Note: This calculator is not approved. Use at your own risk. I created it according the Best-Practice-Guide V9.5U2 and VT402 presentation VeeamON 2017