At present data security is the most important challenges in the world, most of the business is suffering lost their important data, and Disaster recovery (DR) is confusing and expansive. Hyper v Replication resolves this complexity and expenses of Disaster recovery (DR). The remaining challenges for IT are to overcome any barrier.
Replica for disaster recovery
Virtual replica machine is fully ready to run as a duplicate source machine. When replica will be run then HVR assumes that the source machine machine is lost or unreachable, after switch on within a minute machine will be fully ready for real environment operation.
Hyper v Replication is Not a substitution for Automated Failover or Clustering
The very basic difference between Hyper-v Replica (HVR) and a failover cluster is that, Hyper-v Replica (HVR) maintains two separate copies of the same virtual machine and from them clustering uses only one. But Failover over Clustering is designed to rapidly relocate a protected resource – in this case, virtual machines – from an unavailable host to an available host. Replica is designed to allow for qiuck recovery of a virtual machine when one or more of the source. It does not require a common storage platform with the source.
Failover clustering is automated system but, HVR is not automated system. Replica operates on duplicity: if the replica is active, it must have been activated Purposely, If the source and replica virtual machines are active together, you have a “split-brain” scenario. Clients must be confused as to which to connect. Data will be update in two places together. Then a critical situation will be created and you cannot recover without data loss.
Best practices for Using Hyper-V Replica
Hyper-V Replica is a well-known and very usable technology with many possible configurations. You can configure it in one-to-one / many-to-many cluster setup. There is some important advantages are:
• Replica does not need same Hardware environment like as source.
• Here is not mandatory that every virtual machine must replicate
• Default Uses a single storage location
• It is possible to change storage location at any time.
• A failover system is triggered on the target host.
• The failover event is completed on the target host
• Now active the virtual replica machine copy.
• When primary replica site will be active replica is reestablished in reverse mood.
See Video Tutorial