In this section, we will describe how to design and size the Veeam backup server.
The first choice a designer has to do, is if the Veeam Server is going to be a machine dedicated to run only the central component of a Veeam Backup & Replication environment, or if it will hosts multiple roles at the same time. This choice usually relates to the size and complexity of the environment:
- all-in-one (Appliance Model): all the Veeam components (Backup Server, proxy, repository, and possibly others) are installed in one single machine. In this case, the different configuration numbers need to be summed together to find out the final required size of the server;
- scale-out (Dedicated server): the machine where the Backup Server is installed runs only this service (maybe also Enterprise Manager and SQL server are installed), so the sizing calculations only involves this roles.
Choosing which deployment mode to use involves multiple considerations. We list here a few:
- all-in-one is more simple, requires minimum design effort (we only have to size the underlying server) and the Veeam server is self-contained. If this is done on a physical machine, this “Appliance” is totally independent from the environment it is protecting. But it also become a single point of failure, as there is no redundancy.
- scale-out model is more powerful: we can have a “control plane” running VBR+EM+SQL in a virtual environment, to leverage the High Availability features, while the “data plane” with proxies and repositories will be different machines, each with their specific and optimized sizing. This design can protect big environments as both proxies and repositories can be deployed in multiple instances when needed.
When planning to use Veeam Backup & Replication for backup jobs only, the backup server should be placed in the main datacenter alongside the infrastructure to be protected to leverage quick response times and local management traffic.
When replication is used among multiple sites, the backup server should be deployed in the DR site to allow failover plans to work seamlessly, even in the case of the complete loss of the primary site. In this case, the scale-out model should be used, so that data traffic for backups stays in the primary datacenter, while only management and replication traffic flows between the two datacenters.
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.
For proper sizing, we suggest to use the Veeam Sizing Estimator.
Plan for a minimum of 40 GB. 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).
For backup server sizing and configuration refer to the Build - Backup Server section of this guide.
- Build - Backup Server
- Backup Server
- System requirements
- Installation settings
- Veeam Backup Catalog
- vPower NFS Service
- Quick Migration