Veeam Backup & Replication 10
User Guide for Microsoft Hyper-V
Related documents

Replica Mapping

If a replica for the VM that you plan to replicate already exists in the DR site, you can map the original VM in the production site to this VM. For example, you can map the original VM to a VM replica created with another replication job or restore a VM from the backup on the target host in the DR site and map the original VM to it. You can also use replica mapping if you need to reconfigure or recreate replication jobs, for example, split one replication job into several jobs.

Replication to a mapped VM is performed in the following way:

  1. During the first run, the replication job calculates the differences between the original and mapped VM. Instead of copying and transferring all data of the original VM, the replication job transfers only incremental changes to synchronize the state of the mapped VM with the state of the original VM.

After successful synchronization, in the Home view of Veeam Backup & Replication, under Replicas node you will see a VM replica with 2 restore points:

    • One restore point will contain the latest state of the mapped VM.
    • The other restore point will contain the latest state of the original VM on the source host.
  1. All subsequent runs of the replication job will be performed in a regular manner: Veeam Backup & Replication will transfer only incremental changes to the target host.

 

Replica Mapping 

Replica Mapping for VMs with Checkpoints

[For legacy replicas] The legacy VM replica to which you map the original VM must not have any checkpoints. Otherwise, replica mapping will not work.

[For snapshot replicas] If a snapshot replica to which you map the original VM has any checkpoints that were created by Veeam Backup & Replication, for example, with a replication job run on another backup server, Veeam Backup & Replication will identify these checkpoints as valid restore points for the VM replica and, additionally, will create one new restore point during the first run of the replication job. For example, if a VM replica on the target host has 3 checkpoints created with Veeam Backup & Replication, after the first run of the replication job, you will have a VM replica with 4 valid restore points.

If a snapshot replica to which you map the original VM has any checkpoints that were created outside Veeam Backup & Replication, for example, triggered manually by the user, Veeam Backup & Replication will not identify them as valid restore points. During the first run of the replication job, Veeam Backup & Replication will create 2 new restore points as described in the procedure above.

For example, if a VM replica has 2 checkpoints created in Hyper-V Manager, after the first run of the replication job, you will have a VM replica with 2 restore points. 2 checkpoints created in Hyper-V Manager will remain in the checkpoint chain. However, you will not be able to see these checkpoints in the Veeam Backup & Replication console and will not be able to use these checkpoints for failover and failback operations.

Related Topics

Defining Seeding and Mapping Settings

This Document Help Center
User Guide for VMware vSphereUser Guide for Microsoft Hyper-VVeeam Backup Enterprise Manager GuideVeeam Agent Management GuideVeeam Cloud Connect GuideVeeam Explorers User GuideVeeam Plug-ins for Enterprise Applications GuideVeeam PowerShell ReferenceVeeam Explorers PowerShell ReferenceVeeam RESTful API ReferenceRequired Permissions for VMware vSphereQuick Start Guide for VMware vSphereQuick Start Guide for Microsoft Hyper-VVeeam Backup for AWS DocumentationVeeam Availability for Nutanix AHV DocumentationVeeam Backup for Microsoft Office 365 DocumentationVeeam ONE DocumentationVeeam Agent for Windows DocumentationVeeam Agent for Linux DocumentationVeeam Management Pack Documentation
I want to report a typo

There is a misspelling right here:

 

I want to let the Veeam Documentation Team know about that.