Page Comparison

...

8. Disaster Recovery Procedures

The disaster recovery procedures for [Organization Name] are as follows:For our main application and data at CourseKata we are using the Pilot Light strategy:

Replicate your data from one region to another and provision a copy of your core workload infrastructure. Resources required to support data replication and backup such as databases and object storage are always on. Other elements such as application servers are loaded with application code and configurations, but are switched off and are only used during testing or when Disaster Recovery failover is invoked.

• AWS (main application) Environment Recovery (Terraform Procedure):

  1. In case of an incident in the main region (Virginia, us-east-1), activate the disaster recovery plan in California (us-west-1).

  2. Follow the step-by-step Terraform procedure outlined in the provided cookbook /wiki/spaces/COURSEKATA/pages/10523836, including pulling the repository (https://github.com/UCLATALL/coursekata-terraform), initializing Terraform, applying the plan, and deploying applications.

  3. Document and save terminal logs for audits and compliance.

  4. Post-recovery, switch the DNS records to the new environment.

  5. (Regularly test this procedure every month, including testing VPC creation and Beanstalk environment setup, excluding DNS.)

• GCP (JupyterHub) Environment Recovery:

  • In case of an incident in the main region (Iowa, us-central1-a), activate the disaster recovery plan in Oregon (us-west1-a).

  • Follow GCP documentation to restore from backup (https://cloud.google.com/compute/docs/disks/restore-snapshot ).

  • Re-deploy the application using the documented deployment application included in the source code repository (https://github.com/coursekata/ckhub-k8s)

  • Document and save terminal logs for audits and compliance.

  • Post-recovery, switch the DNS records to the new environment.

  • (Regularly test this procedure every month, excluding DNS.)

...