Open topic with navigation

Failing over Hyper-V to Hyper-V jobs

When a failover condition has been met, failover will be triggered automatically if you disabled the wait for manual intervention option during your protection configuration. If the wait for manual intervention option is enabled, you will be notified in the console when a failover condition has been met. At that time, you will need to trigger it manually from the console when you are ready.

1. On the Manage Jobs page, highlight the job that you want to failover and click Failover in the toolbar.
2. Select the type of failover to perform.
• Fail over live data—Select this option to initiate a full, live failover using the current data on the target. This option will shutdown the source machine (if it is online), stop the protection job, and start the replica virtual machine on the target with full network connectivity.
• Perform test failover—Select this option to perform a test failover using the current data on the target. This option will leave the source machine online, suspend the protection job, and start the replica virtual machine on the target without network connectivity.
• Failover from a snapshot—This option is not applicable to virtual protections.
3. Select the how you want to handle the data in the target queue. You may want to check the amount of data in queue on the target by reviewing the Statistics or Performance Monitor.
• Apply data in target queues before failover— All of the data in the target queue will be applied before failover begins. The advantage to this option is that all of the data that the target has received will be applied before failover begins. The disadvantage to this option is depending on the amount of data in queue, the amount of time to apply all of the data could be lengthy.
• Discard data in the target queues and fail over immediately— All of the data in the target queue will be discarded and failover will begin immediately. The advantage to this option is that failover will occur immediately. The disadvantage is that any data in the target queue will be lost.
• Revert to last good snapshot if target data state is bad— This option is not applicable to virtual protections.

4. When you are ready to begin failover, click Failover.

   Once failover has occurred, if you add CPUs to the replica of the source on the target, you may have to reboot the replica before the operating system will recognize the additional CPUs.

   IPv6 addresses on the source will be set to DHCP on the target after failover. Update them to static addresses manually, if needed.

   If you are using node-locked activation codes, you are limited to three failovers and reverses.

   In a cluster configuration, if you move the shared storage ownership on the original source cluster or change the drive letter after failover, you will be unable to reverse your protection. Keep the source cluster configuration the same in order to allow proper reversing of protection.

    

5. If desired, you can undo your live or test failover by selecting Undo Failover in the toolbar. In either case, the replica virtual machine on the target will be shut down and the protection job will be restarted performing a file differences mirror. The one difference when undoing a live failover is the virtual machine on the source will be restarted. This step is not needed when undoing a test failover, because the virtual machine on the source is not shut down during a test failover. In both cases, all changes made on the replica virtual machine on the target will be lost. If you do not want to lose data changes made on the replica virtual machine on the target, see Reversing Hyper-V to Hyper-V jobs.