ZFS Buddy Backup

ZFS Buddy Backup is a Unraid plugin that simplifies ZFS snapshot replication to a backup buddy, whether another Unraid server or any OpenZFS platform such as…

  • Backup
  • Plugins
  • Tools & Utilities
ZFS Buddy Backup is a Unraid plugin that simplifies ZFS snapshot replication to a backup buddy, whether another Unraid server or any OpenZFS platform such as TrueNAS SCALE or Proxmox VE. It syncs raw encrypted snapshots so the target cannot read your data, and the remote SSH user is restricted to only the commands replication needs.

Platform availability

Available on 1 of 10 platforms

  • Unraid
  • TrueNAS (not listed)
  • Umbrel (not listed)
  • ZimaOS (not listed)
  • Proxmox (not listed)
  • Helm (not listed)
  • Mac (not listed)
  • Windows (not listed)
  • Linux (not listed)
  • Any server (not listed)

Health score?A 0-100 score computed nightly from four factors: maintained (40%: recent commits and steady activity), popular (25%: GitHub stars, log scale), easy to install (20%: platforms, install notes, setup guides, Docker image) and light to run (15%: minimum RAM, ARM support). When the source code has been checked, a fifth factor, security check (20%: automated scan for committed secrets, unsafe desktop-app settings, known-vulnerable dependencies and project hygiene; any serious finding caps it at 20), is added. Factors without data are left out and the rest are rescaled.

63/100 Good

Maintained
91last commit 27 days ago
Popular
2415 GitHub stars
Easy to install
251 install platform, install notes
Light to run
No data
Security check
95no serious findings, CI, tests

Based on 4 of 5 factors.

Availability: platform listings confirmed today, links checked 4 days ago

GitHub stars
15
Open issues
5
Last commit
2026-10-25
Latest release
2026.10.25
License
GPL-3.0
Activity
declining

Checked 5 days ago - source: GitHub (Piratkopia13/unraid-buddybackup)

Resources & Compatibility

Requirements not published yet.

First-install notes

  • Don't create a ZFS pool on used disks Before creating a ZFS pool (a storage area made from one or more disks), make sure the disks are not already in use for files, swap (temporary virtual memory), or another pool. If you force it, you can break your system or erase data that was already there. source
  • Use mirrors so one dead disk doesn't lose backups Create a mirrored pool (the same data written to two or more disks) for backups so it can keep working if one disk fails. Without that redundancy, a single dead disk can make the pool unavailable and interrupt backups. source
  • Set a quota on the backup dataset Set a quota (a space limit) on the ZFS dataset (a folder-like storage area) that holds backups using zfs set, then verify it with zfs get. Without a limit, one folder can fill the whole pool and stop backups or other work. source

Fetched 53 days ago - each note links to its source

Alternatives (2)

  • StableBit DrivePool - State of the art, file based drive pooling software.
  • zfs - Unraid plugin that enables the OpenZFS filesystem and volume manager on non-Array disks, so self-hosters on Unraid can build checksummed, s…

Checked 40 days ago - source: AlternativeTo

Common questions

What TrueNAS SCALE replication settings are needed to back into Unraid?

Create a Replication Task pointing to Unraid, set Snapshot Retention Policy to None, and keep Use Sudo For ZFS Commands disabled. Unraid's allowlist strictly denies destructive commands like zfs destroy.

What one-time command should I run on a generic OpenZFS host that will receive Unraid backups?

Run the plugin's one-time setup command as root on the remote host. It creates a restricted SSH user, a forced-command allowlist scoped to the dataset, minimal zfs allow delegations, and mountpoint=none for received datasets.

Can the remote backup host read the snapshots sent by the plugin?

No. The plugin syncs raw encrypted ZFS snapshots, the remote end does not get a shell, and the SSH user is limited to the replication commands.

Should I set a quota on the backup dataset?

Set a quota on the backup dataset with zfs set, then verify it with zfs get. This prevents one dataset from filling the pool and stopping backups.

Answers sourced from github.com, illumos.org

Community

Collected 48 days ago - public community threads