liveBook · Manning

Disaster recovery

As explained in Amazon Web Services in Action, Third Edition: An in-depth guide to AWS

Disaster recovery is the set of processes and capabilities for restoring systems and data after a disruptive failure or destructive event.

Disaster recovery is the set of processes and capabilities for restoring systems and data after a disruptive failure or destructive event. In cloud architectures, it includes preparing for virtual-machine, availability-zone, and region-wide outages. section 13.0 section 13.3

Start by defining two business measures:

  • Recovery time objective (RTO) is how long the system may remain unavailable before reaching a working state. section 13.3
  • Recovery point objective (RPO) is the acceptable amount of data loss, expressed as time between the failure and the latest recoverable data. section 13.3
  • Use these objectives to choose an architecture, because higher availability increases system complexity and initial and operating costs. section 13.3

Copy an RDS snapshot across regions

To prepare for a region-wide outage, copy a database snapshot from us-east-1 to eu-west-1, then restore a database from the copied snapshot. Retrieve the source snapshot ARN before copying it. Check privacy and compliance rules before moving real data between regions. section 10.3.4

$ aws rds describe-db-snapshots \
 --db-snapshot-identifier wordpress-manual-snapshot \
 --query "DBSnapshots[0].DBSnapshotArn" --output text

Retrieve the ARN of the manual RDS snapshot before using the cross-region copy operation. section 10.3.4

$ aws rds copy-db-snapshot \
 --source-db-snapshot-identifier $SourceSnapshotArn \
 --target-db-snapshot-identifier wordpress-manual-snapshot \
 --region eu-west-1

Copy the identified RDS snapshot to the eu-west-1 region for later database restoration. section 10.3.4

How Amazon Web Services in Action, Third Edition: An in-depth guide to AWS covers it

How deep it goes
Defines RTO and RPO, then demonstrates cross-region snapshot copying; it stops short of a complete recovery runbook.
Examples
Uses a WordPress database snapshot copied from us-east-1 to eu-west-1 and a Jenkins server outage to illustrate recovery objectives.
What you can do after
Operate/configure Amazon RDS snapshot commands and evaluate recovery architectures against RTO, RPO, cost, and compliance constraints.
How it connects
Connects disaster recovery with high availability, autoscaling, CloudWatch, availability zones, Amazon RDS, snapshots, and EFS.

Also explained in

Compare how 7 books explain disaster recovery →

Related concepts

This explainer was generated by Manning's knowledge graph from the text of Amazon Web Services in Action, Third Edition: An in-depth guide to AWS. The section links point to the parts of the book it draws on.