Week 7—— Hyper-V Replica

Week 7—— Hyper-V Replica

Hyper-V Replica
Hyper-V Replica is a disaster recovery add-on feature for Hyper-V.

The Hyper-V Replica is not a VM mobility concept or a backup strategy.

Its purpose is to maintain a standby replica copy of virtual machines, running on your Hyper-V host or in your data center.

1.What are the prime components of Hyper-V Replica?

Hyper-V Replica has the following components:

1. Replication engine
   Manages replication configuration and handles initial replication, delta replication, failover, and test-failover
2. Change tracking module
   Keeps track of the write operations in the virtual machine
3. Network module
   Provides a secure and efficient channel to transfer data
4. Hyper-V Replica Broker server role
   Provides seamless replication while a virtual machine is running on different failover cluster nodes
5. Management tools
   Hyper-V Manager, Windows PowerShell, Failover Cluster Manager

2.What is Recovery Time Objective (RTO)? What is Recovery Point Objective (RPO)?

• Recovery Time Objective (RTO): This is another expression for Service Level Agreement (SLA). The term is used to refer to the duration of time within which a business is restored post a major contingency, or in other words, how much downtime you can bear for a system without it impacting on your business?
• Recovery Point Objective (RPO): This is used to quantify your data recovery and loss, and is used to indicate the amount of data loss acceptable in the event of a downtime.

3.Describe the difference between Test Failover and Planned Failover.

Test failover：
Non-disruptive testing, with zero downtime
New virtual machine created in recovery site

• From the replica checkpoint
• Turned off and not connected

Stop Test Failover

Planned failover：
Initiated at primary virtual machine which is turned off
Sends data that has not been replicated
Fail over to replica server
Start the replica virtual machine
Reverse the replication after primary site is restored