disaster-recovery

Plan and execute disaster recovery for databases and systems with failover strategies.

50|13|Updated Jan 19, 2026
One-click install
npx skills add https://github.com/chaterm/terminal-skills --skill disaster-recovery-chaterm
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: disaster-recovery
Source: https://github.com/chaterm/terminal-skills/tree/main/backup/disaster-recovery
Command: npx skills add https://github.com/chaterm/terminal-skills --skill disaster-recovery-chaterm

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill addresses the critical need for robust disaster recovery planning and execution, minimizing data loss and downtime in the event of a system failure or catastrophe.

Core Features & Use Cases

  • RTO/RPO Definition: Understand and define Recovery Time Objectives (RTO) and Recovery Point Objectives (RPO) to guide backup and recovery strategies.
  • Recovery Strategies: Implement various recovery methods including cold, warm, and hot standby solutions.
  • Database & System Recovery: Provides specific commands for restoring MySQL, PostgreSQL, Redis, file systems, and bootloaders.
  • Failover Mechanisms: Details on how to perform failover for services using tools like Keepalived and DNS.
  • Use Case: A company experiences a critical database failure. This Skill guides the on-call engineer through the steps to restore the database from the latest backup and apply transaction logs to meet the RPO, then orchestrates application failover to a standby instance to meet the RTO.

Quick Start

Execute the disaster recovery plan for the primary database system.

Frequently Asked Questions about disaster-recovery

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

FAQPage Schema
How do I plan disaster recovery strategies and define RTO and RPO for my systems?

Disaster recovery planning requires defining Recovery Time Objectives (RTO) and Recovery Point Objectives (RPO) to guide backup strategies, then implementing cold, warm, or hot standby solutions based on those targets to minimize downtime and data loss.

What is the best way to perform database failover and restore MySQL or PostgreSQL from backups?

Database failover and restoration involves restoring MySQL or PostgreSQL from the latest backup, applying transaction logs to meet the RPO, and orchestrating application failover to a standby instance to meet the RTO using detailed procedural commands.

How does Keepalived work for high availability and system failover during a catastrophe?

Keepalived facilitates high availability failover by managing service transitions to standby instances during a system failure, ensuring continuous operation and meeting defined RTO targets through automated or orchestrated recovery mechanisms.

Can I use cold, warm, and hot standby recovery strategies for Redis and file system restoration?

Yes, cold, warm, and hot standby recovery strategies can be applied to Redis and file system restoration, providing specific commands to recover data and bootloaders based on your defined RPO and RTO requirements.

When do I need to test my disaster recovery plan and what database systems does it cover?

Disaster recovery testing is needed to validate that your RTO and RPO targets are met during a catastrophe, covering specific procedures for MySQL, PostgreSQL, Redis, file systems, and high-availability solutions like Keepalived.

Why do I need transaction logs when restoring a critical database during a system failure?

Transaction logs are required during database restoration to apply recent transactions since the last backup, ensuring data consistency and meeting your defined Recovery Point Objective (RPO) to minimize data loss.