docker-volume-backup VS restic

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

Restic - GitHub

I religiously use Google contacts. It's the simplest way to keep people contacts up to date on Android.

I archive all important documents in specific folders by subject and date. This is backed up to back blaze with restic. https://restic.net/

I use https://ente.io for pictures. I convinced my wife to use it, and she agreed to auto share her photos so I don't nag her for copies. It had simple import from Facebook and Google.

I also keep extensive journals, which really helps to tie it all together. I can basically grep for hangouts, conversations, etc.

I also separate work journal from personal, and have essentially a journal for each project. https://jodavaho.io/tags/bullet-journal.html for how.

I religiously use Google calendar for all plans, you can easily search it for past events to get dates.

I also use monicahq for some notes about things I should remember about people but the habit never stuck.

After Borg, I switched to Restic:

https://restic.net/

AFAIK, the only difference is that Restic doesn't require Restic installed on the remote server, so you can efficiently backup to things like S3 or FTP. Other than that, both are fantastic.

I'm curious, too. I know they've had some issues in the past:

https://github.com/restic/restic/issues/3268#issuecomment-78...

On the other hand, I tested around 15,000 backups last year (multiple hourly backups, daily tests) and they all passed.

I use and recommend restic. I use it for about 60 machines on my LAN, and it's absolutely fantastic.