There are two types of virtual machines involved in the Hyper-V Replica configuration: primary and replica virtual...
By submitting your personal information, you agree that TechTarget and its partners may contact you regarding relevant content, products and special offers.
machines. The replication of the virtual machine's contents take place from primary to a replica VM running on a Hyper-V Replica Server. There are a handful of actions available on the right click context menu of both primary and replica VMs. However, there are a few actions that are available only on just either the primary VM or the replica VM.
Test failover is available on the replica VM. The test failover action, when executed, creates a test VM on the replica server to ensure VM can be brought online using the recovery points you select during the test failover. It can be executed any time without affecting the production workloads.
This action is available only on the primary VM. Planned failover is executed in case of any maintenance activities at the Hyper-V Primary Server or you need to intentionally failover to replica VM.
The failover action, which is available on the replica VM, is executed to bring the virtualized workloads at replica server in case of any disasters with the primary VM.
This action breaks the replication between primary and replica VMs. Remove replication can be executed from either of the VMs.
Reverse replication action is available only on the replica VM. You will see reverse replication action on the right click context menu of the replica VM only if a planned failover was initiated from the primary VM or from an event that caused the failover from primary VM to replica VM. Once reverse replication action is executed, the replication direction changes from replica VM to primary VM.
The cancel failover action is executed to cancel the current failover. If you think the replica VM is not working after applying the recovery point, the cancel failover helps you revert back the changes and start over with a new recovery point.
Remove replication points
Executing this action causes all recovery points to be removed from the replica VM. Execute remove replication points action only if you think recovery points will no longer be needed or you want to start a fresh replication cycle between primary and replica VMs. This action is executed on the replica VM.
The pause/resume action is available on both the primary and replica VMs. As the name suggests, the pause action pauses the replication between primary and replica VMs. Generally, you pause the replication between primary and replica VMs in case of any maintenance activity at the Primary Hyper-V server.
View replication health
This action is available on both the VMs. Executing the view replication health action will show you the overall replication health of a particular virtual machine including replication delta to be replicated to replica VM, any missed replication cycles, last time the replication took place, etc.
It is important to understand that when the failover takes place, the replication direction changes which causes replica VM to act as primary VM and vice-versa. This would also change the actions on the right click context menu of both the VMs.
Dig Deeper on Microsoft Hyper-V management
Related Q&A from Nirmal Sharma
System Center Orchestrator provides Run .Net Script activity, which can be used to call PowerShell scripts, but there are limitations you should know.continue reading
By referencing various log files, like the Real-Time Log and the Historic Log, and checking the Orchestrator Runbook Audit History page, you can more...continue reading
To execute custom scripts for Azure Windows and Linux VMs to support post-deployment configurations, you'll have to download the Azure Custom Script ...continue reading
Have a question for an expert?
Please add a title for your question
Get answers from a TechTarget expert on whatever's puzzling you.