Database Backup and Recovery: RPO and RTO Explained
Database backup and recovery is one of the most critical operational concerns for any system that stores important data. Two metrics define recovery capability: Recovery Point Objective (RPO) and Recovery Time Objective (RTO). Understanding these helps you define and communicate your resilience requirements.
Recovery Point Objective (RPO)
RPO is the maximum acceptable amount of data loss in the event of a failure — measured in time. An RPO of 1 hour means you can accept losing up to 1 hour of transactions. This drives backup frequency: to achieve 1-hour RPO, you need at least hourly backups.
Recovery Time Objective (RTO)
RTO is the maximum acceptable time to restore service after a failure. An RTO of 4 hours means you need to be able to restore from backup and resume operations within 4 hours of a failure. This drives your recovery infrastructure and process.
Backup Types
- Full backup: Complete copy of all data. Slowest to create, fastest to restore.
- Incremental backup: Only data changed since the last backup. Fastest to create, slowest to restore (must apply each increment).
- Point-in-time recovery (PITR): Continuous log shipping enabling recovery to any point in time — standard for managed database services (AWS RDS, Cloud SQL).
Our Backup Architecture
All managed database services we use include automated backups with PITR. We configure backup retention to match client RPO requirements, and implement offsite backup copies for disaster recovery. We test restoration procedures — untested backups are not reliable backups.