metodologia-disaster-recovery

Plan disaster recovery with RPO/RTO targets and tiered failover patterns.

Updated Mar 31, 2026

Search Tags:#runbooks #disaster-recovery #business-continuity #rpo #rto #failover-design #bia

Ready to run

npx skills add https://github.com/JaviMontano/metodologia-propuesta-agent-public --skill metodologia-disaster-recovery

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: metodologia-disaster-recovery
Source: https://github.com/JaviMontano/metodologia-propuesta-agent-public/tree/main/.claude/skills/specialized/disaster-recovery
Command: npx skills add https://github.com/JaviMontano/metodologia-propuesta-agent-public --skill metodologia-disaster-recovery

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Disaster recovery planning and business continuity for organizations, defining recovery objectives, failover patterns, and executable playbooks to minimize downtime.

Core Features & Use Cases

DR plans, recovery runbooks, and DR/test calendars for critical systems
RPO/RTO mapping per system and tiered failover strategies (active-active, active-passive, pilot light, warm standby)
Integration of Business Impact Analysis (BIA) with recovery planning
Produce runbooks with roles, contacts, procedures, and escalation paths
Deliverables: DR plan, runbooks, and testing calendars
Use cases: plan DR, define RPO/RTO, design failover, create BCP, tabletop exercises

Quick Start

Define a DR strategy for your system and generate a DR plan, runbooks, and a testing calendar.

Frequently Asked Questions about metodologia-disaster-recovery

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

FAQPage Schema

How do I create a disaster recovery plan with defined RPO and RTO targets?▼

Disaster recovery planning maps per-system RPO/RTO targets to tiered failover strategies, producing executable runbooks with roles, contacts, procedures, and escalation paths. It aligns your recovery objectives with Business Impact Analysis to minimize downtime.

What is the difference between active-active and pilot light failover design?▼

Failover design patterns range from active-active for immediate recovery to pilot light for minimal pre-provisioned resources. Your choice depends on per-system RPO/RTO targets, with warm standby and active-passive offering intermediate recovery speed and cost balances.

How do I build recovery runbooks for business continuity planning?▼

Recovery runbooks document step-by-step procedures, assign roles and contacts, and define escalation paths for incident response. They integrate BIA alignment and traceable evidence tagging to ensure executable business continuity during failures.

Can I use this to plan tabletop exercises and DR testing calendars?▼

Disaster recovery planning includes generating DR and test calendars for critical systems. You can schedule tabletop exercises and failover tests against defined RPO/RTO targets to validate runbook effectiveness and tiered failover readiness.

What do I need to define before generating a DR plan and failover strategy?▼

You need a defined DR strategy for your system, including identified critical systems and Business Impact Analysis data. This establishes the RPO/RTO targets and tier classification required to generate runbooks and testing calendars.

Why should I align Business Impact Analysis with recovery planning?▼

BIA alignment ensures your recovery objectives match business priorities. It drives per-system RPO/RTO enforcement and failover design selection, producing traceable evidence tagging that validates your DR plan meets continuity requirements.