disaster-recovery

Name: disaster-recovery
Availability: InStock
Author: timequity

Design disaster recovery plans with RTO and RPO targets.

6|Updated Dec 7, 2025

Search Tags:#backup #continuity #DR #disaster-recovery

Ready to run

npx skills add https://github.com/timequity/plugins --skill disaster-recovery

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: disaster-recovery
Source: https://github.com/timequity/plugins/tree/main/craft-coder/infra/disaster-recovery
Command: npx skills add https://github.com/timequity/plugins --skill disaster-recovery

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill covers backup strategies, disaster recovery planning, and test-driven DR runbooks to minimize downtime and data loss.

Core Features & Use Cases

RTO/RPO & DR Strategies: Definition and options (backup/restore, warm standby, multi-site).
Backup Techniques: Database dumps and automated backups using IaC.
Runbooks & Testing: DR runbooks with failover and failback steps.

Quick Start

Review the DR runbook and perform a backup restore test to validate recovery readiness.

Frequently Asked Questions about disaster-recovery

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I define recovery objectives for disaster recovery planning?▼

Recovery objectives consist of RTO (Recovery Time Objective) and RPO (Recovery Point Objective). RTO specifies the maximum acceptable downtime; RPO defines the maximum tolerable data loss measured in time. These metrics drive your choice of backup strategy, replication approach, and failover architecture across cloud and on-premises environments.

What backup strategies minimize data loss and downtime?▼

Backup strategies include full database dumps with automated scheduling via Infrastructure as Code, cross-region replication for warm standby capacity, and multi-site deployments for active-active resilience. Each strategy trades off complexity and cost against RTO and RPO targets to meet your business continuity requirements.

How do I test disaster recovery readiness without disrupting production?▼

DR testing uses runbooks that document failover and failback steps, then executes backup restore tests in isolated environments to validate recovery procedures. Verification procedures confirm data integrity and system functionality, while stakeholder communications ensure teams understand their roles before an actual incident.

Can I automate database backups across cloud and on-premises environments?▼

Yes. Automated backups leverage Infrastructure as Code to schedule and execute database dumps consistently across hybrid cloud and on-premises infrastructure, eliminating manual intervention and ensuring backup consistency for both failover and compliance requirements.

What's the difference between backup/restore, warm standby, and multi-site DR strategies?▼

Backup/restore recovers from stored snapshots with longer RTO but lower cost. Warm standby maintains a hot replica for faster failover. Multi-site keeps active systems in multiple locations for minimal RTO and RPO. Strategy selection depends on your defined recovery objectives and acceptable infrastructure investment.

Why do I need documented runbooks for disaster recovery?▼

Runbooks document step-by-step failover and failback procedures, recovery verification checks, and stakeholder communication protocols. They eliminate guesswork during high-stress incidents, ensure consistent execution across team members, and serve as the basis for regular DR testing and validation.