Marketplace

disaster-recovery

Backup strategies, disaster recovery planning, and business continuity.

$ Installer

git clone https://github.com/timequity/vibe-coder /tmp/vibe-coder && cp -r /tmp/vibe-coder/skills/infra/disaster-recovery ~/.claude/skills/vibe-coder

// tip: Run this command in your terminal to install the skill

SKILL.md

View on GitHub →

name: disaster-recovery description: Backup strategies, disaster recovery planning, and business continuity.

Disaster Recovery

RTO vs RPO

Metric	Definition	Example
RTO	Recovery Time Objective	4 hours
RPO	Recovery Point Objective	1 hour

RTO: How long until service is restored? RPO: How much data can we lose?

DR Strategies

Strategy	RTO	Cost
Backup & Restore	Hours	$
Pilot Light	Minutes	$$
Warm Standby	Minutes	$$$
Multi-Site Active	Seconds	$$$$

Backup Strategy

Database

# PostgreSQL
pg_dump -h host -U user dbname | gzip > backup.sql.gz

# MySQL
mysqldump -h host -u user -p dbname | gzip > backup.sql.gz

Automated Backups

# AWS RDS
resource "aws_db_instance" "main" {
  backup_retention_period = 7
  backup_window           = "03:00-04:00"

  # Cross-region replica for DR
  replicate_source_db = aws_db_instance.primary.arn
}

DR Runbook

Failover Steps

Detect - Monitor alerts for primary failure
Assess - Confirm failure, estimate recovery
Decide - Failover if RTO exceeded
Execute - Run failover procedure
Verify - Test functionality
Communicate - Update stakeholders

Failback Steps

Verify primary is healthy
Sync data from secondary
Switch traffic back
Monitor closely

Testing

Test Type	Frequency
Backup restore	Monthly
Failover drill	Quarterly
Full DR test	Annually

Multi-Region

Primary (us-east-1)          Secondary (us-west-2)
┌─────────────────┐          ┌─────────────────┐
│    App + DB     │ ──sync── │   DB Replica    │
└─────────────────┘          └─────────────────┘
        │                            │
        └──────── Route 53 ──────────┘
                (failover)