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
Rehearse operations - array-based replication
The requirements for rehearse operations for VMware virtual machines depend on the replication type.
Rehearse operations with EMC SRDF-based replication
Rehearse operations with NetApp SnapMirror based replication
The device group should be associated with the snapshot LUNs. Resiliency Platform supports TimeFinder Snap and TimeFinder Mirror.
Rehearsal operations for resiliency groups that are replicated using EMC SRDF technology in Asynchronous mode cannot be performed using TimeFinder Snap technology (VDEV devices). You need to configure TimeFinder Mirrors (BCV devices) to perform the rehearsal operations on such resiliency groups.
When the rehearse operation is initiated, Resiliency Platform creates point-in-time snapshots, since rehearsal cannot work with existing snapshots.
Note:
If there are any active snapshots that are in progress, you need to terminate the snapshots and refresh the asset discovery.
The datastores on the snapshot device are attached on the DR host.
Resiliency Platform registers the virtual machines in the production data center for rehearsal. They have identical configuration to the DR virtual machines, except these virtual machines consume storage from the datastore mounted using the snapshot volumes. These virtual machines are disconnected from the network and are unregistered during cleanup.
NetApp SnapMirror based replication uses FlexClone for the rehearse operation, so the NetApp storage server must be enabled with the FlexClone license.
When the rehearse operation is initiated, Resiliency Platform creates a point-in-time volume snapshot as part of the rehearsal operation. The snapshot volume is exported and mounted on the DR host.
Note:
The rehearse operation breaks any ongoing replication between the source and destination storage server as the FlexClone operation cannot be performed on the destination read-only volume. SnapMirror replication resumes after the rehearsal cleanup operation.
Resiliency Platform registers the virtual machines in the production data center for rehearsal. They have identical configuration to the DR virtual machines, except these virtual machines consume storage from the datastore that is mounted using the snapshot volumes. These virtual machines are disconnected from the network and are unregistered during cleanup.