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 Hitachi TrueCopy Universal Replicator
This section lists the pre-requisites to enable data replication using Hitachi TrueCopy/Universal Replicator when the hosts are part of a Microsoft failover cluster. For Hitachi TrueCopy/Universal Replicator based replication, all virtual machines consuming storage from a device group must belong to the same resiliency group.
Prerequisites:
Ensure that HORCM is installed on a host and the Hitachi TrueCopy/Universal Replicator device groups are already set up for replication between the primary and remote arrays.
Ensure that Hitachi Command Device is presented to the array control host. You can designate any host, including the Hyper-V Server, as the array control host.
Note:
The TrueCopy/HUR PVOLs & SVOLs must mapped to different hosts from different data centers.
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 (R1) 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. In order to share the virtual machine configurations between cluster nodes, make sure to have another CSV (non-replicated). The user must set default virtual machine location to point to the non replicated CSV.
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 Microsoft Windows 2012 R2 host using Add Hosts option under Infrastructure Management Server (IMS).
Add the array control host where the TrueCopy/HUR device groups are configured, to the each IMS using the Add Hosts operation.
Add HiCommand Device Manager using the Add Enclosure option. Provide the discovery host name.
Perform add host and add enclosure operations for the IMS at the disaster recovery data center as well.
This section lists the pre-requisites to enable data replication using Hitachi TrueCopy/Universal Replicator when the hosts are not part of a Microsoft failover cluster.
Prerequisites:
Ensure that Hitachi Command Device is presented to the array control host. You can designate any host, including the Hyper-V Server, as the array control host.
The replicated and primary LUNs must be mapped to different hosts from different data centers.
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 centre under the Hyper-V Manager and kept their data files (.vhdx) on the replicated volumes. Do not keep their 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 (TC SVOL disk and ShadowImage SVOL) 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.
Note:
For the support of rehearse operation, you must add the snapshot devices to the DR data center's SRDF device group, and thereafter map them to the DR data center's Hyper-V hosts.
Once you have performed the necessary configurations, proceed with Resiliency Platform specific tasks.
Veritas Resiliency Platform configurations:
Add the host where the HTC/HUR device groups are configured, to the Infrastructure Management Server (IMS) using the Add Hosts operation.
Add HiCommand Device Manager using the Add Enclosure option. Provide the discovery host name.
Perform add host and add enclosure operations for IMS at the disaster recovery data center as well.
Limitations:
Logical grouping of disks (Windows Server Storage space storage pool) is not supported.