design-disaster-recovery

Define RTO/RPO, backup strategies, failover design, and recovery procedures.

12|1|Updated Mar 23, 2026

Search Tags:#disaster recovery #backup strategy #RTO/RPO #recovery plan #failover design

Ready to run

npx skills add https://github.com/wfukatsu/nexus-architect --skill design-disaster-recovery

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: design-disaster-recovery
Source: https://github.com/wfukatsu/nexus-architect/tree/main/skills/design-disaster-recovery
Command: npx skills add https://github.com/wfukatsu/nexus-architect --skill design-disaster-recovery

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill addresses the need for comprehensive disaster recovery planning by providing guidelines and tools for defining RTO/RPO, backup strategies, failover design, and recovery procedures.

Core Features & Use Cases

RTO/RPO Definition: Guides users in establishing Recovery Time Objectives and Recovery Point Objectives by service tier.
Backup Strategy: Offers advice on setting up backup schedules, retention periods, and testing procedures.
Failover Design: Provides insights into cross-region and cross-AZ failover strategies for business continuity.
Data Recovery Procedures: Outlines step-by-step data recovery procedures, including theScalarDB Coordinator table.
Runbooks: Offers templates for recovery procedures for various failure scenarios.
Recovery Test Plan: Includes a chaos engineering approach to validate disaster recovery plans.

Quick Start

Use the /architect:design-disaster-recovery command to start defining your disaster recovery strategy.

Frequently Asked Questions about design-disaster-recovery

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

FAQPage Schema

How do I define RTO and RPO objectives for different service tiers?▼

To define RTO and RPO objectives, you establish Recovery Time and Recovery Point Objectives categorized by service tier. This structured approach ensures your disaster recovery planning aligns specific recovery targets with business continuity requirements.

What is the best way to design a cross-region failover strategy for business continuity?▼

Designing a cross-region failover strategy requires insights into cross-AZ and cross-region configurations. This approach provides architectural guidelines to ensure system resilience and maintain business continuity during regional disasters.

How do I create a disaster recovery backup strategy with proper retention schedules?▼

Creating a disaster recovery backup strategy involves setting up backup schedules, retention periods, and testing procedures. This ensures your data remains protected and recoverable while validating your retention policies meet recovery needs.

Can I use chaos engineering to test my disaster recovery plan?▼

You can use chaos engineering to validate your disaster recovery plan through a structured recovery test plan. This approach proactively tests system resilience by simulating failure scenarios to ensure your recovery procedures function correctly.

How do I build step-by-step data recovery runbooks for failure scenarios?▼

Building data recovery runbooks involves outlining step-by-step recovery procedures and using templates for various failure scenarios. This provides clear, actionable instructions for data recovery during actual disasters.