Hyper-V Server replica technology

Hyper-V Server replica technology

I'm going to talk to you today. Hyper-V Replica technology, Hyper-V replica technology is a new feature of Microsoft in Windows Server 2012. The Hyper-V replica feature enables administrators to make virtual machines (VMS) replicate over the network asynchronously for disaster recovery purposes. If a disaster occurs in one of the main stations, you can quickly replicate the VM copy of the site to keep the business running, as we saw in the following diagram:

650) this.width=650; "height=" 261 "title=" clip_image001 "style=" Border-top:0px;border-right:0px;background-image: none;border-bottom:0px;padding-top:0px;padding-left:0px;border-left:0px;padding-right:0px; "alt=" clip_image001 " Src= "Http://s3.51cto.com/wyfs02/M02/79/91/wKiom1aUu9TyKw46AAFhCyuHUGY686.png" border= "0"/>

Hyper-V replica is a free disaster recovery tool in Hyper-V 2012/R2 and is a disaster recovery solution, not a highly available solution. This means that if the primary site fails, the administrator will need to manually restore the offsite virtual machine copy to ensure business continuity. In a highly available solution (using multi-site cluster failover), if the primary site fails, the virtual machines are automatically replicated offsite for recovery without human intervention. Hyper-V uses the Hyper-V Volume Shadow Copy Service (VSS) editor to transfer snapshot data for a virtual machine on a host to a secondary host.

In an enterprise, the continuity of business requires the system to be able to quickly resume business after downtime and minimize the probability of data loss. Disruption of business can occur for a variety of reasons, such as engine room power outages, server hardware failures, network failures, software failures, and irresistible natural disasters. Depending on the specific type of failure, the customer needs a disaster recovery solution that can easily recover the service.

For a natural disaster or a long-term outage of the engine room, this failure can affect the entire data center, which requires a disaster recovery solution that enables data restoration in a remote datacenter to restore the normal operation of the service. Starting with Windows Server R2, Hyper-V and failover clustering can be used together to provide high availability for virtual machines, minimizing service outages. 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 technologies can protect virtualized workloads from local host failures, or are used for planned maintenance of host hosts in a cluster, protection and prevention can affect the overall data center failure. Although failover clustering can be used in conjunction with hardware-based SAN replication technology to provide protection for data centers, such approaches are often expensive.

The new Hyper-V replica feature of Windows Server 2012 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.

Prerequisite conditions for using Hyper-V replicas:

As long as these two sites are connected over the network and running server-V at the same time, there is no need for any complex settings, which would be a good disaster recovery solution. Hyper-V replicas apply only to server 2012 and are not in the Hyper-V client. To take full advantage of Hyper-V replicas, you must meet the criteria:

1. Your hardware must support Hyper-V in a server 2012 environment

2. Your primary and replica servers must have sufficient storage space and physical memory to run the virtual machine

3. The network connection between the primary server and the replica server must be guaranteed

4. Properly configure firewall rules, you must allow replication between the master and replica sites

5. You must have a X.509v3 certificate to support mutual authentication (if required)

Ok, say so much, let's look at how to configure Hyper-V replica:

1. Open Windows Advanced Firewall: 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=" 427 "title=" image "style=" border-top:0px;border-right:0px;background-image:none; border-bottom:0px;padding-top:0px;padding-left:0px;border-left:0px;padding-right:0px; "alt=" image "src=" http:// S3.51cto.com/wyfs02/m02/79/91/wkiom1auu9nwbrcpaakw4syrwhg865.png "border=" 0 "/>

2. Log in to HV-01, open Hyper-V Manager, and click on "Hyper-V settings"

650) this.width=650; "height=" "title=" image "style=" border-top:0px;border-right:0px;background-image:none; border-bottom:0px;padding-top:0px;padding-left:0px;border-left:0px;padding-right:0px; "alt=" image "src=" http:// S3.51cto.com/wyfs02/m02/79/8f/wkiol1auvavq6-6maadnhqnbzhy925.png "border=" 0 "/>

3. Click "Copy Configuration", tick enable this computer as a replica server, on the authentication and Port page, specify the authentication type according to the actual requirements to allow incoming replication traffic. On the Authorization and Storage page, specify the server that has permission to copy the virtual machine to this computer, optionally "Allow replication from any authenticated server" and "Allow replication from the specified server" as shown in:

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

650) this.width=650; "height=" 484 "title=" image "style=" border-top:0px;border-right:0px;background-image:none; border-bottom:0px;padding-top:0px;padding-left:0px;border-left:0px;padding-right:0px; "alt=" image "src=" http:// S3.51cto.com/wyfs02/m00/79/91/wkiom1auu96an7rsaaggpt4dfqa932.png "border=" 0 "/>

Repeat the above on the HV-02, such as:

650) this.width=650; "height=" 484 "title=" image "style=" border-top:0px;border-right:0px;background-image:none; border-bottom:0px;padding-top:0px;padding-left:0px;border-left:0px;padding-right:0px; "alt=" image "src=" http:// S3.51cto.com/wyfs02/m01/79/91/wkiom1auu-gdahmcaaf7c0uc9l8681.png "border=" 0 "/>

4, set to complete the HV-01 in the Hyper-V manager after the right mouse button virtual machine vm-test, click Enable Replication:

650) this.width=650; "height=" 274 "title=" image "style=" border-top:0px;border-right:0px;background-image:none; border-bottom:0px;padding-top:0px;padding-left:0px;border-left:0px;padding-right:0px; "alt=" image "src=" http:// S3.51cto.com/wyfs02/m00/79/8f/wkiol1auvbsyv6waaad9lnshzjy898.png "border=" 0 "/>

5. Before you start the page, click Next:

650) this.width=650; "height=" 484 "title=" image "style=" border-top:0px;border-right:0px;background-image:none; border-bottom:0px;padding-top:0px;padding-left:0px;border-left:0px;padding-right:0px; "alt=" image "src=" http:// S3.51cto.com/wyfs02/m02/79/91/wkiom1auu-fribzmaaer072mmus242.png "border=" 0 "/>

6, specify the replica server, click Next:

650) this.width=650; "height=" 484 "title=" image "style=" border-top:0px;border-right:0px;background-image:none; border-bottom:0px;padding-top:0px;padding-left:0px;border-left:0px;padding-right:0px; "alt=" image "src=" http:// S3.51cto.com/wyfs02/m00/79/91/wkiom1auu-mj7ux1aad_6u2kfsu806.png "border=" 0 "/>

7. Specify the link Parameters page, specify the replica server, replica server port, authentication type, and tick transfer data over the network using compression, click Next:

650) this.width=650; "height=" 484 "title=" image "style=" border-top:0px;border-right:0px;background-image:none; border-bottom:0px;padding-top:0px;padding-left:0px;border-left:0px;padding-right:0px; "alt=" image "src=" http:// S3.51cto.com/wyfs02/m02/79/91/wkiom1auu-6xbf-zaae55age8p4806.png "border=" 0 "/>

8. On the Select Replication VHD page, select the disk that the administrator does not want to copy 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=" 484 "title=" image "style=" border-top:0px;border-right:0px;background-image:none; border-bottom:0px;padding-top:0px;padding-left:0px;border-left:0px;padding-right:0px; "alt=" image "src=" http:// S3.51cto.com/wyfs02/m02/79/8f/wkiol1auvcdjutlraaehyfkmaqi722.png "border=" 0 "/>

9, in the Configuration 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. The Hyper-V default replication frequency is 5 minutes:

650) this.width=650; "height=" 288 "title=" image "style=" border-top:0px;border-right:0px;background-image:none; border-bottom:0px;padding-top:0px;padding-left:0px;border-left:0px;padding-right:0px; "alt=" image "src=" http:// S3.51cto.com/wyfs02/m00/79/91/wkiom1auu_lsvgbeaacn6fb_83a370.png "border=" 0 "/>

10. To 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=" 319 "title=" image "style=" border-top:0px;border-right:0px;background-image:none; border-bottom:0px;padding-top:0px;padding-left:0px;border-left:0px;padding-right:0px; "alt=" image "src=" http:// S3.51cto.com/wyfs02/m01/79/91/wkiom1auu_sdbug-aae3f8ymvjk931.png "border=" 0 "/>

11. 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 the initial copy over the network, send the initial copy using external media, and use the 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=" 484 "title=" image "style=" border-top:0px;border-right:0px;background-image:none; border-bottom:0px;padding-top:0px;padding-left:0px;border-left:0px;padding-right:0px; "alt=" image "src=" http:// S3.51cto.com/wyfs02/m02/79/91/wkiom1auu_eit3q9aagejxeysfq902.png "border=" 0 "/>

12, confirm the error, click Finish:

650) this.width=650; "height=" 484 "title=" image "style=" border-top:0px;border-right:0px;background-image:none; border-bottom:0px;padding-top:0px;padding-left:0px;border-left:0px;padding-right:0px; "alt=" image "src=" http:// S3.51cto.com/wyfs02/m02/79/91/wkiom1auu_qd71_maaefgwx-lgo974.png "border=" 0 "/>

After the configuration is complete, you can return to Hyper-V Manager to see the replication progress:

650) this.width=650; "height=" "title=" image "style=" border-top:0px;border-right:0px;background-image:none; border-bottom:0px;padding-top:0px;padding-left:0px;border-left:0px;padding-right:0px; "alt=" image "src=" http:// S3.51cto.com/wyfs02/m00/79/8f/wkiol1auvczdltlpaadcpqepo-w968.png "border=" 0 "/>

You can also view replication information:

650) this.width=650; "height=" 221 "title=" image "style=" border-top:0px;border-right:0px;background-image:none; border-bottom:0px;padding-top:0px;padding-left:0px;border-left:0px;padding-right:0px; "alt=" image "src=" http:// S3.51cto.com/wyfs02/m01/79/8f/wkiol1auvc6cduc0aabvxaxli-a029.png "border=" 0 "/>

The right mouse button has been enabled for the replicated virtual machine, click "Copy"--"View copy run status":

650) this.width=650; "height=" 337 "title=" image "style=" border-top:0px;border-right:0px;background-image:none; border-bottom:0px;padding-top:0px;padding-left:0px;border-left:0px;padding-right:0px; "alt=" image "src=" http:// S3.51cto.com/wyfs02/m02/79/8f/wkiol1auvdhaixhxaafqmyhyszc113.png "border=" 0 "/>

You can see the current replication run as follows:

650) this.width=650; "height=" 536 "title=" image "style=" border-top:0px;border-right:0px;background-image:none; border-bottom:0px;padding-top:0px;padding-left:0px;border-left:0px;padding-right:0px; "alt=" image "src=" http:// S3.51cto.com/wyfs02/m00/79/8f/wkiol1auvdozlaugaac_cg61vdg736.png "border=" 0 "/>

At this point we log on to the replica server and open Hyper-V Manager to view virtual machine replication:

650) this.width=650; "height=" 431 "title=" image "style=" border-top:0px;border-right:0px;background-image:none; border-bottom:0px;padding-top:0px;padding-left:0px;border-left:0px;padding-right:0px; "alt=" image "src=" http:// S3.51cto.com/wyfs02/m01/79/91/wkiom1auvaitpy2saaep7kiusx4073.png "border=" 0 "/>

Log in to the virtual machine "vm-test" in which to create a new file for testing:

650) this.width=650; "height=" 232 "title=" image "style=" border-top:0px;border-right:0px;background-image:none; border-bottom:0px;padding-top:0px;padding-left:0px;border-left:0px;padding-right:0px; "alt=" image "src=" http:// S3.51cto.com/wyfs02/m01/79/8f/wkiol1auvdvywf-qaabjtwf8ha4579.png "border=" 0 "/>

After the new completion, close the test virtual machine, then right click on "Copy"--"planned failover":

650) this.width=650; "height=" "title=" image "style=" border-top:0px;border-right:0px;background-image:none; border-bottom:0px;padding-top:0px;padding-left:0px;border-left:0px;padding-right:0px; "alt=" image "src=" http:// S3.51cto.com/wyfs02/m01/79/91/wkiom1auva6dbpidaadijgwh5z4110.png "border=" 0 "/>

Click Fail over:

650) this.width=650; "height=" 382 "title=" image "style=" border-top:0px;border-right:0px;background-image:none; border-bottom:0px;padding-top:0px;padding-left:0px;border-left:0px;padding-right:0px; "alt=" image "src=" http:// S3.51cto.com/wyfs02/m02/79/8f/wkiol1auvelr-x6uaaejimowhuw918.png "border=" 0 "/>

After the failover is logged in to HV-02, open Hyper-V Manager, you can see that the virtual machine "Vm-test" has been started:

650) this.width=650; "height=" 245 "title=" image "style=" border-top:0px;border-right:0px;background-image:none; border-bottom:0px;padding-top:0px;padding-left:0px;border-left:0px;padding-right:0px; "alt=" image "src=" http:// S3.51cto.com/wyfs02/m00/79/91/wkiom1auvbwrdizqaadbhc3tqh4684.png "border=" 0 "/>

Login HV-02 to see that the test file is synchronized:

650) this.width=650; "height=" 239 "title=" image "style=" border-top:0px;border-right:0px;background-image:none; border-bottom:0px;padding-top:0px;padding-left:0px;border-left:0px;padding-right:0px; "alt=" image "src=" http:// S3.51cto.com/wyfs02/m01/79/91/wkiom1auvbmgbx9baab0oacbkz4059.png "border=" 0 "/>

Related operations on Hyper-V replicas today we will introduce you so much! More exciting content, look forward to your attention!

This article is from the "Wu Yuzhang Microsoft blog" blog, make sure to keep this source http://wuyvzhang.blog.51cto.com/9992636/1734251

Hyper-V Server replica technology