I need to fully automate my backup/recovery process. I use restic as my primary backup/recovery tool and documented a process for Docker volume backup and restore with restic which I also use to backup Docker local volumes (unfortuantely requires small amounts of downtime per service) – There is also this nice tool called auto-restic which I haven’t gotten around to using yet, which I thinik will help with automating. Right now I still kick the process of by-hand, whenever I feel I should probably do another backup 🤦‍♂️

One of my main problems/blockers I think is that I use my Mac Studio as my primary backup target (from my NAS and Docker volumes), then I use Backblaze B2 as my secondary target from there. So my backup process is 2-step with two targets (a local target and a remote target). What I really need is another secondary smaller NAS that I can just host the tools on more permanently, hmmm.

Woohoo 🥳 Finally fixed the remaining bugs in my set of shell scripts for backing up Docker volumes:

https://git.mills.io/prologic/backup-docker-volumes

Has the behavior of:

• Given a Docker node;
  
• Find all active volumes.
  
• For each volume, find its running container or service,
  
• Stop the Container or scale down the Service.
  
• Run the backup on the volume
  
• Restart the Container or scale up the Service.