See below for how to recover the state after a disaster

Stopping services on PKI Hub cluster 1

If the PKI Hub cluster 1 is accessible after the disaster, run the following command on any node of that cluster to stop the services.

$ sudo stop-services.sh

Setting PKI Hub cluster 2 as the active cluster

Set PKI Hub cluster 2 as the active cluster.

To set PKI Hub cluster 2 as the active cluster

  1. Configure one of the database nodes on the passive datacenter as the primary (read-write) database node.
  2. Configure the load balancer to send traffic to the passive datacenter instead of the active one. 
  3. 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). 

    After deploying Certificate Authority, perform the ATEAM-19193 workaround described in Known issues in Certificate Authority for PKI Hub 1.2.0.