We are looking at a modifying our current Veeam 9.5 deployment for a similar scenario, except that our "DR site" is MS Azure. Thus, our connection to it is much slower than in the original post here.
Our prod site has two ESX hosts, not 3, with one vCenter server and a direct-connected SAN. The existing Veeam Backup & Replication server is a physical server, with both internal and NAS-based repositories (not on the production SAN). We have a VM proxy server to assist with the backup of the on-site VM servers.
We have an existing VM in Azure that has our current offsite repository, with that Azure VM set as a proxy server.
The current, single, on-site, physical B&R server currently manages the backup copy jobs to the Azure repository.
For improved/simplified site DR, we are considering either moving the B&R server to the Azure VM or installing a second instance of B&R server there and having it run the backup copy jobs to it's repository.
According to this article, it seems like having the second B&R server may be the better bet, giving ease of restore for site failover, but maintaining local backup performance at the prod site:https://www.veeam.com/blog/physical-vir ... ation.html
However, to do this, does it get into the potential mess with multiple B&R servers having access to the same repositories? Would the Azure-based server have to be connected to the prod site repositories to do the copy jobs, or does it just talk to the prod site B&R server?
Also, would Veeam Enterprise Manager have a useful role here, particularly with managing encryption of the jobs and potential recovery of the encrypted configuration etc?