Docker Backup
Offen Docker Volume Backup: Setup, S3 and Restore Guide
Set up offen/docker-volume-backup with Docker Compose: schedule, retention, S3 upload, GPG encryption, stopping containers, database dumps and restores.
Containers are designed to be disposable. The data they write is not. Backnix is designed to back up the persistent volumes and configuration that make a Docker host recoverable.
A Docker host mixes four very different things. Confusing them leads to backing up gigabytes of images that can be downloaded again while the one volume holding the production database is forgotten.
Read-only templates pulled from a registry or built from a Dockerfile. They can be recreated, as long as the Dockerfile and registry still exist.
Running instances of images. Their writable layer is temporary and is lost when the container is removed.
docker-compose.yml files, .env files, secrets and reverse proxy settings that describe how everything fits together.
Named volumes and bind mounts where databases, uploads and application state live. This is the data you cannot download again.
When a Docker host fails without a volume backup, the containers come back empty. When the volumes are saved but the Compose files and environment variables are not, nobody remembers which image versions, ports and settings were in use. Both situations turn a quick rebuild into days of guesswork.
Backnix is designed to discover volumes and Compose projects on the host, back up volume data and configuration files, and use database-aware dumps for database containers so their data is consistent.
Identify named volumes and bind mounts used by your containers.
Dump MySQL, MariaDB or PostgreSQL containers with their native tools instead of copying live files.
Keep Compose files and environment files next to the data they configure.
The diagram shows the designed architecture; availability is listed below.
Skip images and temporary layers; protect the data that matters.
Recreate the stack with the same configuration and restore the volumes.
Database-aware backups avoid corrupted copies of busy containers.
Copying a volume while a database writes to it can produce an unusable copy; either dump the database or stop the container briefly. Named volumes live under Docker's data directory (usually /var/lib/docker/volumes), while bind mounts can be anywhere on the host. Secrets in .env files should be encrypted in backups, which client-side encryption handles. Keep image tags pinned so a restore uses the same versions.
Backup of Docker persistent volumes and Compose configuration.
Run backups automatically on a schedule.
Client-side encryption before upload and TLS in transit.
Status is updated as capabilities are released. See all features.
Docker Backup
Set up offen/docker-volume-backup with Docker Compose: schedule, retention, S3 upload, GPG encryption, stopping containers, database dumps and restores.
Docker Backup
Back up PostgreSQL running in Docker Compose with pg_dump: consistent dumps, roles, an automated script with checks, cron, offsite copies and restore tests.
Docker Backup
Restore a PostgreSQL dump in Docker Compose: identify the format, recreate the database, use pg_restore or psql, initdb scripts and fix common errors.
Compare storage plans in USD or BRL. Yearly plans include 50% off the first annual payment.
Tell us what you need to protect. We will answer by email; nothing is charged.