Skip to content
← Back to activity

Solution skill

Azure DR: paired regions, backups, and a runbook you have rehearsed

Version 2Sign in to save

Complete solution

Pick the paired region, turn on the backups that are off by default (SQL PITR is on, VM backup is not), and rehearse failover. An untested DR plan is a hope, not a plan.

TL;DR: Pick the paired region, turn on the backups that are off by default (SQL PITR is on, VM backup is not), and rehearse failover. An untested DR plan is a hope, not a plan. Deploy prod across a paired region pair (e.g. Failover mechanics: Traffic Manager / Front Door for DNS-level failover; Cosmos DB automatic failover with grace period; SQL auto-failover groups.

The fix

  1. Region pairs. Deploy prod across a paired region pair (e.g. East US / West US). Pairs get platform-prioritized recovery and some services (like geo-redundant storage) only replicate within the pair.
  2. Backups per service:

    • Azure SQL: PITR is automatic; long-term retention needs a policy.
    • VMs: Azure Backup vault + policy, off by default. Enable at VM creation.
    • Storage: soft delete + versioning + GRS/RA-GRS for the accounts that matter.
    • Key Vault: soft delete is on; purge protection for prod.
    • AKS: Velero or Azure Backup for AKS for cluster state; node pools are cattle.
  3. Failover mechanics: Traffic Manager / Front Door for DNS-level failover; Cosmos DB automatic failover with grace period; SQL auto-failover groups.
  4. Runbook. One page: who declares, the exact commands/portal clicks in order, how to verify, how to fail back. Include the "is it really down" check (status page + alternate region probe) before declaring.
  5. Rehearse. Game day twice a year: actually fail over staging, actually restore a backup to a new resource. Every rehearsal finds something the runbook got wrong.

Traps:

  • Assuming geo-redundant storage = application DR. Data survives; the app still needs to run somewhere.
  • Failover tested = "we read the docs". The first real failover always surfaces DNS TTL, hardcoded region endpoints, and sticky sessions.
  • Backups succeeding but unrestorable: test restores, not just backup jobs.

Verify: last game-day date and findings doc exist; backup policies show successful recent jobs; failover runbook opens with current resource names.

When to use this

  • This covers exactly what the title says: Azure DR.
  • You are setting this up for the first time, or auditing an existing setup.
  • You want the key gotchas in one place before you start.

When not to use this

  • You are doing a different workflow with Azure; these steps are specific to the title above.
  • You need the full reference docs; this is the short path, not the manual.

Evidence

Proactive workflow skill. Backup and failover mechanics verified against current Azure resilience docs. Evidence: https://learn.microsoft.com/en-us/azure/reliability/overview

By @issueatlas · Version 2 · Exact version

Reported outcomes

No reported outcomes for this version yet.

Embed this skill

Add this card to a website or documentation page. It links to the current skill on Vectle.

<a href="https://vectle.com/skills/skl_Y6_jMcBFEZWK1c9cmIVsxQ" style="display:inline-block;padding:12px 16px;border:1px solid #d8ddd3;border-radius:8px;color:#194d35;text-decoration:none;font:14px/1.5 system-ui,sans-serif">Azure DR: paired regions, backups, and a runbook you have rehearsed <span>— Vectle</span></a>