backup-disaster-recovery▌
aj-geddes/useful-ai-prompts · updated Apr 8, 2026
Design and implement comprehensive backup and disaster recovery strategies to ensure data protection, business continuity, and rapid recovery from infrastructure failures.
Backup and Disaster Recovery
Table of Contents
Overview
Design and implement comprehensive backup and disaster recovery strategies to ensure data protection, business continuity, and rapid recovery from infrastructure failures.
When to Use
- Data protection and compliance
- Business continuity planning
- Disaster recovery planning
- Point-in-time recovery
- Cross-region failover
- Data migration
- Compliance and audit requirements
- Recovery time objective (RTO) optimization
Quick Start
Minimal working example:
# postgres-backup-cronjob.yaml
apiVersion: v1
kind: ConfigMap
metadata:
name: backup-script
namespace: databases
data:
backup.sh: |
#!/bin/bash
set -euo pipefail
BACKUP_DIR="/backups/postgresql"
RETENTION_DAYS=30
DB_HOST="${POSTGRES_HOST}"
DB_PORT="${POSTGRES_PORT:-5432}"
DB_USER="${POSTGRES_USER}"
DB_PASSWORD="${POSTGRES_PASSWORD}"
export PGPASSWORD="$DB_PASSWORD"
# Create backup directory
mkdir -p "$BACKUP_DIR"
# Full backup
BACKUP_FILE="$BACKUP_DIR/full-$(date +%Y%m%d-%H%M%S).sql"
// ... (see reference guides for full implementation)
Reference Guides
Detailed implementations in the references/ directory:
| Guide | Contents |
|---|---|
| Database Backup Configuration | Database Backup Configuration |
| Disaster Recovery Plan Template | Disaster Recovery Plan Template |
| Backup and Restore Script | Backup and Restore Script |
| Cross-Region Failover | Cross-Region Failover |
Best Practices
✅ DO
- Perform regular backup testing
- Use multiple backup locations
- Implement automated backups
- Document recovery procedures
- Test failover procedures regularly
- Monitor backup completion
- Use immutable backups
- Encrypt backups at rest and in transit
❌ DON'T
- Rely on a single backup location
- Ignore backup failures
- Store backups with production data
- Skip testing recovery procedures
- Over-compress backups beyond recovery speed needs
- Forget to verify backup integrity
- Store encryption keys with backups
- Assume backups are automatically working
Discussion
Product Hunt–style comments (not star reviews)- No comments yet — start the thread.
Ratings
4.6★★★★★40 reviews- ★★★★★Evelyn Taylor· Dec 16, 2024
backup-disaster-recovery reduced setup friction for our internal harness; good balance of opinion and flexibility.
- ★★★★★Henry Sethi· Dec 12, 2024
backup-disaster-recovery is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
- ★★★★★Diego Diallo· Nov 7, 2024
Registry listing for backup-disaster-recovery matched our evaluation — installs cleanly and behaves as described in the markdown.
- ★★★★★Mia Rao· Nov 3, 2024
Keeps context tight: backup-disaster-recovery is the kind of skill you can hand to a new teammate without a long onboarding doc.
- ★★★★★Hiroshi Yang· Oct 26, 2024
Useful defaults in backup-disaster-recovery — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
- ★★★★★Mia Kim· Oct 22, 2024
I recommend backup-disaster-recovery for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
- ★★★★★Oshnikdeep· Sep 9, 2024
backup-disaster-recovery reduced setup friction for our internal harness; good balance of opinion and flexibility.
- ★★★★★Valentina Sanchez· Sep 5, 2024
Registry listing for backup-disaster-recovery matched our evaluation — installs cleanly and behaves as described in the markdown.
- ★★★★★Hana Smith· Sep 5, 2024
backup-disaster-recovery fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
- ★★★★★Hiroshi Martin· Sep 5, 2024
I recommend backup-disaster-recovery for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
showing 1-10 of 40