Disaster recovery for GCP

Disaster recovery of deployment via Terraform script

Secondary resources will be created, and the disaster recovery script will be executed automatically by the Terraform script.

• To create the secondary resources via Terraform script:

  1. Promote the Cloud SQL read replica to primary.

  2. Set the value of the recoverKyvosCluster to true and enableDr to false in the kyvosparams.tfvars file located in the Terraform folder > Conf folder (available in GCP installation files). This indicates that the deployment will act as the disaster recovery cluster. For more details, click here.

  3. Reuse the following configurations for secondary deployment. The following resources will not be recreated in the secondary deployment. Instead, they will be reused from the primary deployment:

     1. Service Account

     2. VPC Network and subnetwork

     3. Secret Manager

     4. Storage Bucket

     5. CloudSQL

  4. Trigger deploy.sh script (available in the GCP installation files).

  5. Once your resources are created, you can access the Kyvos Manager using the secondary Kyvos Manager node.

NEXT: Perform Disaster Recovery from Kyvos Manager

After performing DR from Kyvos Manager, the secondary cluster will become the active Kyvos environment.

Wizard-based deployment- Manual disaster recovery and back up

To manually perform disaster recovery, perform the following steps.

1. Promote CloudSQL Replica.

2. Create secondary resources with the same configuration as that of primary resources deployment.

3. Download disaster recovery script (complete-disaster-recovery.sh) on secondary Kyvos Manager node from the bucket and execute it with Kyvos user. The bucket path is <bucket-name>/user/engine_work/setup/scripts.

4. Now, you can access Kyvos Manager using the secondary Kyvos Manager node IP.

NEXT: Perform Disaster Recovery from Kyvos Manager