HP StorageWorks Storage Mirroring Recover User's Guide (T5437-96008, November 2009)

528 of 739
Virtual workload failover
Select one of the following virtual machine failover scenarios:
Fail over an ESX virtual machine
Fail over a server to a virtual target machine on VMware ESX
Fail over a physical or virtual machine with Hyper-V
Fail over a Hyper-V virtual machine
Failing over an ESX virtual machine
If you have not done so already, launch the Storage Mirroring Recover for Virtual
Infrastructure console.
Note:
Storage Mirroring Recover for Virtual Infrastructure does not prevent you from
initiating a failover while the protection job is in the stopped state. While the job
is stopped, the validity of the target data cannot be verified because protection
is not active. Failing over could result in a corrupt target virtual machine or loss
of data. You should NOT perform a failover while the job is in a stopped state.
To ensure target data is up to date, re-start the protection job and then failover.
The following are representative scenarios where you might need to perform a failover or
reversal.
Failover after a problem is encountered on the source
1. Click the Failover button.
2. Choose the Live failover option. This will allow the clients to use the target until
the source is repaired. At this point, you can either:
Use the target replica as a permanent production server by deleting the
protection job, then selecting the Keep the associated replica virtual
machine option. For more information, see Monitoring protected virtual
machines.
Move the latest data back to the source. To do this, complete the following
steps.
3. Click the Reverse protection button. When you are prompted to confirm, click Yes
.
4. Wait for the original source to be synchronized with changes from the target.
5. Click the Failover button.
6. Choose the Live failover option.