Configuring Hyper-V virtual machines for disaster recovery using HPE 3PAR Remote Copy

3PAR Remote Copy with Microsoft Failover Clustering

This section lists the prerequisites and limitations to enable data replication using HPE 3PAR Remote Copy when the hosts are part of a Microsoft failover cluster.

Prerequisites:

Ensure that the Infrastructure Managment Server (IMS) is able to communicate with 3PAR array using SSH.
Confirm that HPE 3PAR array user has edit or super role to perform HPE 3PAR Remote Copy operations.
Ensure that all the virtual machines consuming storage from a HPE 3PAR Remote Copy group belong to the same resiliency group.
Ensure that the HPE Remote Copy groups are set up for replication between the primary and the remote arrays. Ensure that the group names are unique across all data centers. Group name on the recover data center is auto generated by HPE. Do not modify the name.
Ensure to 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 you have created Microsoft failover cluster using the required nodes at the production and recovery data centers.
Ensure that you have created the cluster shared volume (CSV) on the replicated shared disk at the primary data center's Hyper-V Server.
Create virtual machines on the primary data center's Microsoft failover cluster with their data disks (.vhdx) on the replicated CSVs.
Ensure that you have all the Hyper-V integration services enabled for these virtual machines.
Ensure to create virtual machines in the Microsoft failover cluster at the production data center.
Ensure that the Hyper-V virtual network switch name that is used by the replicated virtual machines, is same across all the Hyper-V hosts.
Ensure that the virtual volume on the target data center is masked to the Hyper-V on the target data center.
Ensure to add all the Hyper-V servers of a cluster to Veritas Resiliency Platform.

Once you have performed the necessary configurations, proceed with Resiliency Platform specific tasks.

Veritas Resiliency Platform configurations:

Add the 3PAR enclosure to the IMS using the Add enclosure operation.
Add Microsoft Windows 2012 R2 host using Add Hosts option under IMS.
Perform add host and add enclosure operations for the IMS at the recovery data center as well.

Limitations:

HPE 3PAR Remote Copy synchronous replication is not supported.
3PAR storage connectivity via iSCSI is not supported.
Having the same WWN for both source and target LUNs in a RemoteCopy replication pair is not supported for LUNs mapped to the Windows application hosts or Windows Hyper-V servers.
Having the same WWN as the target LUN assigned to the snapshot LUNs during rehearsals is not supported for Windows application hosts or Windows Hyper-V servers.

3PAR Remote Copy without Microsoft Failover Clustering

This section lists the prerequisites and limitations to enable data replication using HPE 3PAR Remote Copy when the hosts are not part of a Microsoft failover cluster.