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
Rickatron Blog 
Posted by FTF Veeam v6 Replication – Phased Implementaton Methodology | VMETC.com on July 23, 2012 at 9:52 pm
[…] the technical details in this series, but there are already many posts on installing Veeam v6 and creating Proxies, creating replication jobs, or you can follow the Evaluators Guides for vSphere or Hyper-V. […]
Posted by Manuel Joao Matos on March 1, 2013 at 1:29 pm
Hi!
I’ve come to a problem where I have several backup proxies on each site and still have some issues. So I decided to clone some virtual machine proxies and configure them like described above.
For some reason the replication jobs never use the new proxies despite them seeing all datastores and being correctly added to the Backup Infrastructure on Veeam 😦
Is there any additional configuration needed?
Posted by rickvanover on March 3, 2013 at 11:35 pm
I don’t recommend cloning proxies. Maybe clone the VM then add it to Veeam as a proxy.
Posted by Manuel Joao Matos on March 4, 2013 at 6:01 am
In fact I did clone one VM already configured as proxy and then I unistalled the transport agent and added it to Veeam as a managed server and then as a proxy with no issues.
After this the newly configured proxy never works on the jobs 😦
I even tried to disable all the other proxies to force this new one to assume the jobs but it didn’t work
Posted by Grant on August 15, 2013 at 1:52 pm
You need to go to the actual replication/backup job on the Backup & Replication server. Right click job, edit, Job Settings, and select your desired target and source proxies. All of this after the proxy has been added as described above.
Posted by wRx7M on September 25, 2013 at 7:11 pm
Thanks for this information. It is a little different in Veeam 7 but not by much. This has shed some light on something that I could not really get much information on prior to finding your nice walk-through. Thanks again!