locked
hyper v work group replica RRS feed

  • Question

  • I have hyper-v  work group replica enabled between 2 hosts which is working fine

    Now if I need to use the replicated machines on the second host, how do I start them? shutting down the machines on the primary replication host and starting the machines on the secondary? 

    or something else?

    I want to test my replicated machine for functionality for the moment i'll really need them

    Tuesday, July 2, 2019 8:54 AM

Answers

  • Hi,

    Good Day! And thanks for posting in our forum!

    I will share with you the links I used to refer to when learning Hyper-V Replica. I am sure it will give you some help and help you to have a new understanding of Hyper-V Replica.

    Reference Link:

    1. https://blogs.technet.microsoft.com/canitpro/2013/04/07/step-by-step-virtual-machine-replication-using-hyper-v-replica/

    2.  https://social.technet.microsoft.com/wiki/contents/articles/21948.hyper-v-replica-troubleshooting-guide.aspx#Enabling_replication

    3. https://www.petri.com/use-hyper-v-replica-broker-prepare-host-clusters

    4. https://www.red-gate.com/simple-talk/sysadmin/virtualization/a-practical-guide-to-microsoft-hyper-v-replica-part-i/

    5. https://www.red-gate.com/simple-talk/sysadmin/virtualization/a-practical-guide-to-microsoft-hyper-v-replica-part-ii/

    6.  http://ramprasadtech.com/wp-content/uploads/2016/06/Hyper-v-Repilcation-Failover-Theory.pdf

    7. http://www.aidanfinn.com/?p=14537

    In addition, here are some common questions about Hyper-V Replica that I have organized for your reference.

    1. Describe the configuration of Hyper-V Replica.

    Enabling Replication on the Replica Server:

    • In Server Manager, click Tools, and then click Hyper-V Manager.
    • In the Actions pan, click Connect to Server (right pane), type ServerName, and then click OK.  (or just click the server name if it is already there)
    • Click Hyper-V Manager.
    • Click ServerName.
    • Click Hyper-V Settings(right pane)
    • Click Replication Configuration(left pane)
    • Turn on Checkbox to “Enable this computer as a Replica server”
    • Make sure Use Kerberos (HTTP): is checked Specify the port:  80
    • Click Allow replication from any authenticated server
    • Type the location you would like to put replicas
    • Click OK

    Initial Virtual Machine Replication:

    • In Hyper-V Manager, Select the Virtual Machine you wish to replicate
    • In Task Pane (right Pane) select Enable Replication (this is also available on the right click menu)
    • Click Next on Before You Begin
    • Type or Browse to the Replica Server (remember, this is the name of the destination server that will receive the replica) then Click Next
    • Make sure Compress the data that is transmitted over the network is turned ON then Click Next
    • Replica Server Authentication – After Replica server for virtual machine replication is enabled, configuration of specific authentication types and ports for incoming replication traffic is required.
    • Two authentication options are available. Kerberos authentication (using HTTP), which does not allow the data you send across the network will not be encrypted or certificate-based authentication (using HTTPS), which does encrypt the data sent across the network.
    • Chose Recovery History options as desired (ex. Additional Recover Points = 4, Replicate incremental VSS every 4 hours)

    Recovery points contain one or more snapshots. The options presented allow for keeping the latest recovery point for restoring your primary virtual machine on the Replica server, or allow the ability to maintain multiple recovery points on your server. When choosing the multiple recovery points option, remember that more storage would be required on the Replica server. Additionally, when specification at to the number of recovery points is utilized, the Enable Replication Wizard specifies how much storage is needed. Recovery points are created every hour, but the Replica server receives frequent and regular changes from the primary server, so that your primary and Replica servers stay synchronized.

    • Click Send initial copy over the network and Start replication immediately then Click Next
    • Turn on the drives you want to replicate then Click Finish

    2. Describe the requirements about Hyper-V Replica.

    • Hardware that supports the Hyper-V role on Windows Server 2012. Keep in mind that hardware-assisted virtualization is available in processors that include a virtualization option—specifically processors with Intel Virtualization Technology (Intel VT) or AMD Virtualization (AMD-V) technology. In addition, hardware-enforced Data Execution Prevention (DEP) must be available and enabled.
    • Sufficient storage on both the primary server and Replica server to host the files used by virtualized workloads.
    • Network connectivity between the locations hosting the primary and Replica servers.
    • Properly configured firewall rules to permit replication between the primary and Replica sites.
    • You need to use certificate-based authentication if you want transmitted data to be encrypted. Use an X.509 v3 certificate to support mutual authentication with certificates.

    3. Why the function can be enable after Windows Server 2012?

    When it comes to high-availability in Hyper-V Server 2012, two options are available:

    • Quick migration – this option was already available in Windows Server 2008 and is built on top of Windows failover-clustering. Basically it is a failover cluster where the Virtual Machines are configured as cluster resources. In the case of a failover, the Virtual Machines are stopped, they failover to the other cluster node and are started again. This always comes with some downtime;
    • Live migration – Live migration was introduced in Windows Server 2008 R2 and is also built on top of Windows failover-clustering. In this case, a failover cluster is built and, again, the Virtual Machines are cluster resources as well. But in a failover, the VMs do not stop but keep running during the failover. The entire running machine is brought to the other cluster node without any downtime.

    Both options are intended to improve availability for Hyper-V but there still is no rapid Disaster Recovery with either of them. To make good this omission, Windows Server 2012 brings a rapid Disaster Recovery solution by means of Hyper-V Replica. 

    4. Which port is used for HTTP and which port is used for HTTPS? Can these port numbers be changed?

    HTTP Port: 80

    HTTPS Port: 443

    We can change these Port number.

    5. Which are firewall exception about Hyper-V Replica?

    Hyper-V Replica HTTP Listener(TCP-In)

    Hyper-V Replica HTTPS Listener(TCP-In)

    6. Why we need to select VHD during enable replication?

    The Virtual Machine configuration file (XML) will be replicated to the Replica Server in any case but if you select VHD files unnecessarily, it will put extra overhead on the Replication Engine on the Primary Server and more network bandwidth will be used for a VHD file which need not be replicated. The wizard cannot work out which VHD file belongs to the Operating System and which one belongs to the data. You might have noticed that “Choose Replication VHDs” configuration page talks about excluding the “Paging file”. Well, you can configure a second VHD on the IDE controller and move the paging file to that location and then do not select the paging file VHD during “Choose Replication VHDs” configuration page.

    All VHD files including paging VHD file must be replicated once. Once the initial replication is completed, break and re-enable the replication but this time, do not select the paging VHD file. This way, the paging file VHD will not be replicated to the Replica Server which saves a lot of bandwidth.

    7. How many types of the operation in Hyper-V replica failover operations?

    For any Primary and Replica Virtual Machine in a Hyper-V Replica environment, there are three types of failover operations available. Some of the failover tests can be used for the Primary Virtual Machine and some can be used for Replica Virtual Machine.

    • Test Failover (TFO)
    • Planned Failover (PFO)
    • Unplanned Failover (UFO)

    Reference link:

    https://www.red-gate.com/simple-talk/sysadmin/virtualization/a-practical-guide-to-microsoft-hyper-v-replica-part-ii/

    8. What is the difference between Hyper-V Replica and Live Migration?

    Live Migration is a synchronous replication, Hyper-V Replica is an asynchronous synchronous replication, Live Migration has only one data, Hyper-V Replica has two data.

    9. What is the difference between Hyper-V Replica and export/import VM?

    Export and import virtual machines can only copy the current state of virtual machines, can not be updated, and there is no disaster recovery function.

    Hope this can help you, if you think it is useful, please help me mark the reply as an answer, thank you very much!

    Best Regards,

    Daniel


    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Wednesday, July 3, 2019 2:30 AM

All replies

  • Hello,

    Hyper-V Replica allows you to fail over to a protected virtual machine on the Replica server at any
    time, there are three (3) main options you need to understand for failover operations.


    1. Planned Failover to a Replica Server

    A planned failover operation enables you to fail over your production virtual machine to a Replica server as part of a predetermined schedule. You might want to do this for multiple reasons—for example, to test the state of your Replica virtual machine. This allows you to make appropriate arrangements in your organization if they are required. We recommend that you perform planned failovers for off-business hours.

    There are several prerequisites when you perform a planned failover. Your virtual machine must not be running, and your server running Hyper-V at the primary site must be enabled to receive replication traffic from the Replica
    server. Keep in mind that a planned failover also initiates a “reverse replication.” Reverse replication is the process where replication is established from a virtual machine that was formerly a Replica virtual machine, but is now a primary virtual machine as the result of a failover.

    2. Test Failover to a Replica Server

    Hyper-V Replica is continually updating the Replica server to ensure that the primary virtual machine matches the Replica virtual machine as closely as possible. If you want to, you can test a Replica virtual machine on the Replica server. You can conduct a test failover operation at any time without interrupting ongoing replication. This process creates and starts a virtual machine with the name “<virtual machine name> – Test”.

    3. Unplanned Failover to a Replica Server

    In the event of a failure in the primary site, you can bring up the Replica virtual machine on the Replica server. When you configured your Replica server in the Enable Replication Wizard, you had the option of specifying multiple recovery points. Now, you can select the one you require to restore the specified the virtual machine.

    Reference:
    Step-By-Step: Virtual Machine Replication Using Hyper-V Replica

    Best regards,
    Leon


    Blog: https://thesystemcenterblog.com LinkedIn:

    Tuesday, July 2, 2019 9:04 AM
  • Hi,

    Good Day! And thanks for posting in our forum!

    I will share with you the links I used to refer to when learning Hyper-V Replica. I am sure it will give you some help and help you to have a new understanding of Hyper-V Replica.

    Reference Link:

    1. https://blogs.technet.microsoft.com/canitpro/2013/04/07/step-by-step-virtual-machine-replication-using-hyper-v-replica/

    2.  https://social.technet.microsoft.com/wiki/contents/articles/21948.hyper-v-replica-troubleshooting-guide.aspx#Enabling_replication

    3. https://www.petri.com/use-hyper-v-replica-broker-prepare-host-clusters

    4. https://www.red-gate.com/simple-talk/sysadmin/virtualization/a-practical-guide-to-microsoft-hyper-v-replica-part-i/

    5. https://www.red-gate.com/simple-talk/sysadmin/virtualization/a-practical-guide-to-microsoft-hyper-v-replica-part-ii/

    6.  http://ramprasadtech.com/wp-content/uploads/2016/06/Hyper-v-Repilcation-Failover-Theory.pdf

    7. http://www.aidanfinn.com/?p=14537

    In addition, here are some common questions about Hyper-V Replica that I have organized for your reference.

    1. Describe the configuration of Hyper-V Replica.

    Enabling Replication on the Replica Server:

    • In Server Manager, click Tools, and then click Hyper-V Manager.
    • In the Actions pan, click Connect to Server (right pane), type ServerName, and then click OK.  (or just click the server name if it is already there)
    • Click Hyper-V Manager.
    • Click ServerName.
    • Click Hyper-V Settings(right pane)
    • Click Replication Configuration(left pane)
    • Turn on Checkbox to “Enable this computer as a Replica server”
    • Make sure Use Kerberos (HTTP): is checked Specify the port:  80
    • Click Allow replication from any authenticated server
    • Type the location you would like to put replicas
    • Click OK

    Initial Virtual Machine Replication:

    • In Hyper-V Manager, Select the Virtual Machine you wish to replicate
    • In Task Pane (right Pane) select Enable Replication (this is also available on the right click menu)
    • Click Next on Before You Begin
    • Type or Browse to the Replica Server (remember, this is the name of the destination server that will receive the replica) then Click Next
    • Make sure Compress the data that is transmitted over the network is turned ON then Click Next
    • Replica Server Authentication – After Replica server for virtual machine replication is enabled, configuration of specific authentication types and ports for incoming replication traffic is required.
    • Two authentication options are available. Kerberos authentication (using HTTP), which does not allow the data you send across the network will not be encrypted or certificate-based authentication (using HTTPS), which does encrypt the data sent across the network.
    • Chose Recovery History options as desired (ex. Additional Recover Points = 4, Replicate incremental VSS every 4 hours)

    Recovery points contain one or more snapshots. The options presented allow for keeping the latest recovery point for restoring your primary virtual machine on the Replica server, or allow the ability to maintain multiple recovery points on your server. When choosing the multiple recovery points option, remember that more storage would be required on the Replica server. Additionally, when specification at to the number of recovery points is utilized, the Enable Replication Wizard specifies how much storage is needed. Recovery points are created every hour, but the Replica server receives frequent and regular changes from the primary server, so that your primary and Replica servers stay synchronized.

    • Click Send initial copy over the network and Start replication immediately then Click Next
    • Turn on the drives you want to replicate then Click Finish

    2. Describe the requirements about Hyper-V Replica.

    • Hardware that supports the Hyper-V role on Windows Server 2012. Keep in mind that hardware-assisted virtualization is available in processors that include a virtualization option—specifically processors with Intel Virtualization Technology (Intel VT) or AMD Virtualization (AMD-V) technology. In addition, hardware-enforced Data Execution Prevention (DEP) must be available and enabled.
    • Sufficient storage on both the primary server and Replica server to host the files used by virtualized workloads.
    • Network connectivity between the locations hosting the primary and Replica servers.
    • Properly configured firewall rules to permit replication between the primary and Replica sites.
    • You need to use certificate-based authentication if you want transmitted data to be encrypted. Use an X.509 v3 certificate to support mutual authentication with certificates.

    3. Why the function can be enable after Windows Server 2012?

    When it comes to high-availability in Hyper-V Server 2012, two options are available:

    • Quick migration – this option was already available in Windows Server 2008 and is built on top of Windows failover-clustering. Basically it is a failover cluster where the Virtual Machines are configured as cluster resources. In the case of a failover, the Virtual Machines are stopped, they failover to the other cluster node and are started again. This always comes with some downtime;
    • Live migration – Live migration was introduced in Windows Server 2008 R2 and is also built on top of Windows failover-clustering. In this case, a failover cluster is built and, again, the Virtual Machines are cluster resources as well. But in a failover, the VMs do not stop but keep running during the failover. The entire running machine is brought to the other cluster node without any downtime.

    Both options are intended to improve availability for Hyper-V but there still is no rapid Disaster Recovery with either of them. To make good this omission, Windows Server 2012 brings a rapid Disaster Recovery solution by means of Hyper-V Replica. 

    4. Which port is used for HTTP and which port is used for HTTPS? Can these port numbers be changed?

    HTTP Port: 80

    HTTPS Port: 443

    We can change these Port number.

    5. Which are firewall exception about Hyper-V Replica?

    Hyper-V Replica HTTP Listener(TCP-In)

    Hyper-V Replica HTTPS Listener(TCP-In)

    6. Why we need to select VHD during enable replication?

    The Virtual Machine configuration file (XML) will be replicated to the Replica Server in any case but if you select VHD files unnecessarily, it will put extra overhead on the Replication Engine on the Primary Server and more network bandwidth will be used for a VHD file which need not be replicated. The wizard cannot work out which VHD file belongs to the Operating System and which one belongs to the data. You might have noticed that “Choose Replication VHDs” configuration page talks about excluding the “Paging file”. Well, you can configure a second VHD on the IDE controller and move the paging file to that location and then do not select the paging file VHD during “Choose Replication VHDs” configuration page.

    All VHD files including paging VHD file must be replicated once. Once the initial replication is completed, break and re-enable the replication but this time, do not select the paging VHD file. This way, the paging file VHD will not be replicated to the Replica Server which saves a lot of bandwidth.

    7. How many types of the operation in Hyper-V replica failover operations?

    For any Primary and Replica Virtual Machine in a Hyper-V Replica environment, there are three types of failover operations available. Some of the failover tests can be used for the Primary Virtual Machine and some can be used for Replica Virtual Machine.

    • Test Failover (TFO)
    • Planned Failover (PFO)
    • Unplanned Failover (UFO)

    Reference link:

    https://www.red-gate.com/simple-talk/sysadmin/virtualization/a-practical-guide-to-microsoft-hyper-v-replica-part-ii/

    8. What is the difference between Hyper-V Replica and Live Migration?

    Live Migration is a synchronous replication, Hyper-V Replica is an asynchronous synchronous replication, Live Migration has only one data, Hyper-V Replica has two data.

    9. What is the difference between Hyper-V Replica and export/import VM?

    Export and import virtual machines can only copy the current state of virtual machines, can not be updated, and there is no disaster recovery function.

    Hope this can help you, if you think it is useful, please help me mark the reply as an answer, thank you very much!

    Best Regards,

    Daniel


    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Wednesday, July 3, 2019 2:30 AM
  • Hi,
    Just checking in to see if the information provided was helpful. Please let us know if you would like further assistance.
    Best Regards,
    Daniel

    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Friday, July 5, 2019 1:54 AM
  • Hello,

    I'm Daniel. I hope everything goes well with you recently.

    I'm working on ending every post with "marked as an answer" to better help other people in the community with the same questions find answers quickly.

    If my answer above is helpful to your question, would you please help me  mark it as an answer? If unfortunately, my reply is not helpful to you or if you need further help from me, please feel free to reply to me at any time.

    Thank you again for your support of my work!
    Best wishes,
    Daniel




    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Monday, July 15, 2019 6:27 AM