| name | fairdb-backup-manager |
| description | Manage 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".
|
| allowed-tools | Read, Write, Edit, Grep, Glob, Bash(tar:*), Bash(rsync:*), Bash(aws:s3:*) |
| version | 1.26.0 |
| author | Jeremy Longshore <jeremy@intentsolutions.io> |
| license | MIT |
| tags | ["devops","backup","disaster-recovery"] |
| compatibility | Designed for Claude Code, also compatible with Codex and OpenClaw |
FairDB Backup Manager
Overview
Automate backup and recovery operations for FairDB database instances. Generate backup scripts, configure retention policies, schedule automated backups to local storage or S3, and produce tested restore procedures with integrity verification.
Prerequisites
- FairDB instance running and accessible with admin credentials
tar and rsync installed for file-level backups- AWS CLI configured with
s3:PutObject and s3:GetObject permissions (if using S3 as backup target)
- Sufficient storage at backup destination (2-3x database size for rotation)
- Cron or systemd timer access for scheduling
- Test environment available for restore verification
Instructions
- Assess the FairDB instance: identify data directory location, database size, and write throughput
- Select backup method: logical dump for portability, filesystem snapshot for speed, or continuous archiving for minimal RPO
- Generate backup script with lock acquisition, data export, compression (
tar czf), and checksum generation
- Configure S3 upload with server-side encryption (
aws s3 cp --sse aws:kms) for off-site copies
- Set up retention policy: keep hourly backups for 24 hours, daily for 7 days, weekly for 4 weeks, monthly for 12 months
- Create cleanup script to purge expired backups according to retention schedule
- Schedule backups via cron with proper logging to
/var/log/fairdb-backup.log
- Generate restore procedure: download from S3, verify checksum, decompress, and import with validation query
- Test restore procedure in a staging environment and document the time-to-recovery
Output
- Backup shell script with logging, locking, compression, and S3 upload
- Restore shell script with checksum verification and data validation
- Cron schedule entries or systemd timer units
- Retention cleanup script
- S3 lifecycle policy configuration for long-term archive tiering
Error Handling
| Error | Cause | Solution |
|---|
Backup lock acquisition failed | Another backup or maintenance process is running | Check for stale lock files; implement timeout-based lock with flock |
