Automated backup infrastructure across multiple sites. A scheduler triggers periodic backups, the primary backup agent compresses and archives data, a secondary site syncs copies for disaster recovery, and a tester periodically restores and verifies backup integrity.
clawhub install pilot-backup-disaster-recovery-setup # Replace <your-prefix> with a unique name for your deployment (e.g. acme)
# On scheduler node
clawhub install pilot-cron pilot-task-chain pilot-audit-log pilot-slack-bridge
pilotctl set-hostname <your-prefix>-backup-sched
# On primary backup server
clawhub install pilot-backup pilot-archive pilot-compress pilot-share
pilotctl set-hostname <your-prefix>-backup-primary
# On offsite secondary (different region/datacenter)
clawhub install pilot-sync pilot-verify pilot-health pilot-share
pilotctl set-hostname <your-prefix>-backup-secondary
# On restore test server
clawhub install pilot-backup pilot-verify pilot-health pilot-alert
pilotctl set-hostname <your-prefix>-restore-tester
# scheduler <-> primary
# On backup-sched:
pilotctl handshake <your-prefix>-backup-primary "backup dr"
# On backup-primary:
pilotctl handshake <your-prefix>-backup-sched "backup dr"
# primary <-> secondary
# On backup-primary:
pilotctl handshake <your-prefix>-backup-secondary "backup dr"
# On backup-secondary:
pilotctl handshake <your-prefix>-backup-primary "backup dr"
# secondary <-> tester
# On backup-secondary:
pilotctl handshake <your-prefix>-restore-tester "backup dr"
# On restore-tester:
pilotctl handshake <your-prefix>-backup-secondary "backup dr"
# tester <-> scheduler
# On restore-tester:
pilotctl handshake <your-prefix>-backup-sched "backup dr"
# On backup-sched:
pilotctl handshake <your-prefix>-restore-tester "backup dr"
# scheduler <-> secondary
# On backup-sched:
pilotctl handshake <your-prefix>-backup-secondary "backup dr"
# On backup-secondary:
pilotctl handshake <your-prefix>-backup-sched "backup dr"
pilotctl trust