backuplisted

# Backup — Backup & Disaster Recovery ## Activate When - User invokes `/godmode:backup` - User says "backup strategy," "disaster recovery," "what happens if we lose the database?" - User is designing data infrastructure that needs durability guarantees - After `/godmode:infra` provisions stateful services (databases, storage, queues) - Incident post-mortem reveals backup or recovery gaps - Compliance requirements mandate backup and recovery documentation ## Workflow ### Step 1: Inventory Data Assets Identify all data that needs protection: ``` DATA ASSET INVENTORY: | Asset | Type | Size | Growth | Critical | ``` ### Step 2: Define RPO/RTO Targets Set recovery objectives for each data tier: ``` RECOVERY OBJECTIVES: | Data Tier | RPO | RTO | Justification | ``` ### Step 3: Backup Strategy Design Design backup approach for each data tier: #### Tier 1: Continuous Protection ``` TIER 1 BACKUP STRATEGY: Primary database: ``` #### Tier 2: Periodic Snapshots ``` TIER 2 BACKUP STRATEGY: File uploads (S3/GCS): ``` #### Tier 3: Daily Backups ``` TIER 3 BACKUP STRATEGY: Application logs: ``` IF backup age >24h: trigger immediate backup. IF restore test fails: alert and re-run. ### Step 4: Backup Verification Automated checks that backups are actually working: ``` BACKUP VERIFICATION SCHEDULE: | Check | Frequency | Method | Alert | ``` ``` ### Step 5: Data Integrity Verification Verify backed-up data is consistent and usable: ``` DATA INTEGRITY CHECKS: | Check | Method | Fr