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

Veeam Management Pack Help Center  > Best Practices for Deployment & Configuration >  Deployment Scenarios > Medium-size or Large-scale Environment: Advanced Deployment

Medium-size or Large-scale Environment: Advanced Deployment

Previous page Next page Print this Topic

Table of contents

For medium-size or large-scale environments, it is recommended to use the advanced deployment scenario which moves the backup workload from Veeam Backup server to dedicated backup proxies and backup repositories.

The essence of the advanced deployment is that the backup proxy takes off a part of Veeam backup server activities — namely, it collects and processes data and moves backup traffic from source to target. In addition, the Veeam backup server no longer acts as a storage location — the backup proxy transports VM data to the backup repository which is the location for keeping backup files, VM copies, metadata and so on. The Veeam backup server in this scenario functions as a ‘manager’ for backup proxies and repositories.


You just add servers to Veeam Backup & Replication and assign proxy and repository roles to them. Veeam Backup & Replication will automatically install light-weight components and services onto these servers. Backup proxies do not require SQL — all settings are stored centrally, within the SQL database used by the Veeam backup server.

Example 1: Virtual Veeam Backup Server, Virtual Proxy

Deploying Veeam backup server on a VM allows you to leverage vSphere features such as High Availability and vMotion. For peculiarities of physical and virtual proxies, please refer to Physical or Virtual? section of this guide.


With the advanced deployment scenario, you can easily meet your current and future data protection requirements. You can expand your backup infrastructure horizontally in a matter of minutes to match the amount of data you want to process and available network throughput. Instead of growing the number of backup servers or constantly tuning job scheduling, you can install multiple backup proxies and repositories and distribute the backup workload among them.

Example 2: Backup with Multiple Virtual Proxies


When using multiple proxies, Veeam Backup & Replication provides for dynamic distribution of the backup traffic among these proxies:

A job can be explicitly mapped to a specific proxy.

Alternatively, you can let Veeam Backup & Replication choose a proxy. In this case, Veeam Backup & Replication will check settings of available proxies and select the most appropriate one for the job.

The advanced deployment scenario can be a good choice for backing up and replicating off-site. You can deploy a backup proxy in the production site and another one closer to the backup repository.

Example 3: Off-site CIFS and Multiple Proxies


When a job is performed, backup proxies on both sides establish a stable connection, so this architecture also allows for efficient transport of data over a slow network connection or WAN.

To regulate backup load, you can specify the maximum number of concurrent tasks per proxy and set up throttling rules to limit proxy bandwidth. The maximum number of concurrent tasks can also be specified for a backup repository; additionally, you can define combined ingestion rate for it.

Another advantage of the advanced deployment scenario is that it contributes to high availability: jobs can migrate between proxies if one of them becomes overloaded or unavailable.

Example 4: Scaling for Production and DR Sites

Another option is to have one Veeam backup server deployed in production site to be responsible for backup jobs and/or local replication, and another Veeam backup server installed at the DR site for the remote replication jobs:


Thus, in disaster situation all operations can be performed by Veeam backupsServer in DR itself without any problems.


Typically, it is recommended to deploy one proxy for backup & restore, and another for replication and failover.

With Veeam’s restore capabilities to be used efficiently, you can also think of deploying a virtual proxy per cluster for hot-add restore.

Table of contents