IGNITE: Schrödinger’s backups: how to avoid uncertainty
summary
Automated restore tests run as part of CI so production backups are actually restorable not just scheduled. A harness creates databases, populates tables with features (CDC streams, indexes), uploads to S3, triggers backup and restore, and compares schemas and data; mismatches fail the build. Developers must add new-feature cases to the end-to-end backup test, which catches missing indexes or missing CDC after restore and shifts culture. Managed instances run in Nebulous Cloud.
AI-written summary · about
related talks
32mSchroedingers Backup
31mTesting in Production
20mHow Can We Make Data Integrity Easy?
46mExploratory Testing: How to Find Backups That Won't Restore
28mBurning Down The House: How to Plan for and Deal with Disaster Recovery in CF
27mIt's all about the Data
27mBackup and Restore: Discover Best Practices for a Distributed Database Backup Strategy
33mPlan to Fail: A Good Captain Doesn’t Sail Without Life Rafts