How Can We Make Data Integrity Easy?
summary
Argues for building a reusable managed framework that orchestrates backup → restore image → verification pipeline → back to production so recovery is a tested, repeatable workflow. Describes real costs: restoring petabytes consumes network, CPU and storage and can be dangerous; a simple implementation was about thousand lines of Go and required ongoing tech support (circa one support interaction every ~30% of the recovery cycle) before it matured. Claims 360-degree recovery is achievable with small, slottable custom logic and repeated automated tests.
AI-written summary · about
chapters (9)
- 0:00Introduction
- 2:36Data Integrity
- 4:57What do we need
- 9:37Our mission
- 14:15How
- 14:25Why
- 14:55Uncomfortable truths
- 17:13Ownership of the problem
- 19:19Conclusion
related talks
31mTradeoffs in Resiliency: Managing the Burden of Data Recoverability
47mDisaster Recovery Strategies for SQL Server
47mEfficiency up, failed releases down; compliant production data for your test and dev environments
58mDefend your data at scale: 3 steps to increase cyber security- 47mDisaster Recovery Strategies for SQL Server
38mProtecting Database Backups From Ransomware and Malicious Intent
06mIGNITE: Schrödinger’s backups: how to avoid uncertainty
27mIt's all about the Data