Docker backup that focuses on the data containers cannot recreate

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.

Compare storage plans

The problem

The problem: knowing what actually needs a backup

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.

  • Images

    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.

  • Containers

    Running instances of images. Their writable layer is temporary and is lost when the container is removed.

  • Configuration

    docker-compose.yml files, .env files, secrets and reverse proxy settings that describe how everything fits together.

  • Persistent volumes

    Named volumes and bind mounts where databases, uploads and application state live. This is the data you cannot download again.

The consequence

The consequence: a host you cannot rebuild

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.

The solution

How Backnix approaches Docker backup

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.

  • Volume discovery

    Identify named volumes and bind mounts used by your containers.

  • Consistent database containers

    Dump MySQL, MariaDB or PostgreSQL containers with their native tools instead of copying live files.

  • Configuration included

    Keep Compose files and environment files next to the data they configure.

Docker backup flow: containers use persistent volumes, Backnix backs up the volumes and stores them in cloud storage.
Docker backup flow: Docker Containers → Persistent Volumes → Backnix Backup → Cloud Storage.

The diagram shows the designed architecture; availability is listed below.

Benefits

Benefits

  • Smaller backups

    Skip images and temporary layers; protect the data that matters.

  • Faster rebuilds

    Recreate the stack with the same configuration and restore the volumes.

  • Safe for running services

    Database-aware backups avoid corrupted copies of busy containers.

Technical considerations

Technical considerations

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.

Availability

Current status of these capabilities

  • Docker Backup

    Backup of Docker persistent volumes and Compose configuration.

    Coming soon
  • Automated Backup Scheduling

    Run backups automatically on a schedule.

    Coming soon
  • Encryption

    Client-side encryption before upload and TLS in transit.

    Coming soon

Status is updated as capabilities are released. See all features.

Related articles

Learn more

Docker backup FAQ

Should I back up Docker images?
Usually not. Keep Dockerfiles in version control and images in a registry. Back up images only if they cannot be rebuilt or pulled.
Can I back up a running container?
Stateless containers, yes. For databases inside containers, use a dump or stop the container to get a consistent copy.
Does it work with Kubernetes?
Backnix currently focuses on Docker and Docker Compose hosts. Kubernetes has different backup patterns and is not covered.

Ready to protect these systems?

Compare storage plans in USD or BRL. Yearly plans include 50% off the first annual payment.

Talk to us

Get in touch about your environment

Tell us what you need to protect. We will answer by email; nothing is charged.