In this section, we will describe how to design and size the Veeam backup server.
Sizing with Veeam is cumulative in respect to configurations, if you want to create an all-in-one appliance (Appliance Model) sum up all the resource requirements (CPU + Memory) to understand what you will need in total, combining roles such as the proxy and repository merits the same considerations.
When planning to use Veeam Backup & Replication for backup jobs only, the backup server should be placed in the main datacenter alongside the virtual infrastructure to be protected to leverage quick response times and local management traffic.
When replication is used the backup server should be deployed in the DR site to allow failover plans to work seamlessly and without any manual complex operations. The primary infrastructure can be managed with the same backup server that will manage the backup proxies deployed in the main site.
Recommended Veeam backup server configuration is 1 CPU core (physical or virtual) and 4 GB RAM per 10 concurrently running jobs. Concurrent jobs include any running backup or replication jobs as well as any job with a continuous schedule such as backup copy jobs and tape jobs.
The minimum recommendation is 2 CPU cores and 8 GB RAM.
Plan for a minimum of 40 GB. If installing in a virtual machine, thin disks may be used. By default the installer will choose the drive with most available free space for the pre-configured Default Backup Repository.
Log file growth will depend on the number and frequency of jobs and the number of instances being protected. Consider that the logging level may also affect the log size.
Plan for 3 GB log files generated per 100 protected instances, with a 24 hour RPO. For environments with more than 500 protected instances it is recommended to change the default location to a different fast access disk. Many concurrently running jobs may produce a lot of write streams to log files, that can slow down operations for the Veeam Backup Service and Backup Manager processes.
This folder is used if guest indexing in backup jobs is enabled.
Plan for 10 GB per 100 VM for guest file system catalog folder (persistent data).
When booting VMs with Instant VM Recovery or SureBackup, this folder is used by default to store all configuration files and redo logs of the running VM. To offload the changes to a specific production datastore refer to the corresponding page of the Instant VM Recovery wizard.
The vPower NFS server is bound to backup repositories and the folder location is defined per server. To achieve best performance for VMs running on vPower NFS please configure the fastest possible storage on the backup server or backup repository.
It is recommended to reserve at least 10 GB space for this folder. If you plan to start a significant number of VMs or run VMs over a longer period increase the space accordingly to fit the produced/estimated amount of changes generated by the running VMs (conservative average change rate can be defined as 100 GB per 1 TB VM per 24 hours - or 10%). Additional disk space is consumed when using Quick Migration.