Hyper-V Server Replica

Hyper-V Server replica technology accompanies the new release of Windows Server 2012, Hyper-V server 20,121, a free disaster recovery tool in Hyper-V 2012/R2 for creating and maintaining replicas of virtual machines (VMS). In the event of a catastrophic loss, the administrator can move to a replica virtual machine, guaranteeing business continuity. , which uses the Hyper-V Volume Shadow Copy Service (VSS) editor to transfer snapshot data for a virtual machine on the host to a secondary host.

In an enterprise, business continuity requires the ability to quickly restore business functions after downtime, minimizing the probability of data loss or even avoiding loss altogether. Business can cause disruptions for a variety of reasons, such as power outages, it hardware failures, network failures, human errors, it software failures, and natural disasters. Depending on the specific type of failure, the customer needs a highly available solution that can easily recover the service.

However, some failures can affect the entire data center, such as natural disasters or prolonged outages, which requires that the disaster recovery solution must be able to restore data at the remote site and restore the service to normal operation. Organizations need to recover from such failures as quickly as possible through low-cost but reliable business continuity solutions.

Starting with Windows Server R2, Hyper-V and failover clustering work together to provide high availability for virtual machines, minimizing disruption. In the event of a failure, administrators can seamlessly migrate virtual machines to other host hosts in the cluster, or load balance virtual machines, without affecting the proper functioning of virtualized applications. While these technical customers protect virtualized workloads from local host failures or are used for planned maintenance of host hosts in a cluster, there is no way to protect the business against failures that affect the entire data center. Although failover clustering can be used in conjunction with hardware-based SAN replication technology to provide protection for data centers, these are often very expensive methods. The new Hyper-V replica feature of Windows Server R2 provides a low-cost, built-in disaster recovery solution.

Hyper-V Replicas enable asynchronous replication of virtual machines for business continuity and disaster recovery. This asynchronous replication in Windows Server R2 is configurable, and administrators can choose from the following replication frequencies: 30 seconds, 5 minutes, and 15 minutes.

The activation of Hyper-V replicas is simple, using wizards, PowerShell, or System Center Virtual Machine Manager in Hyper-V manager. Once a replica is enabled for a specific virtual machine, initial replication can begin.

650) this.width=650; "height=" 413 "title=" clip_image002 "style=" margin:0px;border:0px;padding-top:0px; Padding-right:0px;padding-left:0px;background-image:none, "alt=" clip_image002 "src=" http://s3.51cto.com/wyfs02/ M02/58/55/wkiom1sub1ccohktaagpwaieqnu520.jpg "border=" 0 "/>

The initial replication can be done immediately, scheduled for later, or even exported to a USB drive before the copy can be started and delivered to the remote site. If the customer already has a backup of the source virtual machine at the remote site, it can also be used as the replication destination.

As seen in, the replica feature provides the most flexible way to replicate. Because this approach is software-based, there is no need to provide any special hardware in the site, not only flexible but also keep costs low. In addition to the latest recovery points, administrators can specify additional recovery points. In Windows Server R2, these recovery points can be configured for up to 24 hours of time. Administrators also have the flexibility to choose what to copy. For example, if a virtual machine has four virtual disks, but only three have important data saved, the fourth one can be excluded from replication, which saves network bandwidth and disk space usage.

Hyper-V replicas track write operations against primary virtual machines and efficiently replicate changes to replica servers over the WAN.

650) this.width=650; "height=" 414 "title=" clip_image004 "style=" margin:0px;border:0px;padding-top:0px; Padding-right:0px;padding-left:0px;background-image:none, "alt=" clip_image004 "src=" http://s3.51cto.com/wyfs02/ M00/58/52/wkiol1sucbpahs37aagwfjkrymg860.jpg "border=" 0 "/>

The network connection between the two servers uses the HTTP or HTTPS protocol to support Windows integration and certificate-based authentication. In order to encrypt the connection, you can select certificate-based authentication. Hyper-V replicas can also be tightly integrated with Windows failover clustering to provide simpler replication for different migration scenarios for primary and replica servers. With the ability to integrate with failover clusters, hyper-V replicas can fully understand live migration, ensuring that virtual machines can be copied correctly to the appropriate target site even if they are moved in a clustered environment.

650) this.width=650; "height=" 412 "title=" clip_image006 "style=" margin:0px;border:0px;padding-top:0px; Padding-right:0px;padding-left:0px;background-image:none, "alt=" clip_image006 "src=" http://s3.51cto.com/wyfs02/ M00/58/55/wkiom1sub1oja5_eaaeoekey_jm105.jpg "border=" 0 "/>

After a disaster, you can quickly recover and start a virtual machine at a secondary site, minimizing data loss and the probability of major application and load outages.

Some related concepts will be involved in performing the Hyper-V replica operation. The following is a brief introduction to the related terminology and concepts that explain Hyper-V replica technology.

1. Test applause transfer: The failover Test feature is only available on the backup virtual machine. After you start the failover test, a test virtual machine is created on the backup server to ensure that the virtual machine can function according to the selected recovery point during the failover test. It can be tested at any time without impacting production environment load.

2. Develop a failover plan: This operation is only available on the primary virtual machine. If you need to maintain the Hyper-V Primary server or, for some reason, need to transfer the load to a backup virtual machine, you should develop a failover plan.

3. Failover: Failover operations are only available on backup virtual machines, and when there are any problems with the primary virtual machine, the virtualization load can be transferred to the backup server through the failover feature.

4. Interrupt replication: This operation interrupts the current replication operation between the primary virtual machine and the backup virtual machine. An interrupt copy operation can be performed on both virtual machines.

5. Reverse replication: The reverse copy operation is only available on the backup virtual machine. The reverse copy operation can be found in the right-click menu on the backup virtual machine only if the failover schedule is initiated from the primary virtual machine, or when the failover process from the primary virtual machine to the backup virtual machine is caused by an incident. When the reverse copy operation is performed, the replication direction changes from the backup virtual machine to the primary virtual machine.

6. Cancel failover: Canceling the failover operation is used to cancel the current failover process. If you think that the backup virtual machine does not work after you fall back to a recovery point, canceling failover can help you undo the previous change, starting with a new recovery point.

7. Remove the replication point: Performing a remove replication point operation will cause all recovery points on the backup virtual machine to be removed. This can only be done if you think that all replication points will not be reused, or if you want to start a new replication cycle between the primary and backup virtual machines. This can only be done on a backup virtual machine.

8. Pause/Resume replication Suspend/Resume operations are available on both the primary and backup virtual machines. Pausing, as the name implies, pauses the copy operation between the primary and backup virtual machines. Typically, replication between the primary and backup virtual machines is paused when the primary Hyper-V server needs to be maintained.

9. View replication health: This operation is available on both virtual machines. The replication health query displays the overall replication health status of a specific virtual machine, including the replication increment that will be replicated to the backup virtual machine, any missing replication cycles, the last replication time, and so on.

This document demonstrates how to use Hyper-V replica to replicate a virtual machine from one physical server to another without shutting down the virtual machine.

1. Hyper-V replica is a feature of Hyper-V, and you must enable the Hyper-V server role to use this technology. Replicas also require virtual machines, so you also need to create one or more virtual machines.

2. Open Windows Firewall with Advanced Security, click Inbound Rules, right-click Hyper-V Replica HTTP listener (tcp-in), and then click Enable Rule. Right-click Hyper-V Replica HTTPS listener (tcp-in), and then click Enable Rule

650) this.width=650; "height=" 480 "title=" clip_image008 "style=" margin:0px;border:0px;padding-top:0px; Padding-right:0px;padding-left:0px;background-image:none, "alt=" clip_image008 "src=" http://s3.51cto.com/wyfs02/ M00/58/55/wkiom1sub1acmyenaame3ge1nv0419.jpg "border=" 0 "/>

3. Log in to Hyper-V Server "bj-vmhost-01" to open Hyper-V Manager

4. Right-click Hyper-V host name, select Hyper-V settings

650) this.width=650; "height=" 499 "title=" clip_image010 "style=" margin:0px;border:0px;padding-top:0px; Padding-right:0px;padding-left:0px;background-image:none, "alt=" clip_image010 "src=" http://s3.51cto.com/wyfs02/ M02/58/52/wkiol1sucbvcj5vsaahh810zreu062.jpg "border=" 0 "/>

5. Click Copy Configuration, tick enable this computer as a replica server, on the authentication and Ports page, specify the authentication type according to the actual requirements to allow incoming replication traffic

650) this.width=650; "height=" 391 "title=" clip_image012 "style=" margin:0px;border:0px;padding-top:0px; Padding-right:0px;padding-left:0px;background-image:none, "alt=" clip_image012 "src=" http://s3.51cto.com/wyfs02/ M01/58/52/wkiol1sucb2apemuaaiggzbjoho672.jpg "border=" 0 "/>

Enabled using Hyper-V PowerShell uses the

Enable-netfirewallrule-displayname "Hyper-V Replica HTTP Listener (tcp-in)"

When Kerberos authentication is used, the replicated data is not encrypted. Only certificate-based authentication encrypts data that is replicated during transmission.

6. Authorization and storage page, specifying a server that has permission to copy the virtual machine to this computer, optionally "Allow replication from any authenticated server" and "Allow replication from specified servers", depending on actual requirements

650) this.width=650; "height=" 413 "title=" clip_image014 "style=" margin:0px;border:0px;padding-top:0px; Padding-right:0px;padding-left:0px;background-image:none, "alt=" clip_image014 "src=" http://s3.51cto.com/wyfs02/ M01/58/55/wkiom1sub1zhk6yiaagdn1mehpc277.jpg "border=" 0 "/>

650) this.width=650; "height=" 297 "title=" clip_image016 "style=" margin:0px;border:0px;padding-top:0px; Padding-right:0px;padding-left:0px;background-image:none, "alt=" clip_image016 "src=" http://s3.51cto.com/wyfs02/ M00/58/55/wkiom1sub13b5s7uaaeoleja3tq808.jpg "border=" 0 "/>

7. Log on to another Hyper-V Server "bj-vmhost-02" to repeat the above actions to enable Hyper-V replica functionality

650) this.width=650; "height=" 426 "title=" clip_image018 "style=" margin:0px;border:0px;padding-top:0px; Padding-right:0px;padding-left:0px;background-image:none, "alt=" clip_image018 "src=" http://s3.51cto.com/wyfs02/ M01/58/52/wkiol1succcahfbbaajdni3lqmi605.jpg "border=" 0 "/>

8. Right-click the virtual machine "bj-server-01" and select Enable Replication

650) this.width=650; "height=" 499 "title=" clip_image020 "style=" margin:0px;border:0px;padding-top:0px; Padding-right:0px;padding-left:0px;background-image:none, "alt=" clip_image020 "src=" http://s3.51cto.com/wyfs02/ M00/58/52/wkiol1succlzevulaahkupmkh_o367.jpg "border=" 0 "/>

9. To enable the replication page for bj-ap-01, click Next

10. Specify the Replica server page, type the name of the replica server and click Next

650) this.width=650; "height=" 358 "title=" clip_image022 "style=" margin:0px;border:0px;padding-top:0px; Padding-right:0px;padding-left:0px;background-image:none, "alt=" clip_image022 "src=" http://s3.51cto.com/wyfs02/ M02/58/55/wkiom1sub2ogcazbaagdnyi1uos729.jpg "border=" 0 "/>

11. Specify the link Parameters page, specify the replica server, replica server port, authentication type, and tick use compression to transfer data over the network, click Next

650) this.width=650; "height=" 499 "title=" clip_image024 "style=" margin:0px;border:0px;padding-top:0px; Padding-right:0px;padding-left:0px;background-image:none, "alt=" clip_image024 "src=" http://s3.51cto.com/wyfs02/ M00/58/55/wkiom1sub2txunfvaagxqsmurne050.jpg "border=" 0 "/>

12. On the Select Replication VHD page, select the disks that the administrator does not want to replicate for the virtual machine, and then click Next. Once the operation is switched to a replica server, the disk containing data that is not necessary for the virtual machine to be run may be excluded from replication. VHDs that contain data that changes quickly after a failover and that the replica server no longer uses, such as paging file disks, should be excluded from replication to conserve network bandwidth.

650) this.width=650; "height=" "title=" clip_image026 "style=" margin:0px;border:0px;padding-top:0px; Padding-right:0px;padding-left:0px;background-image:none, "alt=" clip_image026 "src=" http://s3.51cto.com/wyfs02/ M01/58/55/wkiom1sub2wyk0kgaagdd9bbr5s579.jpg "border=" 0 "/>

13. Configure the replication frequency page, according to the actual environment choose to send changes to the replica server frequency, Hyper-V built-in 30 seconds, 5 minutes, 15 minutes, Hyper-V Server R2 added 30 seconds. Hyper-V default frequency 5 minutes

650) this.width=650; "height=" 383 "title=" clip_image028 "style=" margin:0px;border:0px;padding-top:0px; Padding-right:0px;padding-left:0px;background-image:none, "alt=" clip_image028 "src=" http://s3.51cto.com/wyfs02/ M02/58/52/wkiol1succjg6-26aafiqlpjphm312.jpg "border=" 0 "/>

14. Configure additional recovery point pages, the administrator can configure the replica to store only recently received replication data, and update the data on the replica server based on the replication frequency configured by the administrator. Administrators can also configure replicas to retain an additional one or more recovery points, which are created approximately once per hour. Having additional recovery points also allows administrators to restore virtual machine operations to an earlier point in time when the failover is performed. You can keep up to 15 (24 in Windows Server R2) for such a recovery point. Records the number of recovery points required by the administrator.

650) this.width=650; "height=" 418 "title=" clip_image030 "style=" margin:0px;border:0px;padding-top:0px; Padding-right:0px;padding-left:0px;background-image:none, "alt=" clip_image030 "src=" http://s3.51cto.com/wyfs02/ M00/58/52/wkiol1succnrev6haahybmou-jg923.jpg "border=" 0 "/>

15. Select the initial replication Method page, in order to begin copying data, the replica needs to transfer the current state of the virtual machine. This initial state can be transmitted directly through the existing network, either immediately or later, when the administrator configures it. Administrators can also use pre-existing restored virtual machines on the replica server (for example, if an administrator has restored an earlier backup of the virtual machines on the replica server) as the initial replica. Alternatively, the administrator can copy the initial copy to the external media and then physically deliver the media to the replica site, which can save network bandwidth. Records the initial replication method that the administrator plans to use.

1) The initial replication method can choose to send an initial copy over the network, send an initial copy using external media, and use an existing virtual machine on the replica server as the initial copy

2) Scheduled replication You can choose to start replication immediately and customize the time to start replication

650) this.width=650; "height=" 499 "title=" clip_image032 "style=" margin:0px;border:0px;padding-top:0px; Padding-right:0px;padding-left:0px;background-image:none, "alt=" clip_image032 "src=" http://s3.51cto.com/wyfs02/ M01/58/55/wkiom1sub2qa6fnyaaio2hh6ato616.jpg "border=" 0 "/>

16. Completing the "Enable Replication" page, click Finish to confirm the error and finish enabling Hyper-V Replication

650) this.width=650; "height=" 499 "title=" clip_image034 "style=" margin:0px;border:0px;padding-top:0px; Padding-right:0px;padding-left:0px;background-image:none, "alt=" clip_image034 "src=" http://s3.51cto.com/wyfs02/ M02/58/52/wkiol1succ-rjpe4aagmzwiviaw198.jpg "border=" 0 "/>

17. Return to Hyper-V Manager to view replication task progress

650) this.width=650; "height=" 384 "title=" clip_image036 "style=" margin:0px;border:0px;padding-top:0px; Padding-right:0px;padding-left:0px;background-image:none, "alt=" clip_image036 "src=" http://s3.51cto.com/wyfs02/ M01/58/55/wkiom1sub26xlksnaael3yy7in8722.jpg "border=" 0 "/>

18. Click Copy to view the replication information

650) this.width=650; "height=" 185 "title=" clip_image038 "style=" margin:0px;border:0px;padding-top:0px; Padding-right:0px;padding-left:0px;background-image:none, "alt=" clip_image038 "src=" http://s3.51cto.com/wyfs02/ M02/58/55/wkiom1sub2-aijumaacawrnmaog254.jpg "border=" 0 "/>

19. Open Task Manager, click Performance, select Ethernet, and view Network load during load

650) this.width=650; "height=" 499 "title=" clip_image040 "style=" margin:0px;border:0px;padding-top:0px; Padding-right:0px;padding-left:0px;background-image:none, "alt=" clip_image040 "src=" http://s3.51cto.com/wyfs02/ M00/58/52/wkiol1sucdptdeujaahjeq-rz1c287.jpg "border=" 0 "/>

20. Right-click on the replica's virtual machine, select Copy, tap "View Replication Health"

650) this.width=650; "height=" 445 "title=" clip_image042 "style=" margin:0px;border:0px;padding-top:0px; Padding-right:0px;padding-left:0px;background-image:none, "alt=" clip_image042 "src=" http://s3.51cto.com/wyfs02/ M00/58/52/wkiol1sucdwijps6aagsowklz0y327.jpg "border=" 0 "/>

650) this.width=650; "height=" 499 "title=" clip_image044 "style=" margin:0px;border:0px;padding-top:0px; Padding-right:0px;padding-left:0px;background-image:none, "alt=" clip_image044 "src=" http://s3.51cto.com/wyfs02/ M00/58/55/wkiom1sub3xshs66aaepbbitzey970.jpg "border=" 0 "/>

21. Log in to the replica server, open Hyper-V Manager, view the replicated virtual machine

650) this.width=650; "height=" 499 "title=" clip_image046 "style=" margin:0px;border:0px;padding-top:0px; Padding-right:0px;padding-left:0px;background-image:none, "alt=" clip_image046 "src=" http://s3.51cto.com/wyfs02/ M01/58/55/wkiom1sub3fbthoraahxekrihze049.jpg "border=" 0 "/>

22. Log on to the virtual machine "bj-ap-01", the file that is currently being copied for testing in the virtual machine

650) this.width=650; "height=" 442 "title=" clip_image047 "style=" margin:0px;border:0px;padding-top:0px; Padding-right:0px;padding-left:0px;background-image:none, "alt=" clip_image047 "src=" http://s3.51cto.com/wyfs02/ M02/58/55/wkiom1sub3us4bmmaajmzhzzr2y740.jpg "border=" 0 "/>

23. Right-click the replica-enabled virtual machine "bj-ap-01", select Replication, select "Scheduled failover cluster

650) this.width=650; "height=" 499 "title=" clip_image049 "style=" margin:0px;border:0px;padding-top:0px; Padding-right:0px;padding-left:0px;background-image:none, "alt=" clip_image049 "src=" http://s3.51cto.com/wyfs02/ M00/58/52/wkiol1suceca5izwaaidjowba9q735.jpg "border=" 0 "/>

24. The planned failover page, depending on whether you choose to change the replication direction to the opposite direction after failover, by default check "Start replica virtual machine after failover"

650) this.width=650; "height=" 494 "title=" clip_image051 "style=" margin:0px;border:0px;padding-top:0px; Padding-right:0px;padding-left:0px;background-image:none, "alt=" clip_image051 "src=" http://s3.51cto.com/wyfs02/ M00/58/55/wkiom1sub4ghlrq8aaig-0pgyei853.jpg "border=" 0 "/>

25. You need to shut down the virtual machine to perform a planned failover cluster

650) this.width=650; "height=" 492 "title=" clip_image053 "style=" margin:0px;border:0px;padding-top:0px; Padding-right:0px;padding-left:0px;background-image:none, "alt=" clip_image053 "src=" http://s3.51cto.com/wyfs02/ M02/58/55/wkiom1sub4pssdrcaai6e3hnlfm130.jpg "border=" 0 "/>

26. Click Fail-over to complete the failover

650) this.width=650; "height=" 492 "title=" clip_image055 "style=" margin:0px;border:0px;padding-top:0px; Padding-right:0px;padding-left:0px;background-image:none, "alt=" clip_image055 "src=" http://s3.51cto.com/wyfs02/ M01/58/55/wkiom1sub4egb8j6aaimobcwbpg891.jpg "border=" 0 "/>

27. Log on to the replica server "bj-vmhost-01" to open Hyper-V Manager, at which point the replica virtual machine will automatically boot

650) this.width=650; "height=" 383 "title=" clip_image057 "style=" margin:0px;border:0px;padding-top:0px; Padding-right:0px;padding-left:0px;background-image:none, "alt=" clip_image057 "src=" http://s3.51cto.com/wyfs02/ M02/58/52/wkiol1sucemjsi77aaemtysomug662.jpg "border=" 0 "/>

28. Login Replica Virtual machine "bj-ap-01", the file used for testing has been synchronized to the replica virtual machine

650) this.width=650; "height=" 353 "title=" clip_image059 "style=" border:0px;padding-top:0px;padding-right:0px; Padding-left:0px;background-image:none, "alt=" clip_image059 "src=" http://s3.51cto.com/wyfs02/M00/58/52/ Wkiol1sucevdnuwnaagt2qoepvc076.jpg "border=" 0 "/>

This article is from "Xu Ting Blog-Microsoft technology Sharing" blog, please be sure to keep this source http://ericxuting.blog.51cto.com/8995534/1600837

Hyper-V Server Replica