| name | recovery-plans |
| description | ASR recovery plans — multi-VM ordering, scripts, manual gates |
Recovery Plans
When to use this skill
- Multi-tier app needs ordered recovery
- Coordinating with DB failover
Key concepts
- Group VMs into groups that fail over in sequence (1–7).
- Add manual actions (e.g. 'DBA confirms DB failover complete').
- Pre/post scripts are Azure Automation runbooks — modify DNS, attach LB, run smoke tests.
- Test the recovery plan exactly as it would run in real failover; partial tests miss timing bugs.
- Version the plan in source control (export JSON) and keep in sync with deployments.
Common pitfalls
- Putting too many VMs in one group — parallel failover storms saturate ASR.
- Not testing scripts in the test-failover network — they fail in real DR.
- Drift between deployed VMs and recovery plan inclusions.
References
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.