See below for how to recover the active datacenter system on the passive datacenter. 

To recover the active datacenter system in the passive datacenter. 

1. If the active datacenter is accessible after the disaster, run the following command on any node of that cluster to stop the services.
   
   $ sudo stop-services.sh
   If the active datacenter is not accessible or if the stop-services.sh  execution ends with errors, then change the network configuration to prevent nodes in the active data center from accessing the database.
2. Configure one of the database nodes on the passive datacenter as the primary (read-write) database node.
3. Configure the load balancer to send traffic to the passive datacenter instead of the active one. 
4. Log in to the Management console in the passive datacenter and deploy all solutions to complete the restore process. The deployment process is expected to take ~30min (~5 min per solution). 
   

   The deployment of the Certificate Authority will fail due to the ATEAM-19193 issue described in Known issues in Certificate Authority for PKI Hub 1.2.0. Execute the workaround described and retry the deployment of the Certificate Authority.

   When completing these steps, the passive warm-standby datacenter becomes the active one, and vice versa.
5. In the passive datacenter, execute the steps described in Restoring the active cluster configuration on the passive one to restore the new active cluster configuration on the passive one
6. In the passive datacenter, if the stop-services.sh was not executed successfully during step 1 (e.g., because the nodes were down) , fix the issues and retry the execution until it completes without errors. Then change the network configuration to allow nodes in the passive data center to access the database.