RTO & RPO – Best Practices in Hybrid Architectures
summary
Defines RTO as time and RPO as allowable data loss, shows a concrete mismatch: daily backups cannot meet an 8-hour RPO, and a claimed 60-minute RTO requires automation and infra-as-code. Demonstrates AWS tools: AMIs and snapshots copied cross-region, S3 replication/versioning, RDS automated backups (up to 14 days) and replicas, Route 53 health checks and failover, EFS/Storage Gateway for hybrid backups, and Terraform/CloudFormation to rebuild. Compares pilot light, warm standby and multi-site active-active with cost vs recovery-time tradeoffs and advises monthly DR tests.
AI-written summary · about
chapters (9)
- 0:00Start
- 4:27RPO and RTO
- 10:44Latest Events
- 18:34Networking
- 27:05Restore Phase
- 28:20Pilot Light
- 31:05Fully Working Low-Capacity Standby
- 34:52Recovery Strategies
- 36:00CASE SCENARIO
related talks
25mData protection design for business continuity
27mState of the Union on Disaster Recovery
14mDisaster Recovery preparedness
41mResiliency and data residency
47mBuilding Resilience
32mDisaster recovery strategies for increased resiliency
14mExpect the unexpected: Building resilience with AWS
41mWays to optimize Cloud Disaster Recovery cost