Shulou(Shulou.com)06/02 Report--

Hyper-V replicas are a feature that can be used to replicate virtual machines as part of a business continuity solution. From Windows Server 2012, the Hyper-V role introduced Hyper-V Replica as a built-in replication mechanism for virtual machines, which is also applicable in Windows Server 2016. Hyper-V replicas can asynchronously replicate virtual machines from the primary site to the replica virtual machines at the secondary site and do not require shared storage or any specific storage hardware.

Before replicating a virtual machine, the server running Hyper-V must be enabled as the replica server so that the server can be used to receive the replicated virtual machine. To do this, modify the replication configuration settings for the server. In Hyper-V Manager, open the Hyper-V settings and go to the copy configuration page. After you enable the replica server, you can configure the virtual machine for replication.

Advantages:

Resiliency-provides workload resilience for small and medium-sized businesses by replicating between branch offices or regional sites in different geographic locations.

Scalability-by deploying it with Azure Site Recovery services, you can scale and automate replication. When integrated with this service, you can replicate between local sites or between local sites and Azure.

Cost reduction-reduces cost of ownership by providing a storage-independent and workload-independent solution that replicates efficiently, periodically and asynchronously across different storage subsystems and sites on IP-based networks. It does not rely on shared storage, storage arrays, or other software replication technologies.

Restore-allows rapid recovery, minimizes downtime, and runs the workload from the secondary site in the event of an outage.

Purpose:

Because Hyper-V copies are very simple and flexible, they can be used in potential scenarios of various levels of complexity. Some examples include:

Head office and branch

In this case, there are two sites: the main headquarters and one or more branch offices in different physical locations. With virtualized workloads, Hyper-V Replica can be used to provide disaster recovery support for branch offices. The server on any site can be a clustered server or a stand-alone server.

In this case, day-to-day operations will run on virtual machines running on the primary server of each branch office. If the primary server has to go offline for any reason, each branch office will have a secondary master station server at the headquarters to take over the workload.

In Windows Server 2012 R2 or Windows Server 2016, you can use extended replication to further extend this scenario. Each branch office locates its replica server nearby and then uses extended replication to send changes back to the extended replica server at headquarters.

This scenario can be expanded to involve large data centers with many servers without requiring any different management activities associated with Hyper-V replicas.

Cloud service provider

In this scenario, managed service providers set up replica servers in their data centers that receive replication data from multiple primary servers running virtualized workloads at each of their customers' locations. The replica server of the managed service provider therefore provides disaster recovery capabilities for customers who subscribe to it.

To ensure the security of customers, this scenario will involve certificate-based authentication using certificates serviced by separate certificate servers that may be owned by the hosting provider. In addition, Replica's trusted groups feature allows managed service providers to use separate storage locations and tags to isolate replicated data from each customer to prevent data from different customers from being mixed.

Characteristics:

Integration-Hyper-V Replica is part of the Hyper-V role.

Workload independent-Hyper-V replicas replicate virtual machines so that workloads that can be virtualized in Hyper-V can be replicated.

Stand-alone or clustered-Primary and secondary sites can run separate Hyper-V hosts or clusters.

Storage-there is no need for shared storage or specific storage technologies.

Local or remote servers-the primary and secondary servers can coexist physically or geographically separate.

After the primary virtual machine is initially replicated to the secondary virtual machine, only incremental changes are replicated.

The Active Directory-Hyper-V host server does not need to be a domain member. If they are domain members, they do not need to be in the same domain.

Replication frequency-replicates every 5 minutes in Windows Server 2012. In Windows Server 2012 R2, Windows Server 2016, you can configure the replication frequency every 30 seconds, 5 minutes, or 15 minutes.

Testing-you can use Hyper-V replicas to test replication without interrupting normal production replication.

Welcome to the official account of Wechat: Xiao Wen study Society.

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.