ghorg VS docker-volume-backup

I'm using https://github.com/gabrie30/ghorg to do this. Why should I use your tool?

Where I currently work, there are 10 service per developer, actively running (if we're counting in the least charitable manner, maybe 4 per dev with most charitable counting). Our ratio is this huge due to large changes in company size over time. Consolidation is very helpful at this stage. If there's one thing I recommend to everyone who encounters this situation, you absolutely must keep a copy of all the source for all the repos on your computer, all at the same time, to make cross-repo grepping easy. For this purpose I recommend ghorg[0], but however you do it, it'll make everything easier.

[0] - https://github.com/gabrie30/ghorg

There is https://github.com/gabrie30/ghorg which I use to create a single tarball and than upload to S3 (separate script though).

I am interested in coming up with a backup plan before I get too invested in this setup. I found the docker-volume-backup project that looks like it might be a possible solution. However I'm not sure how to implement it using docker swarm since I am new to all of this. I would be interested in learning what backup solution you use for your docker swarm servers.

How do people usually backup their self-hosted docker services using postgres? I have been using docker-volume-backup [0] and just saving the postgres data directory, but I've found it requires a minute of downtime to backup properly.

[0] https://github.com/offen/docker-volume-backup

Offen: https://github.com/offen/docker-volume-backup

To solve points 1,2 i 3 I think it would be best to make the copy by stopping the container first. I've been looking for utilities and I've found some like offen/docker-volume-backup. Again, the disadvantage is that you have to configure everything (mount points, files, users, passwords...) manually for each container, so it is very easy to forget to create the backup of one of them. Also, the scheduling would not be centralised, so the backup wouldn't be run sequentially container after container. I've searched a lot, but I haven't found any good alternative. How are you dealing with the backup of containers?

Since I'm using docker rootless, I've run into issues using convenient solutions such as offen. These solutions don't work in a rootless context due to file permissions. The user in the offen container cannot read some directories owned by other containers. This is usually an issue with databases.

FYI this looks like the actively developed version of that utility: https://github.com/offen/docker-volume-backup

You should have backup OS and data but using a separate backup jobs. Backup OS drive using Timeshift or Veeam Agent. Backup Docker server's containers using Offen or Borg. OS backup would allow you restore operating system while data backup would allow recover files.

There is the image docker-volume-backup that allows you to make backup but depending on the situation (databases, ...) it is not necessarily the best solution