Your RTO Is a Hypothesis: Drill-Based Verification of Recovery Objectives in Multi-Cloud

Main Article Content

Narayana Rajasekhar Vemburaj

Abstract

While all regulated businesses have recovery goals, few can demonstrate them. A business-continuity document is a theory about how a complex, drifting, multi-cloud estate performs on its worst day, and most businesses run a tabletop exercise against the architecture as it was when the document was created, at least once a year. This article does not treat RTO and RPO as objectives but rather as claims that can be measured and it outlines a discipline for certifying RTO and RPO – Recovery Certification – that I use for certification and which is based on a drill. Recovery objectives can only be validated by some evidence of it: by fielding full-path drills that fail on actual workloads, by providing data-loss and recovery-time distributions and confidence bounds rather than single best-case figures, and by providing expiry rules by which a drill result goes out of current currency as the estate drifts. Those partial drills are only at the estate level on a dependency graph, and the untested seams between clouds are where multi-cloud recovery fails. Or the distance between the recovery a document has announced and the recovery a drill a ledger has used remains hidden until the worst day of the year at which point only the latter matters.

Article Details

Section
Articles