{"id":5522,"date":"2026-11-16T05:50:00","date_gmt":"2026-11-16T05:50:00","guid":{"rendered":"https:\/\/www.devopssupport.in\/blog\/?p=5522"},"modified":"2026-11-18T14:50:00","modified_gmt":"2026-11-18T14:50:00","slug":"managed-support-recovery-explained","status":"publish","type":"post","link":"https:\/\/www.devopssupport.in\/blog\/managed-support-recovery-explained\/","title":{"rendered":"What Your Support Partner Owes You on DisasterRecoveryOps"},"content":{"rendered":"<p>Companies that hand their servers to a managed-support partner often assume the partner has also taken over the question of what happens in a disaster. Sometimes that is true; often it is not written down anywhere. Drawing on the Ops Atlas entry for DisasterRecoveryOps, this guide separates what a support contract usually covers from what recovery actually requires, and shows how to test the gap with evidence instead of reassurance.<\/p>\n<h2>Start with the plain definition<\/h2>\n<p>Disaster recovery is the set of arrangements for getting an IT service working again after a serious disruption. Cloud providers describe it as a subset of the broader business-continuity effort, which also covers people, premises and suppliers. The Atlas adds a useful nuance from the US government&#8217;s own guidance: its formal disaster recovery plan applies to disruptions that require relocation, meaning moving the work somewhere else. Smaller outages belong to ordinary incident handling.<\/p>\n<p>DisasterRecoveryOps, the Atlas says, is the label for running all of this as a continuing operational practice. It is a young term, but the questions it covers are easy to state: how fast must we be back, how much recent work can we lose, who decides to switch, and how do we prove it works?<\/p>\n<h2>Four questions a support contract should answer<\/h2>\n<ol>\n<li><strong>Who owns the recovery objectives?<\/strong> A support partner can propose numbers, but only the business can sign them off, because only the business knows what an hour of downtime costs.<\/li>\n<li><strong>Who holds the authority to declare a failover?<\/strong> If the answer is &#8220;whoever is on call&#8221;, check that this person can be reached and is permitted to act.<\/li>\n<li><strong>Who runs and records drills?<\/strong> The Atlas treats rehearsal as the difference between a plan and a hope.<\/li>\n<li><strong>Who is paid to fix gaps found in a drill?<\/strong> Findings without budget become a backlog nobody reads.<\/li>\n<\/ol>\n<p>These questions tie in with the broader principle that delivery practices should be explicit and shared, a theme developed in <a href=\"https:\/\/www.devopssupport.in\/blog\/devops-principles-for-effective-software-delivery\/\">an overview of core principles for effective software delivery<\/a>.<\/p>\n<h2>Why the decision time matters so much to a support team<\/h2>\n<p>Here is the idea the Atlas returns to repeatedly: the recovery clock starts at the problem, and it includes the human decision. Its worked example reports a decision that took 25 minutes against an allowance of 16, a nine-minute overrun, and a total recovery of 64 minutes against a 60-minute objective. The technical team did their part; the delay sat in deciding.<\/p>\n<p>For a managed-support arrangement, this has a concrete implication. If your partner&#8217;s engineer must phone your manager, who must consult a director, who is travelling, the clock keeps running. A good contract therefore names a pre-authorised decision-maker, with a deputy, and sets a deadline measured backwards from the objective.<\/p>\n<h2>What the provider does and does not do for you<\/h2>\n<p>Keep two kinds of provider apart. Your cloud or hosting platform runs the underlying infrastructure. Your managed-support partner runs operations on top of it. Neither automatically owns your recovery design. Even Microsoft&#8217;s own documentation, as the Atlas cites it, says DR is not something Azure supplies on its own. The customer has to choose a design and pay for it.<\/p>\n<p>Consider the 2021 Strasbourg data-centre fire described in the entry. One site was destroyed, and some customers discovered that their copies were stored in the same place. That is an arrangement problem, not a hardware problem, and a support partner is well placed to spot it by asking where copies live relative to the thing they protect.<\/p>\n<h2>Reading a recovery scorecard like an auditor<\/h2>\n<p>Evidence beats adjectives. The Atlas example scorecard contains five numbers worth understanding: a recovery time that missed its target by four minutes, the decision overrun above, a data-loss window of 2.5 minutes against a 5-minute allowance, 67 percent of in-scope services covered by a drill, and 25 percent conformance of the written plan to what actually happened.<\/p>\n<p>The last two figures are the revealing ones. Coverage says how much of your estate has been tested at all; conformance says whether people followed the plan or improvised. A partner who reports both is giving you a view of reality, not a sales page.<\/p>\n<h2>Common ways managed recovery goes wrong<\/h2>\n<ul>\n<li><strong>Recovery steps that live in a console and in someone&#8217;s memory.<\/strong> The entry files this under &#8220;click ops&#8221;, an anti-pattern borrowed from AWS guidance.<\/li>\n<li><strong>A fence that does not fence.<\/strong> Switching a DNS route off redirects only traffic that follows DNS; batch jobs and clients with cached addresses may carry on writing to the old side.<\/li>\n<li><strong>Recovery tools that need the failed region to work.<\/strong> In AWS&#8217;s us-east-1 trouble of October 2025, STS and Identity Center sign-in broke for some users, hence the entry&#8217;s advice to keep holding recovery-only credentials outside the failure domain.<\/li>\n<li><strong>Standby capacity that has gone stale.<\/strong> Quotas and machine images drift unless somebody checks them.<\/li>\n<\/ul>\n<p>Administrators moving into this kind of work can follow the route laid out in <a href=\"https:\/\/www.devopssupport.in\/blog\/infrastructure-as-code-to-sre-why-operations-engineers-should-embrace-devops\/\">an argument for ops engineers adopting code-driven infrastructure and SRE habits<\/a>, a good companion for anyone scripting recovery steps.<\/p>\n<h2>A simple review you can ask your partner for<\/h2>\n<ol>\n<li>The signed objectives for each service, with the date they were last reviewed.<\/li>\n<li>The most recent drill report with time to decide, time to recover and data-loss window.<\/li>\n<li>The list of stores each critical service depends on and the replication lag of each.<\/li>\n<li>The failback plan, since the way home is a migration with its own hazards.<\/li>\n<li>Evidence that break-glass access was tested this quarter.<\/li>\n<\/ol>\n<p>If the partner can produce those five items in a day, you are in good shape. If it takes a month, you have learned something valuable at a cheap moment. Clarity about who does what matters here as well, and the guide to <a href=\"https:\/\/www.devopssupport.in\/blog\/a-guide-to-devops-role-titles-career-paths-job-roles\/\">DevOps role titles and the work behind them<\/a> can suggest which job descriptions to name when you request a drill.<\/p>\n<h2>Where to read the primary source<\/h2>\n<p>For the full treatment, including maturity levels and metric definitions, see <a href=\"https:\/\/www.xopsschool.com\/disasterrecoveryops\/\">the Atlas entry that defines DisasterRecoveryOps and its scope<\/a>. Its length is considerable, so begin with the decision-clock and anti-pattern sections.<\/p>\n<h2>Summing up<\/h2>\n<p>A support contract is not a recovery plan, and a recovery plan is not a drill result. Each step turns a claim into something you can check. Ask for the numbers, measure the decision, and test the way back. The cost is a few hours of engineering time each quarter; the benefit is knowing what will actually happen on the worst day.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>A plain-language explainer on what managed support covers, what recovery requires, and how to test the gap with drill evidence.<\/p>\n","protected":false},"author":8,"featured_media":5523,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[3948],"tags":[],"class_list":["post-5522","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-devops-support"],"_links":{"self":[{"href":"https:\/\/www.devopssupport.in\/blog\/wp-json\/wp\/v2\/posts\/5522","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.devopssupport.in\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.devopssupport.in\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.devopssupport.in\/blog\/wp-json\/wp\/v2\/users\/8"}],"replies":[{"embeddable":true,"href":"https:\/\/www.devopssupport.in\/blog\/wp-json\/wp\/v2\/comments?post=5522"}],"version-history":[{"count":1,"href":"https:\/\/www.devopssupport.in\/blog\/wp-json\/wp\/v2\/posts\/5522\/revisions"}],"predecessor-version":[{"id":5649,"href":"https:\/\/www.devopssupport.in\/blog\/wp-json\/wp\/v2\/posts\/5522\/revisions\/5649"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.devopssupport.in\/blog\/wp-json\/wp\/v2\/media\/5523"}],"wp:attachment":[{"href":"https:\/\/www.devopssupport.in\/blog\/wp-json\/wp\/v2\/media?parent=5522"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.devopssupport.in\/blog\/wp-json\/wp\/v2\/categories?post=5522"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.devopssupport.in\/blog\/wp-json\/wp\/v2\/tags?post=5522"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}