Disaster Recovery Guide › DR Site Operations › DR Site Failover and Failback › Failback to the Primary Site

Failback to the Primary Site

The failback procedure is the reverse of the failover procedure. Like failover, failback is manually initiated. Your decision to failback depends on the capabilities at the DR site:

• If the DR site has equivalent redundancy and performance to the primary site, you may decide not to failback. Every failback requires another outage. Therefore, the DR site carries the load until it fails.
• If the primary site has capabilities that are superior to the DR site, you can failback as soon as the primary site is repaired and the data tier is resynchronized between sites.

Follow the same procedure as noted in Failover section by converting the DR site to Standby and Primary site to Live. Then perform the following steps:

1. On all DR site servers, run the following commands to convert them to Live mode.

   cd /opt/CA/saas/repo/application
   DR_mode.sh mode=standby
   

2. On all of the Primary site servers, run the following commands to convert them to Live mode.

   cd /opt/CA/saas/repo/application
   DR_mode.sh mode=live
   

   Use the following order for running the script on primary site servers:

   • Directory
   • Provisioning Server
   • CA IAM Connector Server
   • Policy Server
   • CSP console
   • Secure Proxy Server
   • Identity Management server
3. If the database has failed at primary site, restore it.
   • Convert the master database at the primary site to standby.
   • Begin database replication from the DR site to the primary site.