This project provides Docker images to periodically back up a PostgreSQL database to a custom S3 service, and to restore from the backup as needed.
services:
postgres:
image: postgres:13
environment:
POSTGRES_USER: user
POSTGRES_PASSWORD: password
backup:
image: eeshugerman/postgres-backup-s3:15
environment:
SCHEDULE: '@weekly' # optional
BACKUP_KEEP_DAYS: 7 # optional
PASSPHRASE: passphrase # optional
S3_REGION: region
S3_ACCESS_KEY_ID: key
S3_SECRET_ACCESS_KEY: secret
S3_BUCKET: my-bucket
S3_PREFIX: backup
POSTGRES_HOST: postgres
POSTGRES_DATABASE: dbname
POSTGRES_USER: user
POSTGRES_PASSWORD: password
- Images are tagged by the major PostgreSQL version supported:
11
,12
,13
,14
, or15
. - The
SCHEDULE
variable determines backup frequency. See go-cron schedules documentation here. Omit to run the backup immediately and then exit. - If
PASSPHRASE
is provided, the backup will be encrypted using GPG. - Run
docker exec <container name> sh backup.sh
to trigger a backup ad-hoc. - If
BACKUP_KEEP_DAYS
is set, backups older than this many days will be deleted from S3. - Set
S3_ENDPOINT
if you're using a non-AWS S3-compatible storage provider.
WARNING: DATA LOSS! All database objects will be dropped and re-created.
docker exec <container name> sh restore.sh
NOTE: If your bucket has more than a 1000 files, the latest may not be restored -- only one S3
ls
command is used
docker exec <container name> sh restore.sh <timestamp>
ALPINE_VERSION
determines Postgres version compatibility. See build-and-push-images.yml
for the latest mapping.
DOCKER_BUILDKIT=1 docker build --build-arg ALPINE_VERSION=3.16 .
cp template.env .env
# fill out your secrets/params in .env
docker compose up -d
This project is a fork of @eeshugerman 's fork of @schickling 's original implementation. This fork has adaptations to run s3cmd instead of aws-cli to facilitate using other S3 providers than AWS.