Veritas™ Resiliency Platform 2.2 Solutions for Applications
- Overview of Resiliency Platform
- Managing applications using Resiliency Platform
- Managing applications using Resiliency Platform
- Providing inputs for partially discovered applications
- Managing custom applications
- About application bundles
- Adding an application bundle to the Resiliency Manager
- Removing an application bundle
- Installing an application bundle on selected application hosts
- Uninstalling an application bundle from selected hosts
- Enabling and disabling application bundle on selected application hosts
- Managing auto-deploy for an application bundle
- Editing the discovery schedule for an application type
- Viewing the details of application types
- Viewing the applicable host details
- Managing InfoScale applications using Resiliency Platform
- Managing resiliency groups
- About resiliency groups
- About service objectives
- Managing applications for basic monitoring
- Starting a resiliency group
- Stopping a resiliency group
- Displaying resiliency group information and status
- Viewing InfoScale applications details
- Viewing resiliency group details
- Editing a resiliency group
- Deleting a resiliency group
- Preparing for disaster recovery configuration
- An overview of key steps required for disaster recovery of applications
- Prerequisites for configuring applications for disaster recovery
- An overview of key steps required for disaster recovery of InfoScale applications
- Prerequisites for configuring InfoScale applications for disaster recovery
- About replication technologies used in disaster recovery of applications
- Configuring DNS server settings for a data center
- Configuring resiliency groups for remote recovery
- Rehearsing DR operations to ensure DR readiness
- Performing disaster recovery operations
- Monitoring and reporting assets status
- Monitoring risks
- Managing activities and resiliency plans
- Managing activities
- 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
- Managing evacuation plans
- Appendix A. Troubleshooting
- Glossary
Rehearse operations for applications - array-based replication
The requirements for rehearse operations for applications depends on the replication type.
Rehearse operations with EMC SRDF based replication:
Device group should be associated with the snapshot LUNs. Veritas Resiliency Platform supports Timefinder Snap and Timefinder Mirror (BCV).
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, the Resiliency Platform creates point in time snapshots as a part of the rehearsal operations, since it cannot work with the 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 snapshot disks are enabled on the DR hosts.
For Linux hosts, the logical volume manager (LVM) volume group (VG) is imported using the snapshot disks. The LVM volume, on the snapshot VG, is then mounted on a mount point. This mount point is same as that of the VG on the DR host if you were to perform the takeover or migrate operation.
For Windows host, the snapshot disk is assigned a drive letter. This drive letter is the same as that of the replicated disk if you were to perform the takeover or migrate operation.
The application is then started on the DR hosts. The application starts to consume storage from the snapshot disks instead of the replicated disks.
During the Rehearse cleanup operation, the above tasks are reversed and the snapshots are terminated, bringing the system back to the original state.
Rehearse operations with NetApp SnapMirror based replication:
NetApp SnapMirror based replication uses FlexClone for the Rehearse operation and so NetApp storage server must be enabled with the FlexClone license.
When the rehearse operation is initiated, the Resiliency Platform creates a point in time volume snapshot as a part of the rehearsal operation. The snapshot volume is exported and mounted on the DR host.
Note:
Rehearse operation breaks any ongoing replication between the source storage server and the destination storage server as the FlexClone operation cannot be performed on the destination read-only volume. SnapMirror replication resumes after the rehearsal cleanup operation is complete.
The application is then started on the DR hosts. The application starts to consume storage from the snapshot disks instead of the replicated disks.
During the Rehearse cleanup operation, the above tasks are reversed and the snapshots are terminated, bringing the system back to the original state.