See below for how to recover the active datacenter system on the passive datacenter.
To recover the active datacenter system in the passive datacenter.
- 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 - Configure one of the database nodes on the passive datacenter as the primary (read-write) database node.
- Configure the load balancer to send traffic to the passive datacenter instead of the active one.
- 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). When completing these steps, the passive warm-standby datacenter becomes the active one, and vice versa.
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.
- 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