I have 3 ESXi hosts in my environment and am using Veeam to backup VMs on all three hosts. I am running the latest version of Veeam Backup and Replication (7.0.0.833 - Enterprise Plus Edition).
- ESXi1 - located at main site (Veeam running as a VM on this host, only Veeam server at main site)
- ESXi2 - located at main site
- ESXi3 - located at remote site (Veaam proxy running as a VM on this host)
- Drobo B800i - located at main site, used as a backup target for all Veeam backups
- Drobo 5N - spare piece of gear I am thinking of using
The remote site in question has 10/10 fiber, our main site has 50/50 fiber, and the two are connected using Cisco ASAs.
Because I have the 10/10 fiber as the slowest link, I was thinking of putting a spare Drobo 5N we have on the remote site's network and adding it as a backup repository in my Veeam server. If I do that and still have the job scheduled to run on my main Veeam server, I know the proxy on the remote network will do the processing for the VM backups, but will the backups at the remote site run directly to the remote repository if I want to do it that way without sending any traffic back to my main Veeam server or making it the middle man between the proxy and the remote repository in some way? I was thinking running backups of the VMs at the remote site to the Drobo 5N on site, and then I could use backupcopy jobs and WAN Acceleration to send them back to my main site over the wire for less bandwidth usage.
Any advice is much appreciated here. If I try to do a full backup of the VMs at the remote site that is going to take a day or two if I am shipping it back to my main site.