disaster-recovery-planner

Design disaster recovery strategies including backup, failover, RTO/RPO planning, and multi-region deployment for business continuity.

⭐2stars🔀1forks📁View on GitHub🕐Updated Nov 28, 2025⬇️2downloads

When & Why to Use This Skill

The Disaster Recovery Planner is a specialized Claude skill designed to architect resilient business continuity solutions. It assists in defining Recovery Time Objectives (RTO) and Recovery Point Objectives (RPO), configuring multi-region failover mechanisms using tools like AWS Route53, and automating database backup and retention scripts to safeguard critical infrastructure against data loss and downtime.

Use Cases

  • Architecting multi-region failover systems for mission-critical applications to maintain high availability during regional outages.
  • Defining and documenting RTO/RPO targets across different service tiers to optimize disaster recovery costs and performance.
  • Implementing automated database backup strategies with point-in-time recovery (PITR) and cloud storage integration.
  • Developing comprehensive disaster recovery runbooks and quarterly testing procedures to ensure organizational readiness.
namedisaster-recovery-planner
descriptionDesign disaster recovery strategies including backup, failover, RTO/RPO planning, and multi-region deployment for business continuity.
allowed-tools[Read, Write, Edit, Bash, Grep, Glob]

Disaster Recovery Planner

Design comprehensive disaster recovery strategies for business continuity.

RTO/RPO Targets

Tier RTO RPO Cost Use Case
Critical < 1 hour < 5 min High Payment, Auth
Important < 4 hours < 1 hour Medium Orders, Inventory
Standard < 24 hours < 24 hours Low Reports, Analytics

Multi-Region Failover

# AWS Route53 Health Checks and Failover
Resources:
  PrimaryHealthCheck:
    Type: AWS::Route53::HealthCheck
    Properties:
      HealthCheckConfig:
        Type: HTTPS
        ResourcePath: /health
        FullyQualifiedDomainName: api-us-east-1.example.com
        Port: 443
        RequestInterval: 30
        FailureThreshold: 3

  DNSFailover:
    Type: AWS::Route53::RecordSet
    Properties:
      HostedZoneId: Z123456
      Name: api.example.com
      Type: A
      SetIdentifier: Primary
      Failover: PRIMARY
      AliasTarget:
        HostedZoneId: Z123456
        DNSName: api-us-east-1.example.com
      HealthCheckId: !Ref PrimaryHealthCheck

Database Backup Strategy

# Automated backup script
#!/bin/bash
TIMESTAMP=$(date +%Y%m%d_%H%M%S)
DB_NAME="production_db"
S3_BUCKET="s3://backups-${DB_NAME}"
RETENTION_DAYS=30

# Full backup daily
pg_dump -Fc $DB_NAME | \
  aws s3 cp - "${S3_BUCKET}/full/${TIMESTAMP}.dump"

# Point-in-time recovery (WAL archiving)
aws s3 sync /var/lib/postgresql/wal_archive \
  "${S3_BUCKET}/wal/" --delete

# Cleanup old backups
aws s3 ls "${S3_BUCKET}/full/" | \
  while read -r line; do
    createDate=$(echo $line | awk '{print $1" "$2}')
    if [[ $(date -d "$createDate" +%s) -lt $(date -d "-${RETENTION_DAYS} days" +%s) ]]; then
      fileName=$(echo $line | awk '{print $4}')
      aws s3 rm "${S3_BUCKET}/full/${fileName}"
    fi
  done

Best Practices

  • ✅ Test DR procedures quarterly
  • ✅ Automate backup verification
  • ✅ Document runbooks thoroughly
  • ✅ Multi-region for critical systems
  • ✅ Monitor backup success/failure