Skip to content
ProHomeLab
RU

Backup

Zerobyte - Backup Automation for Self-Hosted Infrastructure

Stilicho2011Updated 12 min read25 views

Also available in: RU

Zerobyte - Backup Automation for Self-Hosted Infrastructure
Part 2 of 4 in the series Backup
  1. Duplicati - Encrypted Backups for Your Home Server
  2. Zerobyte - Backup Automation for Self-Hosted Infrastructure
  3. Proxmox Backup Server 4.2.0 - Installation, Configuration, and Proxmox VE Backup
  4. Vinchin Backup & Recovery V9.0 SP3 - Overview and Hands-On with Proxmox VE
Contents
Tip

If you enjoyed this article, you can become a sponsor on Boosty.

Zerobyte - backup automation for Homelab

Backups are one of the key responsibilities of any infrastructure.
In a homelab or self-hosted environment, it's important to have a system that:

  • runs backups automatically
  • supports encryption
  • can work with cloud storage
  • has a convenient management interface

That's exactly the job Zerobyte does.

In this article, we'll cover:

  • what Zerobyte is
  • how to install it via Docker
  • how to configure your first backup
  • how to restore data

What is Zerobyte

Zerobyte is a backup automation tool that helps store data across various storage backends. Built on top of Restic, it provides a modern web interface for scheduling, managing, and monitoring encrypted backups of your remote storage.

Project site and docs: zerobyte.app
Source code: github.com/nicotsx/zerobyte

Warning

Zerobyte is still at version 0.x.x and can change significantly from version to version. The project is under active development.

After I released a video about the best new apps of 2025, where I talked about Zerobyte among others, I got a lot of messages asking why I didn't cover one solution or another. According to whoever's asking, the app they personally use is always the best one out there :) Below, I've tried to put together a table comparing the features of the most popular solutions.

Zerobyte's features:

  • Automatic backup with encryption, compression, and retention policies, implemented via Restic
  • Flexible scheduling for automatic backup jobs, with fine-grained retention policy tuning
  • End-to-end encryption, protecting data at every stage
  • Support for multiple protocols: backups from NFS, SMB, WebDAV, SFTP, or local directories

This makes Zerobyte a convenient alternative to solutions like:

If you're running a Proxmox setup, Proxmox Backup Server is also worth a look, since it's built specifically for that ecosystem.


Backup tool Web UI Encryption Deduplication Docker
Duplicati ✔ ✔ ✔ ✔
Kopia ✔ ✔ ✔ ✔
BorgBackup ✖ ✔ ✔ ✔
Zerobyte ✔ ✔ ✔ ✔

Duplicati vs Zerobyte - comparing backup systems

Since in the previous article I talked about Duplicati, let's take a closer look and compare Duplicati with today's subject.

Duplicati and Zerobyte are backup solutions aimed at self-hosted infrastructure and home labs. Both tools offer a web interface, automation, and support for remote storage, but they take different architectural approaches.

Duplicati is a self-contained backup system with its own engine.

Zerobyte is a web interface and backup job manager built on top of the restic backup engine.


Quick comparison table

Criteria Duplicati Zerobyte
Solution type Self-contained backup system Backup manager
Backup engine Own Restic
Architecture Monolithic application Web UI + restic backend
Interface Web UI + CLI Web UI (repos can be opened with restic CLI)
Encryption AES-256 Restic's built-in encryption
Deduplication Block-level deduplication Restic's deduplication
Incremental backups Yes Yes
Compression Yes Yes
File versioning Yes Yes
File restore Yes Yes
Task scheduler Yes Yes
Cloud storage support Yes Via restic or rclone
Local storage Yes Yes
S3 support Yes Yes
WebDAV support Yes As a source; as storage via rclone
SFTP support Yes Yes
rclone support Yes (rclone binary required) Yes
Multiple job management Yes Yes
Snapshot control Yes Yes
Logging and monitoring Yes Yes
Open source Yes Yes
Project maturity High New project
Ease of installation Very simple Simple
Configuration flexibility Medium High

Solution architecture

Duplicati

Duplicati is a fully self-contained backup system.
The app includes:

  • a backup engine
  • a web interface
  • a scheduling system
  • cloud storage support
  • a deduplication mechanism
  • encryption

Thanks to this, Duplicati can be installed as a single app and used right away to create backups.


Zerobyte

Zerobyte works differently. It's a management interface for restic, a popular backup engine.

Zerobyte adds:

  • a web management panel
  • backup job creation
  • schedule management
  • snapshot browsing
  • file restore
  • centralized management of multiple repositories

Essentially, Zerobyte acts as a management panel for restic-based infrastructure. And that comes with a nice bonus: the repositories it creates are plain restic repositories. If something happens to Zerobyte itself, you can still get your data out with regular restic from the command line (more on that in the restore section below).


Supported storage

Duplicati

Duplicati supports a large number of cloud services:

  • Amazon S3
  • Backblaze B2
  • Google Drive
  • OneDrive
  • Dropbox
  • WebDAV
  • SFTP
  • rclone (requires the rclone binary)
  • local disks
  • NAS

Zerobyte

Zerobyte has two separate concepts, each with its own list.

Sources (Volumes) - where the data comes from:

  • local directories (mounted into the container)
  • NFS
  • SMB
  • WebDAV
  • SFTP
  • rclone

Repositories - where the backups go:

  • local directories
  • S3-compatible storage (Amazon S3, MinIO, Wasabi, etc.) and Cloudflare R2
  • Google Cloud Storage
  • Azure Blob Storage
  • REST Server (restic)
  • SFTP
  • rclone - and through it, 40+ more cloud providers, including Google Drive, Dropbox, and OneDrive

So when it comes to storage, the two tools end up roughly even: both can work through rclone, it's just that in Zerobyte it's a built-in repository type right in the UI.


Main advantages

Advantages of Duplicati

  • very simple installation
  • a ready-made backup system
  • supports the most common cloud storage providers
  • a mature, well-known project
  • a convenient web interface

Duplicati is a great fit for:

  • home servers
  • NAS
  • personal backups
  • small homelab infrastructures

Advantages of Zerobyte

  • modern architecture
  • built on the reliable restic backup engine
  • rclone storage support
  • flexible repository handling
  • convenient snapshot management
  • backups are stored in the standard restic format and aren't tied to Zerobyte itself

Zerobyte is better suited for:

  • advanced homelabs
  • infrastructures with multiple backup jobs
  • restic users

When to choose Duplicati

Choose Duplicati if:

  • you need a simple backup system
  • fast setup matters
  • you need support for popular cloud services
  • your infrastructure is small

Duplicati is a good choice for most home servers.


When to choose Zerobyte

Choose Zerobyte if:

  • you already use restic
  • you need a more flexible backup system architecture
  • you want backups you can open without the app itself - with plain restic
  • you have multiple backup repositories

Duplicati vs Zerobyte comparison summary

Tool Best suited for
Duplicati Simple, fast backups for a home server
Zerobyte Managing restic-based backups and more flexible infrastructures

Both tools are open source and can be used in a self-hosted environment. The choice comes down to whether you want a ready-made backup client (Duplicati) or a restic-based backup infrastructure manager (Zerobyte).

Main features of the Zerobyte web interface

Web interface

Zerobyte offers a modern web management panel, through which you can:

  • create backup jobs
  • run backups manually
  • track status
  • restore files

Using Restic

Under the hood, Zerobyte uses Restic, which gives you:

  • deduplication
  • encryption
  • incremental backups
  • support for many storage backends

Docker Compose file from the video

yaml
services: # Declaration of all services (containers) managed by Docker Compose
zerobyte: # Service name (logical container name)
image: ghcr.io/nicotsx/zerobyte:latest # Container image. For a 0.x project it's safer to pin a version (e.g. :v0.43) instead of latest
container_name: zerobyte # Explicit container name for convenience (docker ps, logs, etc.)
restart: unless-stopped # Automatically restart the container on crash (except manual stop)
cap_add:
- SYS_ADMIN # Adds extended privileges (needed for FUSE and working with remote shares). If backing up local data, comment out this line
- SYS_PTRACE # Allows tracing processes. Not present in the current official example
#ports:
# - "4096:4096" # Publish the port externally (not needed if using Traefik)
devices:
- /dev/fuse:/dev/fuse # Pass through the FUSE device for rclone/mounting. If backing up local data, comment out this line
environment: # Environment variables for configuring the app
- TZ=Europe/Moscow # Container timezone (important for schedules and logs)
- BASE_URL=https://zerobyte.stilicho.ru # The URL you use to open Zerobyte (https:// enables secure cookies)
- APP_SECRET=<generate_with_openssl_rand_-hex_32> # Secret used to encrypt sensitive data in the database (32+ chars, must be your own)
security_opt: # Relaxing container security mechanisms
- seccomp:unconfined # Disables the seccomp profile (allows more system calls). Not present in the current official example
- apparmor:unconfined # Disables the AppArmor profile (removes access restrictions). Not present in the current official example
volumes: # Mounting directories (data and file access)
- /etc/localtime:/etc/localtime:ro # Sync time with the host (read-only)
- /home/stilicho/docker/zerobyte:/var/lib/zerobyte # Zerobyte data (config, database, state)
- /home/stilicho/docker:/mydata # Directory with data to back up (source for volumes)
networks:
proxy: # Connect to the proxy network (for use with Traefik)
labels: # Labels for automatic Traefik configuration
- "traefik.enable=true" # Enable Traefik handling for this container
- "traefik.http.routers.zerobyte.entrypoints=web" # HTTP entrypoint (port 80)
- "traefik.http.routers.zerobyte.rule=Host(`zerobyte.stilicho.ru`)" # Routing by domain
- "traefik.http.middlewares.zerobyte-https-redirect.redirectscheme.scheme=https" # Redirect HTTP → HTTPS
- "traefik.http.routers.zerobyte.middlewares=zerobyte-https-redirect" # Apply the redirect
- "traefik.http.routers.zerobyte-secure.entrypoints=websecure" # HTTPS entrypoint (port 443)
- "traefik.http.routers.zerobyte-secure.rule=Host(`zerobyte.stilicho.ru`)" # HTTPS routing rule
- "traefik.http.routers.zerobyte-secure.tls=true" # Enable TLS (HTTPS)
- "traefik.http.routers.zerobyte-secure.tls.certresolver=cloudflare" # Issue the certificate via Cloudflare
- "traefik.http.routers.zerobyte-secure.service=zerobyte" # Bind to the service
- "traefik.http.services.zerobyte.loadbalancer.server.port=4096" # Internal app port inside the container
- "traefik.docker.network=proxy" # Specify the network for Traefik
networks: # Declaration of networks
proxy: # Network name
external: true # Network already exists (Docker Compose won't create it)
Warning

The cap_add and devices sections grant excessive privileges. Only use them if you understand the possible consequences. For example, in my case, without these parameters I wasn't able to connect to an SMB share on TrueNAS.

A few important points about this file (checked against the official docs):

  • APP_SECRET encrypts the secrets Zerobyte stores in its database - storage credentials, passwords, and so on. It needs to be a random string of 32+ characters; openssl rand -hex 32 will do. Don't copy the value from someone else's example, and keep it in .env rather than directly in the compose file.
  • Container privileges. In the current official example, working with remote shares only needs cap_add: SYS_ADMIN and /dev/fuse. SYS_PTRACE and disabling seccomp/AppArmor aren't used there - if everything mounts fine without them, drop them. And if you only back up local folders, you can drop SYS_ADMIN and /dev/fuse as well: the docs describe that simplified setup separately.
  • Don't back Zerobyte up with itself. In this example, the whole /home/stilicho/docker folder is mounted as /mydata, and it also contains /home/stilicho/docker/zerobyte - Zerobyte's own database and local repositories (/var/lib/zerobyte/repositories). If you select all of /mydata, the backup will start copying itself. Exclude the zerobyte folder or pick specific subfolders in the job.
  • /var/lib/zerobyte must live on a local disk. The docs explicitly warn against pointing it at a network share - you'll run into permission issues and a serious performance hit.
  • Don't expose Zerobyte to the internet. The project's authors strongly advise against making it reachable from outside. Traefik is here for HTTPS and subdomain access inside your own network, not for publishing it to the world.

Working with the app

The app is fairly lightweight - the image downloads quickly and spins up just as fast. After that, we go to the subdomain we assigned to our app, in my case zerobyte.stilicho.ru.

We're greeted by an initial registration screen, where we need to set an admin login and password, provide an email address, and download a recovery key for restoring from a backup (in case that's ever needed).

Initial registration screen

Zerobyte admin registration screen

Screen for entering registration details and the option to download the recovery key

Recovery key download screen with password confirmation

Important

The recovery key is a restic.pass file - the restic password that encrypts every repository created in Zerobyte. Without it, your encrypted backups can't be opened. Keep it off the server you're backing up, for example in a password manager like Vaultwarden. Otherwise the key to the safe ends up locked inside the safe.

We're greeted by a pleasant retro interface (angular, like my Mercedes W124) in red and black tones. If you're a Sith and also a fan of retro design, you'll love this interface.

Zerobyte main screen: the Volumes section, still empty

Since there's a link to my video review at the beginning of the article, if you don't mind I'll keep the rest of this description brief.

As I explained in the video, the user needs to configure the source location for backups and the destination resource where the backups will be sent.

So the Volumes section is "what we're going to back up and where the files are located."

Creating a volume with a backend choice: Directory, NFS, SMB, WebDAV, SFTP, rclone

The Repositories section handles configuring the destination resource where we back everything up to.

Creating a repository with a backend choice: Local, S3, Cloudflare R2, Google Cloud Storage, Azure Blob Storage, REST Server, SFTP, rclone

The Backups section lets us fine-tune the backup jobs, including, but not limited to: when and at what time to start the backup process, how many copies to keep, and so on.

Creating a backup job: name, repository, frequency, execution time, backup paths

In the Notifications section, we configure how and through what channel we want to receive notifications.

Creating a notification destination with a type choice: Email, Slack, Discord, Gotify, Ntfy, Pushover, Telegram, Webhook, Shoutrrr

And down at the bottom, the administration settings.

Settings → Account section: user profile, password change, recovery key


Restoring data

A backup you've never tried restoring from isn't a backup - it's a hope. So here's a quick look at how to get your data back.

Restoring through the UI

Restores start from the Backups section:

  1. Open the job that holds the data you need.
  2. Pick the snapshot from the date you want.
  3. In the file browser, select the files or folders you need. If you don't select anything, the whole snapshot you're viewing gets restored.
  4. Choose where to restore: Original location or Custom location (a different folder).
  5. Decide what to do with files that already exist, and click Restore.

Besides restoring to the server, there's a Download button that pulls the selected file or folder straight into your browser. Handy when you just need to grab a file or two onto your own machine.

For Docker services, it's safer to restore not on top of the live files but into a separate folder (Custom location), check what's there, and only then move what you need. Zerobyte's own docs recommend the same. And if you do restore to the original location, stop the container whose files you're bringing back first, and make sure the folder is mounted into Zerobyte without :ro: you can back up from a read-only folder, but you can't restore into one.

If Zerobyte itself is gone

This is where being a layer on top of restic really pays off. Zerobyte's repositories are plain restic repositories, so if the Zerobyte server dies, you can get your data out with the standard restic tool from any machine. All you need is access to the storage and the recovery key (restic.pass):

Terminal window
# list the snapshots in the repository
restic -r /path/to/repository --password-file restic.pass snapshots
# restore the latest snapshot into a separate folder
restic -r /path/to/repository --password-file restic.pass restore latest --target /tmp/restore

For S3, SFTP, and other storage, use the repository address in restic's format (e.g. s3:... or sftp:...) instead of a local path, along with the matching credentials.

Testing your backups

Every now and then, do a test restore: grab a couple of folders, restore them to a separate location, and make sure what's inside is what you expect. It takes a couple of minutes and will one day save you a whole lot of nerves.