backup-and-disaster-recovery

# Backup and Disaster Recovery Plan for the worst case: the database is gone, the host is down for a week, the deploy was poisoned, ransomware encrypted everything. The skill is in advance preparation, not reaction. --- ## When to use - Setting up backups for a new system - Reviewing and validating backup architecture - Defining RPO (recovery point objective) and RTO (recovery time objective) - Running a disaster recovery drill - Diagnosing gaps after an incident - Planning for ransomware, data corruption, or insider threats - Migrating to a new platform (DR planning belongs in the migration plan) ## When NOT to use - Active incident response (use `incident-response`) - Routine deploy rollbacks (use `launch-runbook`) - Code or content versioning (covered by Git, CMS revision history) - Routine database snapshots (use this skill to set them up; routine review goes in monitoring) --- ## Required inputs - The systems in scope (databases, file storage, code, configs, secrets) - The hosting platforms and providers - Existing backup tooling and what it covers - Tolerance for data loss (in time) - Tolerance for downtime (in time) - Compliance requirements (some regulations mandate specific backup standards) --- ## The framework: 4 questions Every disaster recovery plan answers four questions explicitly. ### Question 1: What needs to be recoverable? List every system that holds state. Categorize by criticality. **Tier 1: must recover.** Without it, the business stops. ...