design-backup-dr-recovery

Name: design-backup-dr-recovery
Availability: InStock
Author: Sir-chawakorn

Design backup and disaster-recovery strategies for stateful datastores.

9|3|Updated Jun 13, 2026

Search Tags:#database #resilience #backup #sre #disaster-recovery #pitr

Ready to run

npx skills add https://github.com/Sir-chawakorn/sanook-cli --skill design-backup-dr-recovery

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: design-backup-dr-recovery
Source: https://github.com/Sir-chawakorn/sanook-cli/tree/main/skills/design-backup-dr-recovery
Command: npx skills add https://github.com/Sir-chawakorn/sanook-cli --skill design-backup-dr-recovery

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill addresses the critical risk of data loss by providing a structured framework to design, implement, and validate robust backup and disaster recovery strategies that meet specific business RPO and RTO requirements.

Core Features & Use Cases

Strategy Design: Define RPO/RTO tiers and implement continuous log archiving (PITR) for databases like PostgreSQL, MySQL, and MongoDB.
Resilience Architecture: Configure 3-2-1 backup layouts with immutable storage to protect against ransomware and accidental deletion.
Validation: Automate restore drills to ensure backups are functional and meet recovery time objectives.

Quick Start

Use the design-backup-dr-recovery skill to audit our current PostgreSQL backup strategy and define the RPO and RTO targets for our production database.

Frequently Asked Questions about design-backup-dr-recovery

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

FAQPage Schema

How do I design a disaster recovery strategy that meets specific RPO and RTO targets?▼

To design a disaster recovery strategy, define RPO/RTO tiers and implement continuous log archiving for point-in-time-recovery. This framework structures your data recovery plan to meet specific business continuity objectives and validate restore times.

What is the 3-2-1 backup layout and how does it protect against ransomware?▼

The 3-2-1 backup layout uses immutable storage to protect data against ransomware and accidental deletion. This architecture maintains multiple copies across different media, ensuring at least one offline backup remains unalterable during an attack.

How do I set up point-in-time-recovery (PITR) for PostgreSQL and MongoDB stateful datastores?▼

Point-in-time-recovery for stateful datastores like PostgreSQL and MongoDB requires continuous log archiving. This process captures granular database changes, allowing you to restore data to a specific moment before data loss or corruption occurs.

Can I automate restore drills to validate my database backup functionality?▼

Yes, you can automate restore drills to validate database backup functionality. Automating these recovery tests ensures your backups are functional and actively meet your defined recovery time objectives during a real failure.

How do I configure cross-region failover and split-brain fencing for database resilience?▼

Configuring cross-region failover and split-brain fencing involves designing resilience architectures for stateful datastores. This setup prevents simultaneous primary nodes from causing data corruption during regional outages.

When do I need immutable retention for database backups?▼

You need immutable retention for database backups when protecting against ransomware and accidental deletion. This approach secures continuous log archives, ensuring backup data cannot be modified or deleted before the retention period expires.