Veritas™ Resiliency Platform 2.2 Solutions for VMware
- Section I. Overview of Resiliency Platform
- Overview of Resiliency Platform
- Overview of Resiliency Platform Data Mover
- Overview of recovery to on-premises data center
- Managing assets protected by NetBackup
- Overview of Amazon Web Services
- Overview of vCloud
- Section II. Preparing your environment
- Using array-based replication
- Using Veritas Resiliency Platform Data Mover
- Managing disaster recovery network mapping
- Managing Replication Gateway pairs
- 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) using Resiliency Platform Data Mover
- Managing virtual machines for remote recovery (DR) in Amazon Web Services
- Managing resiliency groups
- Section IV. Managing disaster recovery
- Rehearsing DR operations to ensure DR readiness
- Performing disaster recovery operations
- Rehearsing DR operations to ensure DR readiness
- Managing resiliency plans
- Creating a new resiliency plan template
- Monitoring risks, reports, and activities
- Managing evacuation plans
- Appendix A. General troubleshooting
- Resolving the Admin Wait state
- Appendix B. Sample policy and trust relationships for AWS
Configuring VMware virtual machines for disaster recovery using HPE 3PAR Remote Copy replication
This section lists the prerequisites and limitations to enable data replication using HPE 3PAR Remote Copy replication.
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 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 that the HPE 3PAR Remote Copy replicated LUNs are assigned to the respective VMware ESX Servers.
Note:
If any changes are made to storage or storage-adapters available to the ESX/ESXi host or cluster, you must perform storage rescan, storage adapter rescan or both depending on the changes made.
Ensure that the Symmetrix LUNs composing the datastore of the virtual machine's disk are grouped together into a 3PAR consistency group.
Note:
For HPE 3PAR Remote Copy based replication, all virtual machines that consume storage from a 3PAR Remote Copy Instance must belong to the same resiliency group. An Instance is a collection of volume groups that helps in maintaining write consistency during replication.
Once you have performed the necessary configurations, proceed with Resiliency Platform specific tasks to add the asset infrastructure to the Infrastructure Management Server (IMS). The following is a summary of the steps.
For more information see the Veritas Resiliency Platform Deployment Guide.
Resiliency Platform configurations:
Configure the VMware vCenter Server to send traps to the IMS.
Add the 3PAR enclosure to the IMS using the + HP Enclosure option at both the data centers.
This operation returns the list of 3PAR arrays (local and remote) accessible to the IMS. To configure disaster recovery for the virtual machines, select one or more local arrays only. Ensure that the enclosure discovery is complete before proceeding with adding the VMware vCenter Servers.
Add the vCenter Servers to their respective IMS in each data center using the
option. The user needs to have vCenter administrator privileges. Ensure that the virtualization server and ESX server are discovered successfully.
Limitations:
HPE 3PAR Remote Copy synchronous replication is not supported.
3PAR storage connectivity via iSCSI is not supported.