Dockhand 1.0.38 Backup & Restore: The Self-Hosted Community's Verdict

The Community Spark #

For years, the r/selfhosted community has debated the best way to handle Docker backups. The core problem? Docker’s native architecture treats data as ephemeral, leaving persistent data scattered across host bind mounts or external volumes.

Recently, a post titled “Dockhand 1.0.38 adds backup and restore for stack/containers (beta)” surged to the top of r/selfhosted. Users are electrified by the possibility of a native, built-in solution to snapshot running stacks and their underlying data states without relying on fragile cron scripts.

Synthesized Community Perspectives #

The consensus on r/selfhosted leans toward cautious optimism. Historically, self-hosters have duct-taped solutions together using bash scripts or tools like Duplicati. Dockhand 1.0.38 aims to centralize this workflow.

Where the Community Agreed #

Veteran sysadmins agree that Dockhand’s ability to snapshot both the container configuration (equivalent to a docker-compose export) and the attached volumes simultaneously is a massive time-saver. It eliminates the “configuration drift” problem where backed-up data no longer matches the container’s environment.

The Debates and Counter-Arguments #

However, seasoned users raised valid concerns. User feedback highlighted that beta backup tools often fail to handle large PostgreSQL or MariaDB databases safely. Simply copying hot database files from a bind mount can lead to corruption. The community consensus is clear: Dockhand needs pre-backup and post-backup hooks to flush database locks before snapshotting. Until that is fully implemented, users must rely on sidecar database dumpers.

Deep-Dive Actionable Guide: Implementing Dockhand Backups #

For r/selfhosted veterans and new homelabbers alike, here is a practical guide to configuring Dockhand 1.0.38 beta backup safely.

Step 1: Update Dockhand #

First, ensure you are running the latest beta channel. SSH into your Linux server and execute:

# Pull the latest beta image
docker pull dockhand/dockhand-server:1.0.38-beta

# Restart the Dockhand service
docker compose down && docker compose up -d

Step 2: Define a Stack Backup #

Navigate to your Dockhand UI or edit your stack configuration file. You can enable logical backups for specific stacks by modifying the dockhand.yml file:

backup_config:
  enabled: true
  target_stack: "media-server"
  destination: "/mnt/nas/backups/dockhand/"
  schedule: "0 2 * * *" # Runs daily at 2 AM
  include_volumes: true

Step 3: Safe Database Backups (Community Workaround) #

Because the beta lacks built-in database quiescing, self-hosters recommend adding a temporary dump container to your docker-compose.yml:

services:
  db:
    image: postgres:15
    volumes:
      - pgdata:/var/lib/postgresql/data
  db-dumper:
    image: prodrigestivill/postgres-backup-local:15
    restart: always
    volumes:
      - ./db_dumps:/backups
    environment:
      - POSTGRES_HOST=db
      - POSTGRES_DB=mydb
      - SCHEDULE=@daily

Dockhand will then cleanly back up the static configuration alongside the freshly dumped SQL files stored in ./db_dumps.

Pros & Cons: Dockhand Beta vs. Traditional Bash Scripts #

The Verdict / Expert Advice #

As an ecosystem, self-hosting has desperately needed a unified backup-and-restore mechanism. Dockhand 1.0.38 beta is a monumental step forward, but it is not yet a “set it and forget it” silver bullet.

• For Homelabbers & Enthusiasts: Deploy the beta immediately. The convenience of one-click stack restoration far outweighs the beta quirks for media servers and static apps.
• For Production / Critical Data Users: Wait for the stable release (or the addition of pre/post backup execution hooks). Continue using purpose-built database dumpers in parallel until Dockhand matures its snapshotting engine.

Frequently Asked Questions (FAQ) #

Is Dockhand 1.0.38 backup stable enough for production? No, it is currently in beta. While excellent for homelab static apps and media stacks, it lacks native database quiescing, making it risky for hot databases without manual workarounds.

Does Dockhand backup Docker volumes or just containers? Dockhand 1.0.38 backs up both the container configuration (compose equivalents) and the persistent volumes attached to the stack, ensuring a complete logical restore.

Can I restore a Dockhand backup to a different server? Yes. Because Dockhand captures the entire logical stack configuration and volume data, you can restore entirely on a new host by installing Dockhand and pointing it to the backup archive.