Working with VM replication sets (Windows) : Performing a failover or failback
 
Performing a failover or failback
After the source virtual machine has been replicated to the destination server, the replication target virtual machine is ready for failover. Before performing a failover, you can select from multiple replicated generations if available. When a target virtual machine is being used after failover, it is available for failback.
The following procedure describes how to perform a failover or failback on a replicated virtual machine.
IMPORTANT:  Before performing a failback, ensure that the existing source virtual machine has been deleted. If you prefer to retain the existing source virtual machine, clone the virtual machine before deleting it.
To perform a failover or failback:
1. On the VM Replication menu, click All Replicated Machines to see a list of virtual machines that have been successfully replicated.
In the All Replicated Machines dialog box, in the Items ready for failover section, each row displays a source virtual machine that has been replicated to the destination server. In the Items ready for failback section, each row displays a target virtual machine that is being used after failover.
F1 Help: "All Replicated Machines"
2. To perform a failover, do the following in the Items ready for failover section:
a) In the Generations column, for each virtual machine on which you plan to perform a failover, verify that the replicated generation that you want to use is displayed. By default, the most recent replicated generation is already selected.
NOTE:  To select another generation from a list of all successfully replicated generations of the virtual machine, double-click the Generations column in the row that corresponds to the virtual machine and then click >>.
b) To perform a failover on one virtual machine, in the row that corresponds to the virtual machine, click Failover.
When you click Failover, the failover process begins. The selected generation of the virtual machine is powered on from the destination server. You can then start using the target virtual machine.
c) To perform a failover on multiple virtual machines concurrently, select the check box in the rows that correspond to the virtual machines, and then click Trigger.
NOTE:  DS-Client has no limit on concurrent failover activities.
When you click Trigger, the failover process begins. The selected generation of each selected virtual machine is powered on from the destination server. You can then start using the target virtual machines.
3. To perform a failback, do the following in the Items ready for failback section:
IMPORTANT:  Before performing a failback on a virtual machine, you must ensure that the existing source virtual machine has already been deleted. Do not delete a partially restored source virtual machine from a previously attempted failback that has been stopped or has failed.
a) To perform a failback on one virtual machine, in the row that corresponds to the virtual machine, click Failback.
b) To perform a failback on multiple virtual machines concurrently, select the check box in the rows that correspond to the virtual machines, and then click Trigger.
NOTE:  DS-Client allows a maximum of three concurrent failback activities.
c) In the Select the Source Host and Datastore for Failback dialog box, do the following for each virtual machine on which you are performing a failback:
F1 Help: "Select the Source Host and Datastore for Failback"
1. Verify the current source host and datastore.
2. To select a different source host, click the New source host list, and then select another host.
3. To select a different source datastore, click the New source datastore list, and then select another datastore.
4. To cancel, click Close.
5. To start the failback process, click OK. Any selections that you have made will be saved.
When you click OK, the failback process begins. The active virtual machine on the destination server is restored to the selected source host and datastore. The restored generation is powered on. You can then start using each source virtual machine.
NOTE:  If the failback is stopped or fails, restart in step 3a or 3b to reattempt. Do not delete a source virtual machine that has only been partially restored in a previous failback attempt.