 | ||
| Configuring Hyper-V virtual machines for disaster recovery using HPE 3PAR Remote Copy | ||
|---|---|---|
| Prev | Using array-based replication | Next |
| ||
| Configuring Hyper-V virtual machines for disaster recovery using HPE 3PAR Remote Copy | ||
|---|---|---|
| Prev | Using array-based replication | Next |
This section lists the pre-requisites to enable data replication using HPE 3PAR Remote Copy when the hosts are part of a Microsoft failover cluster. For HPE 3PAR Remote Copy based replication, all virtual machines consuming storage from a HPE 3PAR Remote Copy group must belong to the same resiliency group.
Prerequisites:
Ensure that the discovery host is able to communicate with HPE 3PAR array using SSH.
Confirm that HPE 3PAR array user has all the necessary permissions to perform HPE 3PAR RemoteCopy operations.
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 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.
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 Infrastructure Management Server (IMS).
Perform add host and add enclosure operations for the IMS at the disaster recovery data center as well.
Limitations:
Raw Device Mapping (RDM) on replicated disks to virtual machine is not supported.
HPE 3PAR Remote Copy synchronous replication is not supported.
3PAR storage connectivity via iSCSI is not supported.
This section lists the pre-requisites to enable data replication using HPE 3PAR Remote Copy when the hosts are not part of a Microsoft failover cluster.
Prerequisites:
Ensure that the discovery host is able to communicate with HPE 3PAR array using SSH.
Confirm that HPE 3PAR array user has all the necessary permissions to perform HPE 3PAR RemoteCopy operations.
HPE Remote Copy groups are set up for replication between the primary and remote arrays.
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. Veritas Resiliency Platform does 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 their data files (.vhdx) on the replicated volumes.
Ensure the respective remote disks 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.
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.
Perform add host and add enclosure operations for IMS at the disaster recovery data center as well.
Limitations:
