Configuring Hyper-V virtual machines for disaster recovery using IBM SVC Global Mirror
This section lists the pre-requisites to enable data replication using IBM SVC Global Mirror when the hosts are not part of a Microsoft failover cluster
Prerequisites:
Ensure that you have created the volumes on the primary Hyper-V host where the LUNs are read/write enabled. Veritas Resiliency Platform supports only one volume per replicated disk. We do not support Windows Storage Space Storage Pool.
Ensure that you have created virtual machines at the primary data center under the Hyper-V Manager and kept the data files (.vhdx) on the replicated volumes. Do not keep the configuration files (.xml) on any replicated drive. Also, make sure that the default virtual machine configuration location under Hyper-V Manager Settings is not on a replicated drive.
Ensure the respective remote disks (Read only - R2 remote disk and snapshot) are in the offline state on the Hyper-V server at the DR data center. And also verify that no drive letter is assigned to the volumes present on these offline disks.
Ensure that the IBM SVC Global Mirror replicated LUNs are assigned to the respective HyperV Servers.
Once you have performed the necessary configurations, proceed with Resiliency Platform specific tasks.
Using the Resiliency Platform console Infrastructure settings, you add the asset infrastructure for each data center (the production and recovery data centers). The following is a summary of the steps.
Add IBM SVC enclosure using the option. Provide the IBM SVC server, username, and password. Ensure that the enclosures are discovered successfully.
Add Microsoft Windows 2012 R2 host using the option in > > .
Perform add discovery host and add enclosure (optional) operations at the disaster recovery data center as well.
Raw Device Mapping (RDM) on replicated disks to virtual machine is not supported.