With vSphere Replication you can recover successfully replicated virtual machines at the target site, one at a time.
Before you begin
Verify that the virtual machine at the source site is powered off.
- Log in to the vSphere Web Client for the target site.
- On the Incoming Replications tab, right-click the virtual machine to recover and select Recover.
- Select whether to recover the virtual machine with all the latest data, or to recover the virtual machine with the most recent data from the target site.
Recover with recent changes
Performs a full synchronization of the virtual machine from the source site to the target site before recovering the virtual machine. Selecting this option avoids data loss, but it is only available if the data of the source virtual machine is accessible. You can only select this option if the virtual machine is powered off.
Recover with latest available data
Recovers the virtual machine by using the data from the most recent replication on the target site, without performing synchronization. Selecting this option results in the loss of any data that has changed since the most recent replication. Select this option if the source virtual machine is inaccessible or if its disks are corrupted.
- Select the recovery folder and click Next.
- Select the target compute resource and click Next.
- If the virtual machine contains hard disks for which you have not enabled replication, select a target destination to attach an existing disk or detach the disk, and click Next.
This page only appears if the virtual machine contains hard disks for which you have not enabled replication.
To select a target destination, click Browse and navigate to a folder on a datastore in which disk file is placed.
To detach the disk and exclude disk files from the recovery, click Detach.
- (Optional) : Select Power on after recovery.
- Click Finish.
vSphere Replication validates the provided input and recovers the virtual machine. If successful, the virtual machine status changes to Recovered. The virtual machine appears in the inventory of the target site.
If you enabled multiple point in time instances when you configured replication for the virtual machine, vSphere Replication presents the retained instances as standard snapshots after a successful recovery. You can select one of these snapshots to revert the virtual machine. vSphere Replication does not preserve the memory state when you revert to a snapshot.
If the recovery fails, the replication of the virtual machines reverts to the replication state before the attempted recovery. For more information about the failed recovery attempt, check the last recovery error message in the replication details pane or check vCenter Server tasks.
The recovery might also fail if you use the same name for the virtual machine in a scenario where you use vSphere Replication to replicate a virtual machine in a single vCenter Server and the vCenter Server instance has only one host in its inventory. See Error Recovering Virtual Machine in a Single vCenter Server Instance for more information.
After a successful recovery, vSphere Replication disables the virtual machine for replication if the source site is still available. When the virtual machine is powered on again it does not send replication data to the recovery site. To unconfigure the replication, select Stop replication.
When the source virtual machine is no longer in the vCenter Server inventory, the replication is unconfigured. Unconfigured replications do not appear in the Summary tab nor in the Incoming Replications or Outgoing Replications tabs. Check vCenter Server task history for information on performed recoveries.
If a replicated virtual machine is attached to a distributed virtual switch and you attempt to perform a recovery in an automated DRS cluster, the recovery operation succeeds but the resulting virtual machine cannot be powered on. Edit the recovered virtual machine settings to attach it to the correct network.
vSphere Replication disconnects virtual machine network adapters to prevent damage in the production network. After recovery, you must connect the virtual network adapters to the correct network. If target host or cluster has no access to the DVS the virtual machine was configured with at the source site, manually connect the virtual machine to a network or other DVS to successfully power on the virtual machine.