disaster-recovery-planner

Design disaster recovery strategies with tiered RTO/RPO targets and multi-region DNS failover.

7|2|Updated Nov 9, 2025
One-click install
npx skills add https://github.com/Prompt-or-Die-Labs/hyper-forge --skill disaster-recovery-planner-prompt-or-die-labs
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: disaster-recovery-planner
Source: https://github.com/Prompt-or-Die-Labs/hyper-forge/tree/main/.claude/skills/disaster-recovery-planner
Command: npx skills add https://github.com/Prompt-or-Die-Labs/hyper-forge --skill disaster-recovery-planner-prompt-or-die-labs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you design disaster recovery strategies so your systems can continue operating after outages, data loss events, or regional failures while meeting business continuity expectations.

Core Features & Use Cases

  • RTO/RPO Targeting: Assigns recovery time and data loss tolerances by service tier (e.g., critical auth/payment versus standard analytics) to drive the rest of your DR design.
  • Multi-Region Failover Design: Outlines DNS health-check and failover patterns to route traffic to a healthy region automatically.
  • Database Backup & Point-in-Time Recovery: Provides a backup workflow using full database dumps to object storage and WAL archiving for restore to a specific time.

Quick Start

Ask the AI to produce a DR plan for your production database and API using tiered RTO/RPO targets, automated backups to S3 with WAL archiving, and multi-region DNS failover for critical traffic.

Frequently Asked Questions about disaster-recovery-planner

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

FAQPage Schema
How do I design a disaster recovery plan with tiered RTO and RPO targets?

Disaster recovery planning with tiered RTO/RPO targets assigns recovery time and data loss tolerances by service tier, such as critical payment versus standard analytics, to drive your backup strategy and failover architecture design.

What is the best way to configure PostgreSQL WAL archiving for point-in-time recovery?

PostgreSQL WAL archiving for point-in-time recovery requires pairing full database dumps to object storage with continuous WAL archiving, enabling you to restore the database to a specific time during data loss events.

How does multi-region DNS failover work with Route53 health checks?

Multi-region DNS failover uses Route53 health checks to monitor regional availability, automatically routing traffic to a healthy region when failures occur, preserving service availability for critical systems.

Can I automate database backups to S3 while maintaining point-in-time recovery capabilities?

Automating database backups to S3 while maintaining point-in-time recovery involves scheduling full database dumps to object storage alongside continuous WAL archiving, ensuring both baseline snapshots and transaction logs are preserved.

When do I need multi-region failover architecture for my production database?

Multi-region failover architecture is needed when business continuity goals require high service availability during regional failures, utilizing DNS health-checked failover rules to route critical traffic automatically.