Schroedingers Backup
summary
A real‑world recovery playbook: seven of nine home‑data‑center servers fail over two weeks and everything is rebuild nine servers and restored within two weeks using snapshots, dumps and automation. Uses KVM and LVM snapshots, Clonezilla images, hourly Postgres/MySQL dumps, rsync over SSH, and configuration managed with Ansible (puppet/chef/salt equivalents noted). Builds an isolated VM test lab that replays snapshots plus hourly DB dumps and drives an automated restore pipeline via MQTT instead of Jenkins; one vendor restore failure still costs a day.
AI-written summary · about
chapters (15)
- 0:00Introduction and speaker intro
- 1:03Schrödinger’s backup concept
- 4:41Backup importance and real-world example
- 6:31Four types of system integrations
- 8:25Backup techniques for virtual machines
- 10:32Configuration automation and templating
- 13:28Application deployment examples
- 15:59Database and application backups
- 17:23Verifying backup integrity
- 22:33Trusting end users and developers
- 24:26Automating restore and testing
- 25:39Testing multi-server environments
- 29:38Application-specific backup tools
- 31:06Automating backup testing
- 32:00Q&A session
related talks
25mData protection design for business continuity
25mAutomating Disaster Recovery: The Ultimate Reliability Challenge
06mIGNITE: Schrödinger’s backups: how to avoid uncertainty
33mPlan to Fail: A Good Captain Doesn’t Sail Without Life Rafts
54mFive hybrid cloud backup and disaster recovery mistakes to avoid
59mTech deep dive: Backup & on-demand disaster recovery
28mBurning Down The House: How to Plan for and Deal with Disaster Recovery in CF
33mPlan to Fail: A Good Captain Doesn’t Sail Without Life Rafts