Original Location Recovery (OLR)

If we choose to fail back to the original virtual machine, the following conditions need to be met:

 If the virtual machine is managed by a vCenter server, then the master target's ESX host should
have access to the virtual machine's datastore.
 If the virtual machine is on an ESX host but isn’t managed by vCenter, then the hard disk of the
virtual machine must be in a datastore that the master target's host can access.
 If virtual machine is on an ESX host and doesn't use vCenter, then we should complete
discovery of the ESX host of the master target before we reprotect. This applies if we're failing
back physical servers, too.
 We can fail back to a virtual storage area network (vSAN) or a disk that based on raw device
mapping (RDM) if the disks already exist and are connected to the on-premises virtual machine.

 Important

It is important to enable disk.enableUUID= TRUE so that during failback, the Azure Site Recovery
service is able to identify the original VMDK on the virtual machine to which the pending changes will
be written. If this value is not set to be TRUE, then the service tries to identify the corresponding on-
premises VMDK on a best effort basis. If the right VMDK is not found, it creates an extra disk and the
data gets written on to that.

Before We start
 After a VM boots in Azure after failover, it takes some time for the agent to register back to the
configuration server (up to 15 minutes). During this time, you won't be able to reprotect and an error
message indicates that the agent isn't installed. If this happens, wait for a few minutes, and then
reprotect.
 If we want to fail back the Azure VM to an existing on-premises VM, mount the on-premises VM
datastores with read/write access on the master target server's ESXi host.
 If we want to fail back to an alternate location, for example if the on-premises VM doesn't exist, select
the retention drive and datastore that are configured for the master target server. When you fail back to
the on-premises site, the VMware virtual machines in the failback protection plan use the same datastore
as the master target server. A new VM is then created in vCenter.

Enable reprotection as follows:

1. Select Vault > Replicated items. Right-click the virtual machine that failed over, and then
select Re-Protect. Or, from the command buttons, select the machine, and then select Re-
Protect.
2. Verify that the Azure to On-premises direction of protection is selected.
3. In Master Target Server and Process Server, select the on-premises master target server and
the process server.

Sensitivity: Business Internal

 4. For Datastore, select the datastore to which you want to recover the disks on-premises. This
option is used when the on-premises virtual machine is deleted, and you need to create new
disks. This option is ignored if the disks already exist. You still need to specify a value.
5. Select the retention drive.
6. The failback policy is automatically selected.
7. Select OK to begin reprotection.

8. A job begins to replicate the Azure VM to the on-premises site. You can track the progress on
the Jobs tab.
o When the reprotection succeeds, the VM enters a protected state.
o The on-premises VM is turned off during reprotection. This helps ensure data
consistency during replication.
o Don't turn on the on-premises VM after reprotection finishes.

Sensitivity: Business Internal