Skip to main content
CloudBit Logo
Operations

Backup and disaster recovery on AWS: how to define RPO and RTO (and test them)

Having backups isn't enough: you need to know how much data you can lose, how long you can take to recover, and to have tested the restore before you need it.

· 7 min read · CloudBit team

RPO and RTO in business terms

RPO (recovery point objective) is how much data you can afford to lose: an hour, a day. RTO (recovery time objective) is how long the service can be down before the impact becomes unacceptable. They are defined with the business, per application, and they drive the strategy and the cost.

Four strategies, from lowest to highest cost

Backup and restore: the cheapest, with an RTO of hours. Pilot light: data is replicated and minimal infrastructure is ready to scale. Warm standby: a scaled-down version runs in another region. Active-active: several regions serve traffic at once, with near-zero RTO and the highest cost.

AWS Backup as the central point

AWS Backup centralizes copies of RDS, DynamoDB, EBS, EFS and S3 with tag-based policies. Copies to another account and region protect against human error or compromised access, and vault lock prevents anyone from deleting them early.

Infrastructure as code to recover fast

If the infrastructure is in Terraform or CloudFormation, recreating it in another region means running the code with different parameters. Without IaC, recovery depends on documentation that is usually outdated and on people's memory.

Test the restore

A backup that has never been restored is an assumption. Schedule periodic tests, measure the real time against the agreed RTO and document the steps. AWS Backup restore testing can automate part of this check.

Frequently asked questions

Want to apply this at your company?

Book a free 30-minute technical consultation.

Talk to a specialist