Implementing Backup Strategies
Overview
Design and implement backup strategies for databases, file systems, and cloud resources using tools like tar, rsync, pg_dump, mysqldump, AWS S3, and cloud-native snapshot APIs. Covers full, incremental, and differential backup schemes with retention policies, encryption, and automated verification.
Prerequisites
tar, rsync, or restic installed for file-level backups- Database client tools (
pg_dump, mysqldump, mongodump) for database backups
- AWS CLI configured with S3 write permissions (or equivalent GCP/Azure storage access)
- Sufficient storage capacity at backup destination (local, NFS, or object storage)
- Cron or systemd timer access for scheduling automated backups
- GPG or OpenSSL for backup encryption at rest
Instructions
- Inventory all data sources requiring backup: databases, application data directories, configuration files, secrets/certificates
- Classify data by RPO (Recovery Point Objective) and RTO (Recovery Time Objective) requirements
- Select backup strategy per data class: full daily + incremental hourly for databases, snapshot-based for block storage, rsync for file systems
- Generate backup scripts using appropriate tools (
pg_dump --format=custom, tar czf, rsync -avz --delete)
- Configure retention policy: daily backups kept 7 days, weekly kept 4 weeks, monthly kept 12 months
- Add encryption for backups containing sensitive data (
gpg --encrypt or S3 server-side encryption with KMS)
- Set up automated scheduling via cron jobs or systemd timers with proper logging
- Implement backup verification: restore to a test environment on a weekly schedule and validate data integrity
- Configure alerting for backup failures via email, Slack, or PagerDuty
Output
- Backup shell scripts with logging, error handling, and lock files to prevent concurrent runs
- Cron entries or systemd timer/service unit files
- Retention policy configuration (lifecycle rules for S3, cleanup scripts for local)
- Restore runbook with step-by-step recovery procedures
- Monitoring configuration for backup success/failure alerts
Error Handling
| Error |
Cause |
Solution |
No space left on device |
Backup destination full |
Verify retention cleanup is running; increase storage or reduce retention window |
pg_dump: connection refused |
Database not accepting connections or wrong credentials |
Check pg_hba.conf, verify connection string, and test with psql first |
rsync: connection unexpectedly closed |
Network interruption or SSH timeout |
Add --timeout=300 and --partial flags; use persistent SSH tunnel |
S3 upload failed: Access Denied |
IAM policy missing s3:PutObject permission |
Attach proper IAM policy; verify bucket policy allows writes from the backup source |
Backup file corrupted on restore |
Incomplete write or disk error during backup |
Add checksum verification (sha256sum) after backup; test restores regularly |
Examples
- "Create a backup strategy for a PostgreSQL database: full dump nightly to S3, WAL archiving for point-in-time recovery, 30-day retention."
- "Generate rsync scripts to mirror
/var/www to a remote NAS with incremental daily backups and weekly full backups."
- "Implement encrypted backups for a MongoDB replica set with automated restore testing every Sunday."
Resources
1---2name: implementing-backup-strategies3description: Execute use when you need to work with backup and recovery. This skill provides backup automation and disaster recovery with comprehensive guidance and automation. Trigger with phrases like "create backups", "automate backups", or "implement disaster recovery".4license: MIT5---6# Implementing Backup Strategies
7
8## Overview
9
10Design and implement backup strategies for databases, file systems, and cloud resources using tools like `tar`, `rsync`, `pg_dump`, `mysqldump`, AWS S3, and cloud-native snapshot APIs. Covers full, incremental, and differential backup schemes with retention policies, encryption, and automated verification.
11
12## Prerequisites
13
14- `tar`, `rsync`, or `restic` installed for file-level backups
15- Database client tools (`pg_dump`, `mysqldump`, `mongodump`) for database backups
16- AWS CLI configured with S3 write permissions (or equivalent GCP/Azure storage access)
17- Sufficient storage capacity at backup destination (local, NFS, or object storage)
18- Cron or systemd timer access for scheduling automated backups
19- GPG or OpenSSL for backup encryption at rest
20
21## Instructions
22
231. Inventory all data sources requiring backup: databases, application data directories, configuration files, secrets/certificates
242. Classify data by RPO (Recovery Point Objective) and RTO (Recovery Time Objective) requirements
253. Select backup strategy per data class: full daily + incremental hourly for databases, snapshot-based for block storage, rsync for file systems
264. Generate backup scripts using appropriate tools (`pg_dump --format=custom`, `tar czf`, `rsync -avz --delete`)
275. Configure retention policy: daily backups kept 7 days, weekly kept 4 weeks, monthly kept 12 months
286. Add encryption for backups containing sensitive data (`gpg --encrypt` or S3 server-side encryption with KMS)
297. Set up automated scheduling via cron jobs or systemd timers with proper logging
308. Implement backup verification: restore to a test environment on a weekly schedule and validate data integrity
319. Configure alerting for backup failures via email, Slack, or PagerDuty
32
33## Output
34
35- Backup shell scripts with logging, error handling, and lock files to prevent concurrent runs
36- Cron entries or systemd timer/service unit files
37- Retention policy configuration (lifecycle rules for S3, cleanup scripts for local)
38- Restore runbook with step-by-step recovery procedures
39- Monitoring configuration for backup success/failure alerts
40
41## Error Handling
42
43| Error | Cause | Solution |
44|-------|-------|---------|
45| `No space left on device` | Backup destination full | Verify retention cleanup is running; increase storage or reduce retention window |
46| `pg_dump: connection refused` | Database not accepting connections or wrong credentials | Check `pg_hba.conf`, verify connection string, and test with `psql` first |
47| `rsync: connection unexpectedly closed` | Network interruption or SSH timeout | Add `--timeout=300` and `--partial` flags; use persistent SSH tunnel |
48| `S3 upload failed: Access Denied` | IAM policy missing `s3:PutObject` permission | Attach proper IAM policy; verify bucket policy allows writes from the backup source |
49| `Backup file corrupted on restore` | Incomplete write or disk error during backup | Add checksum verification (`sha256sum`) after backup; test restores regularly |
50
51## Examples
52
53- "Create a backup strategy for a PostgreSQL database: full dump nightly to S3, WAL archiving for point-in-time recovery, 30-day retention."
54- "Generate rsync scripts to mirror `/var/www` to a remote NAS with incremental daily backups and weekly full backups."
55- "Implement encrypted backups for a MongoDB replica set with automated restore testing every Sunday."
56
57## Resources
58
59- PostgreSQL backup guide: https://www.postgresql.org/docs/current/backup.html
60- AWS S3 lifecycle policies: https://docs.aws.amazon.com/AmazonS3/latest/userguide/object-lifecycle-mgmt.html
61- Restic backup tool: https://restic.readthedocs.io/
62- Backup best practices (3-2-1 rule): https://www.veeam.com/blog/321-backup-rule.html
micsapp