rto-rpo-design

name	rto-rpo-design
description	Translate business RTO/RPO into ASR config + architecture

Rto Rpo Design

When to use this skill

• DR design phase
• Renegotiating SLA with business

Key concepts

• RPO ≈ replication lag — ASR healthy replication is typically minutes.
• RTO = detect + decide + execute + validate. Execute alone is often 30–60 min for multi-VM apps.
• Lower RTO requires: pre-warmed compute (CRG), automated runbooks, pre-tested DNS cutover.
• Lower RPO requires: app-tier sync (DB AG/AOAG, log shipping) — ASR alone won't deliver seconds.
• Most enterprises end up with 4-hour RTO, 15-min RPO targets at the VM layer.

Common pitfalls

• Promising 1-hour RTO with no automation, capacity reservation, or runbooks.
• Conflating replication lag (RPO) with app-consistency (still requires app-tier replication).
• Forgetting the human decision time — auto-failover is rare for production.

References

• Microsoft Learn: search for "Rto Rpo Design Azure VM" on https://learn.microsoft.com

---

Validation-first: verify every Azure fact against the Microsoft Learn MCP server (cite the Learn URL); Learn overrides built-in knowledge. If no Learn MCP server is configured, flag the answer ⚠️ unverified and mark specs as indicative. Analysis only — verify against Microsoft documentation before applying.