IT Disaster Recovery Plan Generator

# IT Disaster Recovery Plan Generator

Safety Notice

This listing is from the official public ClawHub registry. Review SKILL.md and referenced scripts before running.

Copy this and send it to your AI assistant to learn

Install skill "IT Disaster Recovery Plan Generator" with this command: npx skills add 1kalin/afrexai-disaster-recovery

IT Disaster Recovery Plan Generator

Build production-ready disaster recovery plans that actually get followed when things break.

What This Does

Generates a complete DR plan covering infrastructure, data, applications, and communications. Output includes RTO/RPO targets, failover procedures, testing schedules, and cost modeling.

When to Use

  • Building DR documentation for compliance (SOC 2, ISO 27001, HIPAA)
  • After an outage exposed gaps in your recovery process
  • Onboarding a new infrastructure team
  • Annual DR plan review and update

How to Use

Tell the agent what you need. Be specific about your stack and requirements.

Quick Start

Generate a disaster recovery plan for our SaaS platform. Stack: AWS (us-east-1 primary, eu-west-1 secondary), PostgreSQL RDS, Redis, S3. RTO target: 4 hours. RPO target: 1 hour. Team size: 8 engineers.

Inputs to Provide

  • Infrastructure: Cloud provider, regions, key services
  • Data stores: Databases, object storage, message queues
  • RTO target: Maximum acceptable downtime
  • RPO target: Maximum acceptable data loss
  • Team size: Who's available during an incident
  • Compliance: Which frameworks apply (SOC 2, ISO 27001, HIPAA, PCI DSS)
  • Budget tier: Startup ($5K-$15K/yr) | Growth ($15K-$50K/yr) | Enterprise ($50K+/yr)

Output Structure

1. Risk Assessment Matrix

ThreatLikelihood (1-5)Impact (1-5)Risk ScoreMitigation
Region outage2510Multi-region active-active
Database corruption3515Point-in-time recovery + cross-region replicas
Ransomware3515Immutable backups + air-gapped copies
DNS failure248Multiple DNS providers
Key person unavailable4312Runbook documentation + cross-training

2. Recovery Tier Classification

Tier 1 — Critical (RTO < 1hr)

  • Authentication service
  • Payment processing
  • Core API

Tier 2 — Important (RTO < 4hr)

  • Admin dashboard
  • Reporting
  • Email delivery

Tier 3 — Standard (RTO < 24hr)

  • Analytics
  • Internal tools
  • Dev/staging environments

3. Failover Procedures

For each Tier 1 service, generate step-by-step runbooks:

  • Pre-failover health checks
  • DNS/load balancer switchover steps
  • Data consistency verification
  • Post-failover smoke tests
  • Rollback procedure if failover fails

4. Backup Strategy

Data StoreBackup FrequencyRetentionLocationRecovery Test Frequency
Primary DBContinuous (WAL)30 daysCross-regionMonthly
Object StorageCross-region replicationIndefiniteSecondary regionQuarterly
Config/SecretsOn change90 daysEncrypted S3 + localMonthly

5. Communication Plan

  • Internal escalation: PagerDuty/Opsgenie chain with backup contacts
  • Status page: Auto-update triggers at incident declaration
  • Customer notification: Templates for P1-P4 severity levels
  • Executive briefing: 15-min cadence during P1, hourly during P2

6. Testing Schedule

Test TypeFrequencyScopeDuration
Tabletop exerciseQuarterlyFull team walkthrough2 hours
Component failoverMonthlyIndividual service1 hour
Full DR simulationAnnuallyComplete failover4-8 hours
Backup restoreMonthlyRandom data store1 hour

7. Cost Model

Break down DR spending by category:

  • Infrastructure (standby capacity, cross-region replication)
  • Tooling (monitoring, alerting, backup software)
  • Testing (engineer hours, cloud costs during drills)
  • Training (onboarding, annual refreshers)

Benchmark: DR typically costs 15-25% of primary infrastructure spend. Companies without DR plans face average downtime costs of $5,600/minute.

Compliance Mapping

Map each DR control to framework requirements:

  • SOC 2 CC7.4/CC7.5: Incident response and recovery
  • ISO 27001 A.17: Information security continuity
  • HIPAA §164.308(a)(7): Contingency plan
  • PCI DSS 12.10: Incident response plan

Rules

  • Always include specific commands and CLI examples (not just "failover the database")
  • Include estimated time for each step in runbooks
  • Flag single points of failure explicitly
  • Default to the 3-2-1 backup rule: 3 copies, 2 media types, 1 offsite
  • Include cost estimates in USD for each recommendation
  • Never assume unlimited budget — tier recommendations by cost

Next Steps

Want to go deeper? Check out the full AI Context Packs — pre-built knowledge bases for SaaS, Healthcare, Legal, Manufacturing, and more. $47 per industry pack, or grab all 10 for $197.

Calculate what manual DR planning costs your team: AI Revenue Calculator

Set up your agent stack in 5 minutes: Agent Setup Wizard

Source Transparency

This detail page is rendered from real SKILL.md content. Trust labels are metadata-based hints, not a safety guarantee.

Related Skills

Related by shared tags or category signals.

General

Business Continuity Planner

Create detailed business continuity and disaster recovery plans by mapping critical functions, setting recovery objectives, assessing risks, and generating c...

Registry SourceRecently Updated
7530Profile unavailable
Automation

Project Trident

Four-tier persistent memory architecture for OpenClaw agents. Implements LCM-backed durability, hierarchical .md file organization, agentic signal routing, a...

Registry SourceRecently Updated
1491Profile unavailable
General

OpenClaw Recovery

跨平台自动备份与健康监控OpenClaw配置,崩溃时自动回滚并发送系统通知,确保服务持续稳定运行。

Registry SourceRecently Updated
600Profile unavailable
General

商业计划生成器

输入产品/业务描述,自动生成完整的商业计划书(执行摘要、市场分析、竞争定位、收入模型、运营计划、财务预测、风险评估)

Registry SourceRecently Updated
870Profile unavailable