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
Configuring applications for disaster recovery using NetApp SnapMirror replication
This section lists the pre-requisites to enable the data replication using NetApp SnapMirror. For NetApp SnapMirror based replication, all applications that consume storage from a NetApp volume must belong to the same resiliency group.
Ensure the NetApp volumes are already setup 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.
Ensure to mount NetApp SnapMirror replicated volumes on the respective servers in both the sites. Do not mount the replicated peer NetApp Volumes on the same server.
Also ensure that the volumes are replicated using SnapMirror policy type mirror. SnapMirror policy types vault and mirror-vault are not supported.
NetApp share can be mounted with array IP or FQDN. For storage to application correlation to work successfully, ensure that the mount entry is consistent in the fstab.
Change the permission to Grant root access to all hosts on the replicated volumes at both the production and recovery sites.
Once you have performed the necessary configurations, proceed with Resiliency Platform specific tasks.
Resiliency Platform configurations:
Ensure that all the application hosts are added and discovered completely by the Infrastructure Management Server (IMS).
Add NetApp enclosure using the option.
Provide the discovery host name, NetApp storage system name or IP, and credentials.
Ensure that all the application hosts are added and discovered completely by IMS at the disaster recovery (DR) site.
Perform add enclosure operations for the IMS at the DR data center as well.