disaster-recovery

Name: disaster-recovery
Availability: InStock
Author: ryukyagamilight

Plan disaster recovery with RTO/RPO definitions and failover procedures for MySQL, PostgreSQL, and Redis.

1|Updated Jan 31, 2026

Search Tags:#disaster recovery #backup #business continuity #failover #restoration #rpo #rto

Ready to run

npx skills add https://github.com/ryukyagamilight/terminal-skills --skill disaster-recovery-ryukyagamilight

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: disaster-recovery
Source: https://github.com/ryukyagamilight/terminal-skills/tree/main/backup/disaster-recovery
Command: npx skills add https://github.com/ryukyagamilight/terminal-skills --skill disaster-recovery-ryukyagamilight

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill helps you plan, implement, and execute disaster recovery strategies to minimize data loss and downtime in the event of a system failure or catastrophe.

Core Features & Use Cases

RTO/RPO Definition: Understand and define Recovery Point Objectives (RPO) and Recovery Time Objectives (RTO).
Recovery Strategies: Implement cold, warm, and hot standby solutions.
Database & System Recovery: Provides commands for restoring MySQL, PostgreSQL, Redis, file systems, and bootloaders.
Failover Mechanisms: Details on Keepalived and DNS failover.
Use Case: Quickly restore critical services after a major outage by following predefined recovery steps and failover procedures.

Quick Start

Execute the disaster recovery plan for critical systems by following the outlined steps for database and system restoration.

Frequently Asked Questions about disaster-recovery

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

FAQPage Schema

How do I define RPO and RTO for a disaster recovery plan?▼

Defining RPO and RTO requires calculating maximum tolerable data loss and downtime windows for business continuity. This Skill provides structured commands to establish Recovery Point Objective and Recovery Time Objective thresholds for critical systems.

What is the difference between cold, warm, and hot standby recovery strategies?▼

Cold, warm, and hot standby strategies differ in recovery speed and operational cost. This disaster recovery planning tool helps you implement these failover configurations, balancing immediate restoration needs against infrastructure maintenance expenses.

How do I restore MySQL, PostgreSQL, and Redis databases after a system failure?▼

Restoring MySQL, PostgreSQL, and Redis databases requires specific recovery commands. This disaster recovery Skill provides detailed procedures for database restoration, enabling rapid data recovery and failover execution during critical outage scenarios.

Can I use Keepalived and DNS failover for application high availability?▼

Keepalived and DNS failover are supported mechanisms for application high availability. This disaster recovery Skill details how to configure these failover systems to rapidly switch traffic and restore critical services during an infrastructure failure.

How do I recover a corrupted file system and bootloader after a disaster?▼

Recovering a corrupted file system and bootloader requires executing targeted system restoration commands. This disaster recovery Skill provides detailed procedures to restore file systems and bootloaders, enabling rapid operating system recovery after critical failures.

When should I choose a hot standby failover over a cold standby strategy?▼

Choose hot standby failover when near-zero downtime is required, as it maintains a live replica for immediate restoration, unlike cold standby which needs full provisioning. This disaster recovery Skill implements both strategies based on your RTO thresholds.