A lightweight, Alpine linux based image for creating and managing scheduled MySQL backups. Runs a slightly modified AutoMySQLBackup utility.
This image uses AutoMySQLBackup 2.5 from Debian Linux source repository as a base, branched at 2.6+debian.4-1
tag.
Original source can be cloned from git://anonscm.debian.org/users/zigo/automysqlbackup.git
or taken at the
appropriate Debian package page.
Custom modifications:
- passed logging to stdout/stderr
- removed error logs mailing code
- made default configuration more suitable for docker container
Let's create a bridge network and start a MySQL container as an example.
docker network create dbtest
docker run --name some-mysql --network dbtest \
-e MYSQL_ROOT_PASSWORD=my-secret-pw -d mysql:latest
For the basic one-shot backup, you can run a container like this:
docker run --network dbtest \
-v '/var/lib/automysqlbackup:/backup' \
-e DBHOST=some-mysql \
-e DBNAMES=all \
-e USERNAME=root \
-e PASSWORD=my-secret-pw \
-e DBNAMES=all \
automysqlbackup
Container will create dumps of all datebases from MySQL inside /var/lib/automysqlbackup
directory and exit.
To run container in a scheduled mode, populate CRON_SCHEDULE
environment variable with a cron expression.
docker run --network dbtest \
-v '/var/lib/automysqlbackup:/backup' \
-e DBHOST=some-mysql \
-e DBNAMES=all \
-e USERNAME=root \
-e PASSWORD=my-secret-pw \
-e DBNAMES=all \
-e CRON_SCHEDULE="0 0 * * *" \
automysqlbackup
Instead of passing environment variables though docker, you can also mount a file with their declarations
as volume. See defaults
file in this image's git repository for the example.
docker run --network dbtest \
-v '/var/lib/automysqlbackup:/backup' \
-v '/etc/default/automysqlbackup:/etc/default/automysqlbackup:ro' \
automysqlbackup
For the example of using this image with docker-compose, see docker-compose.yml file in the image's repository.
Quick tips:
- You can call
automysqlbackup
binary directly for the manual backup:docker-compose exec mysqlbackup automysqlbackup
- Use only YAML dictionary for passing CRON_SCHEDULE environment variable
CRON_SCHEDULE: "0 0 * * *"
as YAML sequence- CRON_SCHEDULE="0 * * * *"
will preserve quotes breaking go-cron (Issue #1).
If set to cron expression, container will start a cron daemon for scheduled backups.
Username to access the MySQL server.
Password to access the MySQL server.
Host name (or IP address) of MySQL server.
Port of MySQL server.
List of space separated database names for Daily/Weekly Backup. Set to all
for all databases.
Default value: all
Backup directory location. Folders inside this one will be created (daily, weekly, etc.), and the subfolders will be database names.
Default value: /backup
List of space separated database names for Monthly Backups.
Will mirror DBNAMES if DBNAMES set to all
.
List of DBNAMES to exclude if DBNAMES are set to all (must be in " quotes).
Include CREATE DATABASE in backup?
Default value: yes
Separate backup directory and file for each DB? (yes or no).
Default value: yes
Which day do you want weekly backups? (1 to 7 where 1 is Monday).
Default value: 6
Choose Compression type. (gzip or bzip2)
Default value: gzip
Compress communications between backup server and MySQL server?
Default value: no
Additionally keep a copy of the most recent backup in a seperate directory.
Default value: no
The maximum size of the buffer for client/server communication. e.g. 16MB (maximum is 1GB)
For connections to localhost. Sometimes the Unix socket file must be specified.
Command to run before backups
Command run after backups
Backup of stored procedures and routines
Default value: yes
Similar to the original automysqlbackup script, all sources for this image are licensed under GPL-2.0.