In the next step, you can create the mapping between source and destination virtual network. Some disks can be excluded if you wish.Īfter that, select the destination cluster / host and the proper resource pool, VM folder and Datastore. Next I select the VMs that will be replicated. Different IP addressing scheme ( enable re-IP): enables to change VM address IPs to be consistent with the destination virtual network.Separate virtual networks (enable network remapping): If both datacenters don’t share the same IP address plan, you need to map the source and destination network.Low connection bandwidth (enable replication seeding): you can copy the VM backup to the second site as a “seed” instead of copy the initial replication over the WAN.Then give a name and a description to the replication job. Then select the appropriate option (I choose VMware vSphere). Step 1: Replicate VMsįirst of all, open your Veeam Backup & Replication console and click on Replication Job. In this way I can work on the vSAN cluster without thinking about the VMs. Usually we run VM on a cluster and then we replicate to a standalone cluster but in my lab, it is the opposite.
In this topic, I will show you how to leverage Veeam Backup and Replication to make a disaster recovery plan. Products such as Microsoft Hyper-V or VMware vSphere can also handle this task. The replication part ensures that your workloads can quickly start again in another datacenter in case of sinister in the first one. It enables to restore the data in case of loss. The backup part ensures your workloads are protected against bad manipulation, ransomware or disaster. Veeam Backup and Replication is a backup and replication product.