Best practices recommend to deploy a Veeam backup server on the target site where replicated VMs will reside. Therefore, if you plan to perform VM replication with Veeam, consider placing a Veeam backup server at the replica target site. A backup server deployed in the DR site guarantees correct one-click failover during disaster recovery event. If it is not possible to deploy a Veeam backup server in the DR site, install Veeam Backup & Replication on a VM and replicate this VM to DR site. Then in the case of a disaster recovery event, you will be able to boot this replica VM using VMware vSphere Web Client and perform the necessary failover operations.
An organization comprises 50 branches, with ESXi hosts on each site, and a vCenter Server in the central location. IT require a central management point for the Veeam backup infrastructure, administration and job scheduling. They require local backups to be created at branch sites, and a backup copy job (with WAN acceleration) to consolidate these at Global HQ. An administrator can implement this example scenario in the following way:
1.Install Veeam Backup & Replication in the branch office (ROBO) and the datacenter (HQ), either on a virtual or physical server. (Do not configure WAN accelerators).
2.Add the branch office (ROBO) ESXi hosts to the corresponding (branch office) Veeam backup servers to provide fast local restore.
3.Install Veeam Backup & Replication at Global datacenter HQ and add all branch office (ROBO) Veeam backup servers as managed servers with proxy, repository and WAN accelerator.
Remember to add appropriate resources so that all 3 roles can run on this server.
4.Configure one or more repository servers and WAN accelerators at Global datacenter (HQ) as described in the documentation.
5.Add the vCenter Server to the Veeam Backup & Replication console at Global datacenter (HQ).
6.Configure backup and backup copy jobs on Veeam backup server at Global datacenter (HQ) for all branch offices (ROBO).
This deployment scenario facilitates centralized administration via Veeam backup console at HQ.
However, the following considerations should be taken into account:
▪Use local Veeam backup servers to rescan/import backups for file-level restore and item-level restore via Veeam Explorers.
▪Enterprise Manager can be used with all of its functionality, but Enterprise Manager Self-Service file restore functions and object restore cannot be used, as it would mount the whole backup file to the central Veeam backup server through the WAN link and also transport the restore data stream twice through the WAN link. This does not affect 1-Click VM Restore/failover and job administration by Enterprise Manager.
▪If a WAN link fails, no backup job will run, as the backup server will not be able to connect to the branch office Veeam and VMware components to start required tasks.
▪As components are managed by multiple backup servers, always ensure that the same patch/update/version level is used for the entire Veeam backup infrastructure.
An organization features 50 branches, with ESXi hosts on each site, and a vCenter Server in the central location. They require VM backups and Self-Service Restore to function without data flowing through a WAN link for restore, as the WAN bandwidth is very low. They require local backups to be created at branch sites, and a backup copy job (with WAN acceleration to save bandwidth) to consolidate these at Global HQ.
An administrator can implement this example scenario, as follows:
1.Install an Enterprise Manager on the Global HQ and add all Veeam Backup & Replication servers later.
2.Install Veeam Backup & Replication on each site, either on a virtual or physical server.
3.Configure WAN accelerators as described to the documentation.
4.Add the branch office ESXi hosts to the corresponding (local) Veeam backup servers to provide fast local restore.
5.Install Veeam Backup & Replication at Global HQ for import and restore of backups that are copied to the Global HQ using the backup copy jobs.
6.Configure backup and backup copy jobs on Veeam backup servers in the branch offices.
This deployment scenario facilitates VM backups at local sites, as well as Enterprise Manager-based Self-Service Restore. Windows VM Restore File Level Recovery and application item restore via Veeam Explorers can be done without a need to rescan/import the backups directly at the branch office Backup & Replication servers. You can use multiple Veeam Backup & Replication management consoles for independent job scheduling.