Veritas™ Resiliency Platform 2.2 Solutions for Microsoft Hyper-V
- Section I. Overview of Resiliency Platform
- Section II. Preparing your environment
- Using array-based replication
- Managing disaster recovery network mapping
- Using array-based replication
- Section III. Working with resiliency groups
- Managing resiliency groups
- Configuring resiliency groups for remote recovery
- Managing virtual machines for remote recovery (DR) using 3rd party replication technology
- Managing virtual machines for remote recovery (DR) in Amazon Web Services
- Section IV. Managing disaster recovery
- Managing resiliency plans
- Creating a new resiliency plan template
- Monitoring risks, reports, and activites
- Managing evacuation plans
- Appendix A. General troubleshooting
- Appendix B. Sample policy and trust relationships for AWS
Configuring Hyper-V virtual machines for disaster recovery using Hyper-V Replica
To replicate data using Hyper-V Replica, you need to first configure Hyper-V Replica in your environment.
Refer to Microsoft documentation for configuring Hyper-V replica with and without Microsoft Failover clustering.
This section lists the pre-requisites to enable data replication using Hyper-V Replica when the hosts are part of a Microsoft failover cluster.
Enable the Hyper-V and Failover Cluster roles on the Windows Server 2012 R2 hosts at the production and recovery (DR) data centers.
Ensure that the Microsoft failover cluster is already created using the required nodes at the production and recovery data centers.
In case of certificate-based authentication, ensure that you have specified broker-level certificate in the Hyper-V Replica broker replication settings.
Ensure that the cluster shared volumes (CSVs) are present at either the production or the recovery data centers' Microsoft failover clusters.
Ensure that all virtual machines are part of the Microsoft failover cluster. The data and configuration of the virtual machines will be stored on the cluster shared volume.
Ensure that Hyper-V Replica Broker is configured on a node of the Microsoft failover clusters at the production and recovery data centers.
On the Replica broker replication settings page, ensure to add the remote site broker details.
Ensure that replication is already enabled for the virtual machines at the primary site.
On Hyper-V host, verify whether the replication state for a given virtual machine is Replicating.
Note:
Disaster recovery for cloned virtual machines in Hyper-V replica is currently not supported.
Once you have performed the necessary configurations, proceed with Resiliency Platform specific tasks.
Resiliency Platform configurations:
Add Hyper-V virtual machines under respective data center using the
option in > > . Provide domain user's credentials if Hyper-V Replica is managed by a domain user. Note that the primary and remote hosts must not be the part of the same data center.
This section lists the pre-requisites to enable data replication using Hyper-V Replica when Microsoft Failover Clustering is not used.
Enable the Hyper-V role on the Windows Server 2012 R2 hosts at the production and recovery (DR) data centers.
Ensure to create and configure the required virtual machines on the host at the production data center.
Ensure to enable the replication for the required virtual machine using the Hyper-V Manager at the production data center. It replicates the virtual machine boot disk (.VHDX) to the recovery data center.
Once you have performed the necessary configurations, proceed with Resiliency Platform specific tasks.
Resiliency Platform configurations:
Add Hyper-V virtual machines under respective data center using the
option in > > . Provide domain user's credential if Hyper-V Replica is managed by a domain user.