planning-disaster-recovery

Design disaster recovery strategies with RTO/RPO planning, backups, and failover testing.

1|Updated Feb 24, 2026
One-click install
npx skills add https://github.com/masermediagroup-stack/maser-media --skill planning-disaster-recovery-masermediagroup-stack
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: planning-disaster-recovery
Source: https://github.com/masermediagroup-stack/maser-media/tree/main/.cursor/skills/community/ai-design-components/skills/planning-disaster-recovery
Command: npx skills add https://github.com/masermediagroup-stack/maser-media --skill planning-disaster-recovery-masermediagroup-stack

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve? Designing and validating disaster recovery is complex: teams must define RTO/RPO targets, choose backup tools, configure cross-region replication, and prove recovery actually works. This Skill provides structured guidance, runbooks, and automation scripts to implement and test DR across databases, Kubernetes, and cloud platforms. ## Core Features & Use Cases - RTO/RPO Planning: Map criticality tiers to recovery objectives and select matching DR strategies (Active-Active, Warm Standby, Pilot Light). - Backup Implementation: Configure pgBackRest, Percona XtraBackup, Velero, and cloud-native backups with point-in-time recovery and retention policies. - DR Validation: Run chaos engineering tests and automated DR drills to measure actual failover times against targets. - Use Case: A platform team needs < 5 minute RPO for a production PostgreSQL database. Use this Skill to configure pgBackRest with continuous WAL archiving to S3, set up cross-region replication, and validate recovery with a monthly automated failover drill. ## Quick Start Ask the AI to design a disaster recovery plan for a production PostgreSQL database with a 1-hour RTO and 15-minute RPO, including backup configuration and a failover runbook.

Frequently Asked Questions about planning-disaster-recovery

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

FAQPage Schema
How do I set up PostgreSQL point-in-time recovery with pgBackRest?▼

Configure pgBackRest with continuous WAL archiving to S3, GCS, or Azure, then schedule weekly full and daily differential backups. Restore to a specific moment using pgbackrest with the recovery target time option for PITR.

What backup tool should I use for Kubernetes cluster disaster recovery?▼

Velero is the primary tool for Kubernetes DR, supporting persistent volume snapshots, namespace-scoped backups, and scheduled jobs. For control plane recovery, combine it with periodic etcd snapshots using etcdctl.

What is the difference between RTO and RPO in disaster recovery?▼

RTO is the maximum acceptable downtime before service must be restored, while RPO is the maximum acceptable data loss measured in time. Mission-critical Tier 0 systems typically require RTO under 1 hour and RPO under 5 minutes.

Does Velero support cross-region backup restore?▼

Yes, Velero supports restoring backups into clusters in different regions when the backup storage location is accessible. It also supports namespace remapping and storage class remapping during selective restores.

How do I test disaster recovery without risking production?▼

Run chaos engineering tests in staging using tools like Chaos Mesh or the included failover test scripts that stop the primary database and measure promotion time. Schedule monthly DR drills and restore backups to isolated staging environments for validation.

How long should backups be retained for GDPR or HIPAA compliance?▼

HIPAA requires 6 years of retention with encryption, while GDPR typically requires 1-7 years with EU data residency and right-to-erasure support. Implement retention with S3 or GCS lifecycle policies and immutable storage for ransomware protection.