網頁

2013年3月7日 星期四

Hyper-V 3.0 --- Cancel or Reverse Replication if Planned failover fail (part 6)

In the Planned failover process, maybe it will be stopped due to some exception happen as the network connection suddenly interrupt or be unstable between Primary and Replica server. Drawing4
In the moment, we need to manually operate the rest action for roll back or go ahead to complete the pending task. ScreenHunter_06ScreenHunter_04
When the problem happens, please firstly view the related error message or event to realize what happen next to decide the next action. In the following scenario, although it cannot do the action “Reverse the replication direction”, all pending data has been replicated so that we can start VM on the Replica server now.ScreenHunter_01 Then the replication state is “Prepared for planned failover” on the primary server.ScreenHunter_02but the its status of Replica server is “Failover complete”.ScreenHunter_03At the moment, we have to quickly make a decision as “Cancel Replication” or “Reverse Replication” if the root cause can be resolved on the condition of Service Level Agreement (SLA).
Why? Because the VM status is power off so that the related Service never is supplied now!

Cancel Planned Replication
If we don’t know what happen and how to resolve this problem, I suggest that roll back to the original environment. That is “Cancel Planned Replication”.

How to do it?

In Hyper-V Manager of the Primary server, right-click  the offline VM next to select Replication and Cancel Planned Replication in menu.ScreenHunter_22Click Yes button to go aheadScreenHunter_23So does that the replication state will be changed from “Prepared for planned failover” to “Replication Error” and the replication health will also be corrected from “Normal” to “Critical”.ScreenHunter_24
In Hyper-V Manager of the Replica server, right-click  the offline VM next to select Replication and Cancel Failover in menu.ScreenHunter_27Click Yes button to go aheadScreenHunter_29So does that the replication state will be changed from “Failover complete” to “Replication enabled”.ScreenHunter_28
Return to the Primary server, right-click the offline VM again to select Replication and Resume Replication in menu.ScreenHunter_30So does that the replication state will be changed from “Replication Error” to “Replication enabled” and the replication health will also be corrected from “Critical” to “Warning”.ScreenHunter_31Now we can start this Offline VM on the primary server.ScreenHunter_33
Reverse Planned ReplicationIn this lab, I know why “Reverse the replication direction” fails because I disable deliberately the port 80 on the Primary Server. When I enable it on the Windows Firewall with Advanced SecurityScreenHunter_05
right-click this offline VM next to select Replication and Reverse Replication… in menu,ScreenHunter_06it will launch the Reverse Replication Wizard on the Replica server.
In the Before You Begin dialog, click Next > buttonScreenHunter_07In Specify Replica Server dialog, select one server to play a replica server role next to click Next > buttonScreenHunter_08In Specify Connection parameters dialog, we just can do clicking Next > button because other information cannot be changed.ScreenHunter_09In Configure Recovery History dialog, choose Additional recover points option next to change Number of additional recovery points to be stored, enable Replicate incremental VSS copy every hours based on our correction, and then click Next > button.ScreenHunter_10Click Finish button to complete the Reverse Replication WizardScreenHunter_11
If the above steps can be executed successfully, the replication information of the offline VM will be changed as Replication Type, Status, Health and current Primary or Replica Server on the original Replica Server.ScreenHunter_12the same status also appears on the original Primary Server.ScreenHunter_14Now we can start this Offline VM on the primary server.ScreenHunter_15
Finally, don’t forget to check replication health status again if complete either “Cancel Replication” or “Reverse Planned Replication”.

<<<   Hyper-V 3.0 --- Execute Planned Failover for Kerberos authentication on the same AD Domain (part 5)

沒有留言:

張貼留言

Since 2010 Design by Davidwa
©Copyright Davidwa Inc. All rights reserved.