continuous-integration/drone/push Build is passing Details
|5 days ago|
|.drone.yml||2 years ago|
|.gitignore||2 years ago|
|Dockerfile||5 days ago|
|LICENSE||2 years ago|
|README.md||5 days ago|
|cleanup.go||2 years ago|
|client.go||2 years ago|
|config.go||5 days ago|
|dump.go||10 months ago|
|dump_mysql.go||5 months ago|
|dump_mysql_test.go||5 days ago|
|dump_postgres.go||10 months ago|
|dump_test.go||2 years ago|
|go.mod||1 year ago|
|go.sum||1 year ago|
|helper.go||2 years ago|
|main.go||5 days ago|
|save.go||2 years ago|
|store.go||2 years ago|
|webhook.go||5 days ago|
Zero-Fuss Docker Database Backup
A simple tool to create backup of all databases on a host. Supports postgres and mysql/mariadb.
Successor to this script.
Simply point it at your docker socket, mount a backup volume and be done:
docker run -v $PWD/backups:/backups -v /var/run/docker.sock:/var/run/docker.sock kolaente/db-backup
The tool will find all database containers running an official
postgres image and
create backups of them periodically. It will also discover new containers
as they are started and won't try to back up containers which have gone away.
When running, all backups for the current run are time-stamped into a sub folder of the backup directory (see below).
To make the backup tool discover other non-offical containers as well you can add the label
any container with a value of
postgres to treat it as a mysql or postgres container.
If you're running docker-compose, you can use a setup similar to the following compose file to run the backup:
version: '2' services: backup: image: kolaente/db-backup restart: unless-stopped volumes: - ./backups:/backups - /etc/localtime:/etc/localtime:ro - /var/run/docker.sock:/var/run/docker.sock
All config is done with environment variables.
Where all backup files will be stored.
The cron schedule at which the backup job runs, using the common unix cron syntax.
Check out crontab.dev for a nice explanation of the schedule.
0 */6 * * * (every 6 hours)
How many backups to keep. If more backups are stored in the backup folder, the oldest one will be removed until there are only as many as this config variable.
If provided, the tool will do an empty GET request to this URL to indicate it successfully completed the backup job. You can use this with other tools to monitor if backups are completed as they should.
Building from source
This project uses go modules, so you'll need at least go 1.11 to compile it.
go build .
to build the binary.