Hyper-V Replica Explained – Part 511
In Part 1 and Part 2 of this article series, we learned the basics of Hyper-V Replica and benefits it provides for small and medium sized businesses. In Part 3, we learned how to install and configure it in a production environment and Part 4 explained how Hyper-V Replica is not a replacement for backup. In the final part of this article series, we are going to learn about the types of failover which are available with Hyper-V Replica.
The other parts of this series are:
- Part 1: Overview and benefits of using Hyper-V Replica
- Part 2: Requirements and facts of Hyper-V Replica
- Part 3: Enabling and configuring Hyper-V Replica
- Part 4: Virtual Machine Backup Vs Hyper-V Replica
The concept of Hyper-V Replica starts from learning how to enable Hyper-V Replica on a Hyper-V Server to how to configure a virtual machine for replication. But that is just how to enable and configure Hyper-V Replica. There is much more to talk about, for example how different types of failover are available and how to use them.
When you need to bring a virtual machine online at Replica Site, you use something called “failover”. There are three types of failover available with Hyper-V Replica as listed below:
- Test Failover
- Planned Failover
- Unplanned Failover
Test Failover, as the name suggests, can be used to test the virtualized workloads on the Replica Server. This is to ensure the Replica Virtual Machine can be brought online at the Replica Server in case of any disaster with Primary Virtual Machine.
Test Failover creates a Test Virtual Machine on the Replica Server. The new virtual machine created by the Test Failover process is appended with tag “Test”. You can always turn the Test virtual machine ON to ensure it is functioning properly. Once you are satisfied that virtual machine is working properly, you can stop the test failover by clicking Stop-Test Failover from Right Click context menu on Replica Virtual Machine.
Test Failover is always executed at Replica Server and is available as “Test Failover” action on the Right Click Context menu of the Virtual Machine as shown in the below screenshot:
Planned Failover is initiated manually by an administrator to move the virtualized workloads from Primary Server to Replica Server. Planned Failover is used when you have maintenance window opened for Primary Site and it needs to go down for some maintenance activities.
Planned Failover performs the some perpetuities before the failover can take place. This includes checking the ability for Replica Server to become as Primary Server also. This is required in order to move the virtualized workloads back to Primary Server.
Note: “Planned Failover” is always executed at Primary Server.
Unplanned event occurs when something goes wrong at the Primary Site or in other words Primary Virtual Machine will stop functioning.
Unplanned Failover appears as “Failover” on the Right Click context menu of the Replica Virtual Machine as shown in the below screenshot:
Clicking the “Failover” allows you to recover the Replica Virtual Machine using the recovery history of your choice. You will be presented with the list of recovery points for your selection as shown in the below screenshot:
If the Replica Virtual Machine does not come online using one of the recovery points you select, you can always use “Cancel Failover” and try with a different recovery point.
Note: Unplanned Failover is always executed at the Replica Server.
In this series, we learned from the benefits of using Hyper-V Replica to different types of failover available with it. We learned how Hyper-V Replica is useful for small and medium sized businesses to reduce the overall cost when it comes to setting up an environment which includes SAN devices.
Have any questions or feedback?
Leave a comment below!