Veritas™ Resiliency Platform 2.2 Solutions for VMware
- Section I. Overview of Resiliency Platform
- Overview of Resiliency Platform
- Overview of Resiliency Platform Data Mover
- About Veritas Resiliency Platform Data Mover
- Supported environments for Resiliency Platform Data Mover with VMware VAIO
- How Resiliency Platform Data Mover works
- About Veritas Resiliency Platform Data Mover architecture
- About full synchronization with Veritas Resiliency Platform Data Mover
- How Veritas Resiliency Platform Data Mover handles virtual machine writes
- Using Resiliency Platform Data Mover for recovery to premises- an overview
- 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
- Supported replication technologies with Veritas Resiliency Platform
- Protecting VMware virtual machines using array-based replication - an overview
- Configuring VMware virtual machines for disaster recovery using EMC SRDF replication
- Configuring VMware virtual machines for disaster recovery using EMC RecoverPoint replication
- Configuring VMware virtual machines for disaster recovery using NetApp SnapMirror
- Configuring VMware virtual machines for disaster recovery using Hitachi True Copy replication
- Configuring VMware virtual machines for disaster recovery using HPE 3PAR Remote Copy replication
- Configuring VMware virtual machines for disaster recovery using IBM SVC Global Mirror replication
- Configuring VMware virtual machines for disaster recovery using IBM XIV Remote Mirror replication
- Using Veritas Resiliency Platform Data Mover
- Managing disaster recovery network mapping
- Managing Replication Gateway pairs
- About Veritas Replication Gateway pairs
- How Resiliency Platform Data Mover supports encryption for data replication
- Creating a Veritas Replication Gateway pair
- Modifying encryption for a Veritas Replication Gateway pair
- Viewing Veritas Replication Gateways
- Viewing Veritas Replication Gateway pairs
- Removing a Veritas Replication Gateway pair
- Using array-based replication
- Section III. Working with resiliency groups
- Managing resiliency groups
- About resiliency groups
- Guidelines for organizing resiliency groups
- About service objectives
- Managing virtual machines for basic monitoring
- Starting a resiliency group
- Stopping a resiliency group
- Displaying resiliency group information and status
- Viewing resiliency group details
- Editing a resiliency group
- Deleting a resiliency group
- 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 VMware 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) using Resiliency Platform Data Mover
- Managing virtual machines for remote recovery (DR) in Amazon Web Services
- Managing virtual machines for remote recovery (DR) in vCloud
- Managing VMware virtual machines for remote recovery using NetBackup images
- Verifying the replication status for Veritas Resiliency Platform Data Mover
- Managing resiliency groups
- Section IV. Managing disaster recovery
- Rehearsing DR operations to ensure DR readiness
- About ensuring the disaster recovery readiness of your assets
- Rehearse operations - array-based replication
- Rehearse operations - Resiliency Platform Data Mover
- Prerequisites for rehearsal operation
- Performing the rehearsal operation
- Performing the rehearsal operation using NetBackup images
- Performing cleanup rehearsal
- Performing disaster recovery operations
- Rehearsing DR operations to ensure DR readiness
- 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 activities
- Managing evacuation plans
- Appendix A. General troubleshooting
- Viewing events and logs in the console
- Events in VMware virtual machines disaster discovery
- Troubleshooting discovery of assets
- Log files to troubleshoot Veritas Resiliency Platform Data Mover
- Managing tunable parameters
- Resiliency Platform fails to attach storage policy to virtual machines
- Resiliency Platform fails to create storage policy
- Resolving the Admin Wait state
- Troubleshooting NetBackup issues
- Troubleshooting delete resiliency group operation
- Appendix B. Sample policy and trust relationships for AWS
- Glossary
Configuring VMware virtual machines for disaster recovery using NetApp SnapMirror
This section lists the prerequisites to enable data replication for the Veritas Resiliency Platform environment using NetApp SnapMirror. For NetApp SnapMirror based replication all virtual machines that consume storage from a NetApp volume must belong to the same resiliency group.
Ensure that the NetApp volumes are already set up for replication between the primary and remote NetApp storage systems, and the replication has a replication schedule associated with it.
Resiliency Platform does not support one NetApp volume having more than one SnapMirror destination volumes.
NetApp volumes or qtrees can be provisioned as NFS datastores mounted on ESX servers, or LUNs created on NetApp volumes or qtrees can be provisioned to ESX servers via Fibre Channel and mounted as VMFS datastores.
Ensure that the NetApp SnapMirror replicated volumes are mounted on the respective VMware ESX servers in both the sites. Do not mount the replicated peer NetApp volumes to the same VMware ESX server.
Also ensure that the volumes are replicated using SnapMirror policy type mirror. SnapMirror policy types vault and mirror-vault are not supported.
NFS datastore need not be mounted on the recovery data center. While creating a resiliency group, you need to select the ESX server or the cluster on the recovery data center on which you want the Resiliency Platform to mount the datastore.
If you have already mounted the datastore then ensure that they have the same name on both data centers.
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.
Resiliency Platform configurations:
Using the Resiliency Platform console Infrastructure settings, you add the asset infrastructure for each data center (the production and recovery data centers). 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 VMware vCenter Servers to their respective data centers. The user needs to have vCenter administrator privileges.
Ensure that the virtualization server and ESX server are discovered successfully.
Add the NetApp enclosures to their respective data centers.
Ensure that you have sufficient privileges to perform SnapMirror replication operations.
More Information