Smelling Smoke? How to Design a Disaster Recovery Strategy...
summary
Cloud Foundry disaster recovery combines HA patterns (active‑active, active‑passive) with measurable RTO/RPO decisions and a practical backup toolchain: BOSH Backup and Restore (BBR) CLI orchestrates SSHed scripts to capture director state, VM artifacts, databases and blobstore content but does not implement release‑specific backups, it relies on release authors to supply scripts. Guidance: align backup frequency to RPO (daily is common, hourly possible with external blobstores), automate via CI (Concourse tasks exist) and routinely test full restores.
AI-written summary · about
chapters (17)
- 0:00Introduction
- 0:50Why do I have to think about disaster recovery
- 2:05User errors
- 3:36Disaster recovery and business continuity
- 4:21What is business impact
- 5:16Disaster recovery vs business continuity
- 7:11Thinking isnt about time
- 7:52High availability
- 9:49High availability challenges
- 11:03Measuring your needs
- 11:49Recovering workloads
- 12:29RTO and RPO
- 13:19Solutions
- 15:00Backup and restore
- 18:40Backup Frequency
- 21:03Hybrid Approach
- 21:27Questions
related talks
53mResiliency and Availability Design Patterns for the Cloud
22mEvolution of Disaster Recovery @ Meta
29mBuilding Resilient Systems
46mKubernetes Stateful Application Disaster Recovery with Zero Data Loss
35mDesign patterns for application resiliency
20mTaking Cloud to Extremes: Scaled-Down, Highly-Available, and Mission-Critical
21mA Roadmap to Active Multi Cloud
49mPatterns for resilient, highly available cloud architectures