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
- Protecting Hyper-V virtual machines using array-based replication - an overview
- Configuring Hyper-V virtual machines for disaster recovery using Hyper-V Replica
- Configuring Hyper-V virtual machines for disaster recovery using EMC SRDF
- Configuring Hyper-V virtual machines for disaster recovery using EMC RecoverPoint
- Configuring Hyper-V virtual machines for disaster recovery using Hitachi TrueCopy Universal Replicator
- Configuring Hyper-V virtual machines for disaster recovery using HPE 3PAR Remote Copy
- Configuring Hyper-V virtual machines for disaster recovery using IBM SVC Global Mirror
- Configuring Hyper-V virtual machines for disaster recovery using IBM XIV Remote Mirror
- Managing disaster recovery network mapping
- Using array-based replication
- Section III. Working with resiliency groups
- Managing resiliency groups
- Configuring resiliency groups for remote recovery
- Understanding the role of resiliency groups in disaster recovery operations
- How Resiliency Platform configures disaster recovery protection for virtual machines
- Prerequisites for configuring Hyper-V virtual machines for disaster recovery
- Limitations for virtual machine disaster recovery
- Managing virtual machines for remote recovery (DR) using 3rd party replication technology
- Managing virtual machines for remote recovery (DR) in Amazon Web Services
- Managing virtual machines for remote recovery (DR) in vCloud
- Section IV. Managing disaster recovery
- Managing resiliency plans
- About resiliency plans
- Creating a new resiliency plan template
- Editing a resiliency plan template
- Deleting a resiliency plan template
- Viewing a resiliency plan template
- Creating a new resiliency plan
- Editing a resiliency plan
- Deleting a resiliency plan
- Executing a resiliency plan
- Viewing a resiliency plan
- Creating a schedule for a resiliency plan
- Editing a schedule for a resiliency plan
- Deleting a schedule for a resiliency plan
- Viewing a schedule for a resiliency plan
- Monitoring risks, reports, and activites
- About the Resiliency Platform Dashboard
- Understanding asset types
- Displaying an overview of your assets
- About risk insight
- Displaying risk information
- Predefined risks in Resiliency Platform
- Viewing the current risk report
- Viewing the historical risk report
- Viewing reports
- Managing activities
- Viewing activities
- Aborting a running activity
- Managing evacuation plans
- Appendix A. General troubleshooting
- Appendix B. Sample policy and trust relationships for AWS
- Glossary
Configuring Hyper-V virtual machines for disaster recovery using HPE 3PAR Remote Copy
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 RemoteCopy 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.
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.
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.
Prerequisites:
Ensure that the 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 RemoteCopy operations.
Ensure that the 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 recovery 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 recovery data center as well.
Limitations:
Logical grouping of disks (Windows Server Storage space storage pool) is not supported.
HPE 3PAR Remote Copy synchronous replication is not supported.
3PAR storage connectivity via iSCSI is not supported.