Prompt #195

Docker Volume Backup with Restic

DevOps · ollama/qwen2.5-coder:7b

5/5

Variables: service, volumes, destination, rpo, rto, keep_daily, keep_weekly, keep_monthly, alert_channel
Tags: backup,restic,docker,sysadmin,disaster-recovery
Source: https://restic.readthedocs.io/en/latest/
Use count: 0
Created: 2026-05-01T18:34:49.745451+00:00
Updated: 2026-05-01T18:34:49.745451+00:00

Content

You are a backup infrastructure engineer. Design a Docker volume backup solution for: {{service}}

Volumes to back up: {{volumes}}
Backup destination: {{destination}} (S3 / Backblaze B2 / SFTP / local)
RPO (Recovery Point Objective): {{rpo}}
RTO (Recovery Time Objective): {{rto}}

Implement with restic:
1. restic init on the repository
2. Backup script: docker stop → restic backup → docker start (for consistency)
   OR use docker checkpoint (CRIU) for live backup if supported
3. Retention policy: keep last {{keep_daily}} daily, {{keep_weekly}} weekly, {{keep_monthly}} monthly
4. systemd timer or cron schedule matching RPO
5. Backup verification: restic check --read-data-subset=5%
6. Restore runbook: step-by-step to restore to a new host
7. Alerting: send failure notification to {{alert_channel}}
8. Encryption: restic uses AES-256-CTR + HMAC-SHA256 by default — key management plan

Output: backup.sh + systemd timer unit + restore runbook.