 | ||
| Configuring disaster recovery for a resiliency group of applications | ||
|---|---|---|
| Prev | Preparing for disaster recovery operations | Next |
| ||
| Configuring disaster recovery for a resiliency group of applications | ||
|---|---|---|
| Prev | Preparing for disaster recovery operations | Next |
Before you configure disaster recovery (DR) for a resiliency group of applications, make sure of the following:
The selected resiliency group must have applications from the production data center and the recovery data center.
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.
For more information on configuring DNS server settings, see the Deployment Guide.
For applications on Windows with Failover Clustering, you may have to plumb or unplumb the IP addresses using appropriate Failover Clustering roles. If Failover Clustering is not used, you must plumb the application IP addresses on all the systems across the data centers. The Resiliency Platform console does not manage plumbing or unplumbing of IP address for applications.
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.
A successful DR configuration enables takeover and migrate operations.
You can also protect your applications by creating a resiliency group and setting up disaster recovery for the group in a single wizard panel.
To configure disaster recovery for a resiliency group of applications
When the configuration is complete, a notification is displayed and the DR Status column on the resiliency group listing page displays the status as Configured.
