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
- Managing disaster recovery network mapping
- Using array-based replication
- Section III. Working with resiliency groups
- Managing resiliency groups
- Configuring resiliency groups for remote recovery
- Managing virtual machines for remote recovery (DR) using 3rd party replication technology
- Managing virtual machines for remote recovery (DR) in Amazon Web Services
- Section IV. Managing disaster recovery
- Managing resiliency plans
- Creating a new resiliency plan template
- Monitoring risks, reports, and activites
- Managing evacuation plans
- Appendix A. General troubleshooting
- Appendix B. Sample policy and trust relationships for AWS
Configuring Hyper-V virtual machines for disaster recovery using EMC SRDF
This section lists the pre-requisites to enable data replication using EMC SRDF when the hosts are part of a Microsoft failover cluster. For EMC SRDF-based replication, all virtual machines consuming storage from a consistency group must belong to the same resiliency group.
Ensure that EMC Solutions Enabler (version v7.4, or later) is installed on a host and the SRDF device groups are already set up for replication between the primary and remote arrays.
Ensure that EMC Symmetrix Gatekeeper 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 SRDF R1 and R2 LUNs must be on 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.
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.
Resiliency Platform configurations:
Add Microsoft Windows 2012 R2 host using the
option in > > .Discovery hosts can be added using the
option in > > > tab.Add the array control host where the SRDF device groups are configured, to the each IMS using the Add Hosts operation.
Add EMC Symmetrix enclosure using the + EMC Enclosure option. Provide the discovery host name and the SYMCLI location on the discovery host. This operation returns the list of all Symmetrix arrays (local and remote) that are accessible to the host. To configure disaster recovery for the virtual machines, select only local arrays. This step is optional.
Default SymCLI location on Linux host
/opt/emc/SYMCLI/bin/
Default SymCLI location on Windows host
C:\Program Files\EMC\SYMCLI\bin
Perform add discovery host and add enclosure (optional) operations at the disaster recovery data center as well.
Limitations:
EMC SRDF LUN-based replication (without device group) and replication in the adaptive copy mode are not supported.
The rehearsal operation for resiliency groups using EMC Symmetrix Timefinder SNAP is not supported in Microsoft Failover Cluster environment.
This section lists the pre-requisites to enable data replication using EMC SRDF when the hosts are not part of a Microsoft failover cluster.
Ensure that EMC Symmetrix Solutions Enabler (version v7.4, or later) is installed on the hosts and SRDF device groups are already set up for the replication between the primary and remote arrays.
Ensure that EMC Symmetrix Gatekeeper device is present on the array control host. You can designate any host, including the Hyper-V Server, as the array control host.
Note:
The replicated and primary LUNs must be on 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. 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 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 (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.
Note:
For the support of rehearsal 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 SRDF device groups are configured, using the
option in > > > tab.Add Symmetrix enclosure using the + EMC Enclosure option. Provide the discovery host name and the SYMCLI location on the discovery host. This operation returns the list of all Symmetrix arrays (local and remote) that are accessible to the host. To configure disaster recovery for the virtual machines, select one or more local arrays.
Default SymCLI location on Linux host
/opt/emc/SYMCLI/bin/
Default SymCLI location on Windows host
C:\Program Files\EMC\SYMCLI\bin
Perform add discovery host and add enclosure operations at the disaster recovery data center as well.
Limitations:
Logical grouping of disks (Windows Server Storage space storage pool) is not supported.