Recommended container backup policy

• docker-db-backup

  10 707 9.1 Dockerfile

  Backup multiple database types on a scheduled basis with many customizable options

I have several dozen containers and I want to establish a good backup policy. Currently, all containers that store data do so by bind mounts to directories on a BTRFS volume. The files are backed up directly from the host. For MySQL/PostgreSQL containers I've been using the fantastic utility tiredofit/db-backup, which does a hot dump of all the data.

• docker-volume-backup

  30 1,500 9.0 Go

  Backup Docker volumes locally or to any S3, WebDAV, Azure Blob Storage, Dropbox or SSH compatible storage

  

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?

• InfluxDB

  www.influxdata.com sponsored

  Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.

  

Suggest a related project