smithery/timequity

disaster-recovery

Backup strategies, disaster recovery planning, and business continuity.

Installation

$ npx skills add smithery/timequity --skill disaster-recovery

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

Also in this package

Other skills from smithery/timequity · top by installs.

npx skills add smithery/timequity

Browse all from smithery/timequity

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 2,138 B
  • docs SUMMARY.md 96 B

History

  1. First recorded snapshot · 0 installs

SKILL.md

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

  1. Detect - Monitor alerts for primary failure
  2. Assess - Confirm failure, estimate recovery
  3. Decide - Failover if RTO exceeded
  4. Execute - Run failover procedure
  5. Verify - Test functionality
  6. Communicate - Update stakeholders

Failback Steps

  1. Verify primary is healthy
  2. Sync data from secondary
  3. Switch traffic back
  4. 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)