It can be best practice to add the ESXi hosts from the replica target side (only) directly to Veeam Backup & Replication as managed servers and to perform replication without vCenter Server on the target side. In most cases, Veeam does not need a vCenter Server for replica target processing. If you use a password manager such as KeePass, it’s also a good idea to include it in the scenario. vCenter Server (and vCD) infrastructure should also be considered for the failover scenario. DNS and possibly authentication services (Active Directory, for example, or DHCP server if some replicated VMs do not use static addresses) should be implemented across both sides. These mechanisms reduce the amount of replication traffic while network mapping and re-IP streamline replica configuration. When planning off-site replication, consider advanced possibilities: It is recommended to place a Veeam backup server on the replica target side so that it can perform a failover when the source side is down.

WAN Accelerators (Enterprise Plus) can help replication jobs fit into allowed windows when bandwidth is not sufficient.

You can manage network traffic by applying traffic throttling rules.

Replication bandwidth estimations can be made using Veeam ONE.Plan failover carefully, in particular, DNS and authentication on both sites.Place a Veeam backup server on the replica target site.This site uses Just the Docs, a documentation theme for Jekyll. Restoring VMs to an HPE 3PAR with thin disks.Backup Repository HA using Windows Storage Replica.

Veeam best practice backup job