- #Veeam backup and replication full
- #Veeam backup and replication password
- #Veeam backup and replication windows
Now, assuming that a backup copy job runs for all VMs every night, some non-critical VMs can be replicated from the daily backup file. In this case, the data communication link should be mostly used for the critical VM replicas synchronization with a challenging RPO. A common example beside the usage of proactive VM restores is a remote office infrastructure, where the link between the remote site and the headquarters provides limited capacity. In some circumstances, you can get a better RTO with an RPO greater or equal to 24 hours, using replicas from backup. When using replication from backup, the target VM is updated using data coming from backup files created by a backup or backup copy job. When replicating VMs to a remote DR site, you can also manage network traffic by applying traffic throttling rules. Veeam ONE may help with estimating change rates ( VM Change Rate Estimation report in Infrastructure Assessment packs) and collecting other information about the infrastructure.
You may try to set up a backup job having the same settings as the replication job and test the bandwidth (as the backup job will transfer the same amount of data as the replication job).
#Veeam backup and replication full
Full information about these factors, however, is rarely at hand. Replication bandwidth estimation has always been a challenge because it depends on multiple factors such as the number and size of VMs, change rate (at least daily, per RPO cycle is ideal), RPO target, replication window. In this scenario, a failover can be performed from the Veeam console without a working vCenter Server itself (for example to failover the vCenter Server virtual machine).
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.
#Veeam backup and replication password
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 as well 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.
#Veeam backup and replication windows