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
Prerequisites for configuring applications for disaster recovery
To be able to perform disaster recovery (DR) operations on the applications in the data center, ensure that the following requirements are met.
The application host must be added to Resiliency Platform and discovery of the applications must be complete. The applications should be running.
Add the discover hosts and the enclosures for replication to the IMS at the production and recovery data center.
If applications are installed on VMware virtual machines, you need to configure the VMware vCenter for discovery. Similarly if the applications are installed on Hyper-V virtual machines, you need to configure the Hyper-V server for discovery.
The replicated storage provided to the application hosts from the storage arrays is discovered if you have configured the discovery hosts and the enclosures.
Replicated storage can be provisioned to the application in numerous ways. For applications installed inside virtual machines, Resiliency Platform discovers storage that is provisioned to the virtual machines in raw mode (e.g. VMware RDM mode) from the hypervisors. Raw mode can also be achieved by using NPIV HBAs and provisioning storage (LUNs) directly from the arrays to the Virtual HBA Ports assigned to the virtual machines.
If the storage is provisioned to the application virtual machines using hypervisor, then you need to provision appropriate snapshot devices to the virtual machines in the same manner as the replicated devices. This is required to perform the rehearsal operation successfully.
For NetApp SnapMirror and HP 3PAR RemoteCopy, the snapshot devices do not exist beforehand and are created as a part of the Rehearsal operation. These snapshot devices should be mapped to the application hosts. As part of the Rehearsal operation, Resiliency Platform maps the snapshot devices to the same hosts to which the replicated LUNs are mapped. If the replicated LUNs are mapped through the hypervisor, then Resiliency Platform cannot further provision them to the application virtual machines.
As a result, Rehearsal is not supported with these replication technologies when the application is installed in virtual machines with replicated storage mapped as raw LUN by the hypervisor.
Applications must be members of the same Veritas Replication Set.
They must use the same replication technology.
Application binaries should be stored on local storage and data files on replicated storage.
The DNS server settings should be configured for both data centers. DNS settings are required for binding a host name to different IP addresses on the DR site. This is required only if you plan to use the Resiliency Platform for performing DNS updates.
Ensure that you have disabled the 'Quick removal' policy for disks in Windows Server 2008 R2 and disabled the 'write-cache' policy for disks in Windows Server 2012 R2.
Applications should be preconfigured at the recovery data center before creating resiliency groups and proceeding with the DR operations. Discovery of these applications on the recovery data center must be complete and status should be offline. Ensure that the application instance name should be same at the production and recovery data center.
Linux LVM Volume Group used for data file storage of an application should not be in exported state.
On Linux application hosts, the data mount point of the application should be present in
/etc/fstabfile.