Planning Disaster Recovery
Overview
Design disaster recovery (DR) plans for cloud infrastructure covering RTO/RPO requirements, multi-region failover, data replication, and automated recovery procedures. Generate runbooks, Terraform for standby infrastructure, and automated failover scripts for databases, compute, and networking.
Prerequisites
- Complete inventory of production infrastructure components and dependencies
- Defined RTO (Recovery Time Objective) and RPO (Recovery Point Objective) per service tier
- Cloud provider CLI authenticated with permissions for multi-region resource management
- Cross-region networking configured (VPC peering, Transit Gateway, or VPN)
- Backup and replication mechanisms already in place or planned
Instructions
- Catalog all production services with their criticality tier (Tier 1: < 15 min RTO, Tier 2: < 1 hour, Tier 3: < 24 hours)
- Map dependencies between services to identify single points of failure and cascading failure paths
- Design the DR strategy per tier: active-active for Tier 1, pilot light or warm standby for Tier 2, backup-restore for Tier 3
- Generate Terraform for standby region infrastructure: VPC, subnets, security groups, and scaled-down compute
- Configure database replication: RDS cross-region read replicas, DynamoDB global tables, or Cloud SQL cross-region replicas
- Set up DNS failover using Route 53 health checks, Cloud DNS routing policies, or global load balancers
- Create automated failover scripts: promote read replica to primary, update DNS records, scale up standby compute
- Document the DR runbook with step-by-step procedures, responsible parties, and communication plans
- Schedule quarterly DR drills: simulate region failure, execute the runbook, measure actual RTO/RPO, and document gaps
- Set up monitoring for replication lag, backup freshness, and standby infrastructure health
Output
- DR plan document with service tiers, RTO/RPO targets, and recovery procedures
- Terraform modules for standby region infrastructure
- Automated failover scripts (database promotion, DNS switching, compute scaling)
- DR drill checklist and post-drill assessment template
- Monitoring dashboards for replication lag and backup status
Error Handling
| Error |
Cause |
Solution |
Replication lag exceeds RPO |
Network throughput insufficient or write volume too high |
Increase replication instance size, enable compression, or implement write throttling during peak |
DNS failover not triggering |
Health check misconfigured or TTL too high |
Verify health check endpoint returns proper status; reduce DNS TTL to 60 seconds before drill |
Standby database promotion failed |
Replication broken or standby in inconsistent state |
Check replication status; if broken, restore from latest snapshot and re-establish replication |
Insufficient capacity in DR region |
Instance types unavailable in standby region |
Pre-provision reserved capacity in DR region or use multiple instance type options |
Application cannot connect after failover |
Connection strings hardcoded to primary region endpoints |
Use DNS-based endpoints (CNAME/Route 53) instead of direct IPs; parameterize region in config |
Examples
- "Create a disaster recovery plan for a 3-tier web application on AWS with < 15 minute RTO for the API layer and < 1 hour for batch processing."
- "Generate Terraform for a warm standby in us-west-2 with RDS cross-region read replica, scaled-down ECS cluster, and Route 53 failover routing."
- "Design a DR drill that simulates primary region failure, executes automated failover, and validates data integrity in the standby region."
Resources
Converted and distributed by TomeVault — claim your Tome and manage your conversions.
1---2name: jeremylongshore-claude-code-plugins-plus-skills-planning-dis3description: Planning Disaster Recovery4---5# Planning Disaster Recovery67## Overview89Design disaster recovery (DR) plans for cloud infrastructure covering RTO/RPO requirements, multi-region failover, data replication, and automated recovery procedures. Generate runbooks, Terraform for standby infrastructure, and automated failover scripts for databases, compute, and networking.1011## Prerequisites1213- Complete inventory of production infrastructure components and dependencies14- Defined RTO (Recovery Time Objective) and RPO (Recovery Point Objective) per service tier15- Cloud provider CLI authenticated with permissions for multi-region resource management16- Cross-region networking configured (VPC peering, Transit Gateway, or VPN)17- Backup and replication mechanisms already in place or planned1819## Instructions20211. Catalog all production services with their criticality tier (Tier 1: < 15 min RTO, Tier 2: < 1 hour, Tier 3: < 24 hours)222. Map dependencies between services to identify single points of failure and cascading failure paths233. Design the DR strategy per tier: active-active for Tier 1, pilot light or warm standby for Tier 2, backup-restore for Tier 3244. Generate Terraform for standby region infrastructure: VPC, subnets, security groups, and scaled-down compute255. Configure database replication: RDS cross-region read replicas, DynamoDB global tables, or Cloud SQL cross-region replicas266. Set up DNS failover using Route 53 health checks, Cloud DNS routing policies, or global load balancers277. Create automated failover scripts: promote read replica to primary, update DNS records, scale up standby compute288. Document the DR runbook with step-by-step procedures, responsible parties, and communication plans299. Schedule quarterly DR drills: simulate region failure, execute the runbook, measure actual RTO/RPO, and document gaps3010. Set up monitoring for replication lag, backup freshness, and standby infrastructure health3132## Output3334- DR plan document with service tiers, RTO/RPO targets, and recovery procedures35- Terraform modules for standby region infrastructure36- Automated failover scripts (database promotion, DNS switching, compute scaling)37- DR drill checklist and post-drill assessment template38- Monitoring dashboards for replication lag and backup status3940## Error Handling4142| Error | Cause | Solution |43|-------|-------|---------|44| `Replication lag exceeds RPO` | Network throughput insufficient or write volume too high | Increase replication instance size, enable compression, or implement write throttling during peak |45| `DNS failover not triggering` | Health check misconfigured or TTL too high | Verify health check endpoint returns proper status; reduce DNS TTL to 60 seconds before drill |46| `Standby database promotion failed` | Replication broken or standby in inconsistent state | Check replication status; if broken, restore from latest snapshot and re-establish replication |47| `Insufficient capacity in DR region` | Instance types unavailable in standby region | Pre-provision reserved capacity in DR region or use multiple instance type options |48| `Application cannot connect after failover` | Connection strings hardcoded to primary region endpoints | Use DNS-based endpoints (CNAME/Route 53) instead of direct IPs; parameterize region in config |4950## Examples5152- "Create a disaster recovery plan for a 3-tier web application on AWS with < 15 minute RTO for the API layer and < 1 hour for batch processing."53- "Generate Terraform for a warm standby in us-west-2 with RDS cross-region read replica, scaled-down ECS cluster, and Route 53 failover routing."54- "Design a DR drill that simulates primary region failure, executes automated failover, and validates data integrity in the standby region."5556## Resources5758- AWS Disaster Recovery: https://docs.aws.amazon.com/whitepapers/latest/disaster-recovery-workloads-on-aws/59- GCP DR planning: https://cloud.google.com/architecture/dr-scenarios-planning-guide60- Azure Business Continuity: https://learn.microsoft.com/en-us/azure/reliability/61- DR strategy patterns: https://aws.amazon.com/blogs/architecture/disaster-recovery-dr-architecture-on-aws-part-i/6263---64> Converted and distributed by [TomeVault](https://tomevault.io/claim/jeremylongshore) — claim your Tome and manage your conversions.65<!-- tomevault:4.0:skill_md:2026-04-11 -->
tomevault-io