I get this frequent, so may as well blog it! Let’s start with my own definition of a VMware Backup Proxy with Veeam Backup & Replication:
A proxy is a data mover for backup and replication jobs with Veeam. The proxy exists as a Windows service (recommended on Windows Server – even Core) and interacts with the Veeam console (where jobs are defined and scheduled). One proxy is installed by default, and additional proxies can be added as needed. For replication, always have a proxy on each site (Production and DR).
OK, now that we’ve covered that. Here is how you add a proxy:
1. Navigate to the Backup Infrastructure section and select “Add VMware Backup Proxy”
2. Click the “Add New” if the server isn’t inventoried already:
3. Add the DNS name (in this example FA1 is in the failover site):
4. Type in a local administrator privileged user:
5. You will then get the summary that the Veeam code will be installed:
6. The summary states that the service was pushed successfully:
7. The proxy wizard will return (note the max concurrent tasks counter):
A single Veeam backup or replication job needs 2 cores to be successful. So this proxy can optimally run 1 job concurrently. If 2 are desired, I’ll need to add more vCPU.
8. You can set throttling if you want:
This is for certain networks during certain time frames to consume no more than x rate of a network bandwidth.
9. You are done!
10. Now, to make the proxy perform with Direct SAN transport mode; I’ll need to add the iSCSI targets of the SAN to the iSCSI initiator of each proxy (in that site). Read this blog post on Direct SAN mode: http://www.veeam.com/blog/direct-san-access-tips-for-iscsi-vmfs-volumes-and-backup-proxies.html
This will allow you then to allow a replication job to use the two-proxy architecture, as well as scale out your backup infrastructure.
The proxies are used in the job configuration, by default the select automatically the best proxy.
Have questions? Ask me on Twitter @RickVanover