nomad4tech/backup-manager repository overview

⁠Backup Manager

A self-hosted web UI for scheduling and managing database backups in Docker environments.

Connect your Docker hosts, discover running databases automatically, and set up scheduled backups - without touching a config file.

Tech stack: Java 21 · Spring Boot 3 · H2 · React + TypeScript · shadcn/ui · Docker

⁠Demo

⁠

⁠Features

• 🐳 Docker-native - local socket or SSH tunnel to remote hosts
• 🔍 Auto-discovery - detects PostgreSQL/MySQL/MariaDB in running containers
• 🗓 Flexible scheduling - cron expressions or fixed-delay intervals (1h step)
• 🗂 Retention policy - keep the last N backups, old files deleted automatically
• 💾 Disk space pre-flight - checks free space before dump; fails fast if insufficient
• ☁️ S3 upload - optional upload to S3-compatible storage after each backup
• 📧 Email notifications - SMTP alerts on success and/or failure
• 🔁 Container resurrection - re-resolves container IDs by names after docker-compose down/up
• 💓 Heartbeat - periodic pings to UptimeRobot, Betterstack, etc.
• 📜 Backup history - full log with status, duration, and file size
• 🔐 Authentication - built-in login with session-based auth and remember me (30 days)
• 🗜 Compression - gzip compression per task, enabled by default
• ✏️ Task editing - edit schedule, compression, S3 upload, and retention directly from the task page

⁠Quick Start

# docker-compose.yml
services:
  backup-manager:
    image: nomad4tech/backup-manager:latest
    container_name: backup-manager
    ports:
      - "8080:8080"
    volumes:
      - /var/run/docker.sock:/var/run/docker.sock
      - ./data:/app/data       # settings & task config (required)
      - ./backups:/app/backups  # backup files (required)
    environment:
      - SPRING_PROFILES_ACTIVE=docker
    restart: unless-stopped

docker compose up -d

Open http://localhost:8080⁠ - the local Docker socket is detected automatically.

Default credentials: admin/admin - change them immediately in Settings -> Account.

⁠Remote Docker Hosts (SSH)

Go to Docker Sockets -> Add Socket, enter the host and SSH credentials. Backup Manager establishes an SSH tunnel and proxies the Docker socket transparently.

socat is managed automatically: if port 2375 is free on the remote host, Backup Manager starts socat via SSH and stops it on disconnect. If Docker is already exposed on that port by other means, no setup is needed. Install socat on the remote host only if Backup Manager needs to start it itself.

⁠How It Works

Backup Manager runs pg_dump/mysqldump inside the database container via Docker exec API. Output streams directly to disk - never buffered in memory, so large databases don't cause memory pressure.

No credentials are stored in config files. PostgreSQL uses $POSTGRES_USER, MySQL uses $MYSQL_ROOT_PASSWORD - both resolved inside the container at runtime.

⁠Supported Databases

⁠Environment Variables

⁠Known Limitations

• Early stage - actively developed and tested by a single maintainer; edge cases and environment-specific bugs may exist; feedback and bug reports are welcome
• No HTTPS - run behind a reverse proxy (Nginx + Let's Encrypt, Caddy, or Cloudflare Tunnel) in production; don't expose port 8080 directly to the internet
• No progress indicator - large backups show RUNNING until complete
• SSH transfers are slow - all dump data travels through the tunnel; schedule large remote backups off-peak
• Windows not tested - socket path is hardcoded to /var/run/docker.sock

⁠Roadmap

• Restore from backup via UI
• Progress indicator for running backups
• Notification webhooks
• Telegram notifications
• Slack notifications
• MongoDB support
• Backup encryption
• Setting import/export

⁠Links

• GitHub Repository⁠
• Report an Issue⁠

MIT License