BackupZit

Synology Active Backup alternative: BackupZit with your NAS as storage or source

Many small and mid-sized offices keep their backups on a NAS. This guide shows how BackupZit works with one: as the storage target for the backups of Windows and Linux machines, virtual machines, databases and Microsoft 365, and as a source whose shares are backed up themselves. It says what BackupZit does today, what it does not do, and how to test it next to the tool you use now.

What this guide covers

BackupZit is free and open source under the GNU AGPLv3, with no limits on machines, VMs or storage. It is self-hosted: you run the console on your own server, there is no cloud service and nothing has to be exposed to the internet. MaxZit, the company behind BackupZit, offers optional paid support. This guide does not compare prices or features of other products and does not describe any NAS software; it describes BackupZit only. Whether your NAS offers SMB, NFS or SSH/SFTP is in the NAS's own documentation.

Synology and Active Backup for Business are trademarks of their owner. BackupZit and MaxZit are not affiliated with, endorsed by or connected to Synology. The names are used here only because many people search for them.

At a glance

AreaIn BackupZitMain limits
NAS as storageSMB share, SFTP, or an NFS export mounted on the agent; each agent has its own repositoryNot immutable by itself; add an off-site or immutable copy
NAS as sourceSMB and NFS shares read by any agent, nothing installed on the NASNFS needs a Linux agent
Physical machinesWindows and Linux files, Windows disk images, Linux system backups, bare-metal restoreNo macOS agent
Virtual machinesProxmox VE, VMware ESXi and vCenter, Hyper-V, agentlessNo XCP-ng
DatabasesSQL Server, PostgreSQL, MySQL/MariaDB with point-in-time restoreOnly on the agent's own machine
Microsoft 365Exchange Online mail, calendars, contacts, OneDrive, SharePoint librariesNo restore into the mailbox yet; no Teams chats
ConsoleAppliance VM, appliance ISO, install script, packages or DockerRuns on Linux only; no app on the NAS

The NAS as a storage target

Under Storage targets a NAS can be added in three ways. The agents write the backups to it directly; each agent gets its own repository below the target's location, deduplicated, compressed with zstd and, with Encrypt backups (AES-256) on, encrypted before the data leaves the machine.

  • SMB share (Windows server, NAS): server, share, optional folder, user, password and, for domain accounts, the domain. The agents connect with these credentials themselves (SMB 2/3), so no drive has to be mapped and services running as SYSTEM work. The account must be allowed to create, read, delete and rename files. Agents and the console need TCP 445 to the NAS.
  • SFTP: sftp://user@host:22/path with a password or a private key and the server's host key fingerprint, which is pinned. Create a user that can only write into the backup folder.
  • NFS: mount the export on a Linux agent (for example in /etc/fstab) and add a Local / mounted path (on the agent machine) target such as /mnt/nfs-backup. For Windows machines an SMB target is the better choice.

When a target is added, Test connection writes a small file, reads it back and removes it, so a wrong password or host key shows at once. For SMB and SFTP (with OpenSSH's statvfs extension), Storage usage shows the size and free space of the NAS with a forecast of when it will be full, and Needs attention on the dashboard warns at 90 %. Keep the Recovery key apart from the NAS: with it and the storage credentials the backups can be restored even without the console.

Backing up the shares of the NAS

A NAS / file share job backs up a network share without installing anything on the NAS. Choose any agent that reaches the share — it reads the share and writes the backup to another target — and enter:

  • the share, smb://nas01/data (optionally with a folder) or nfs://nas01/volume1/data;
  • for SMB the account (user, optional domain, password, stored encrypted), empty for guest access; NFS uses the agent machine's access to the export;
  • the folders to back up (empty: the whole share) and exclusions such as #recycle, @eaDir or .snapshot.

For every run the agent connects the share — Windows agents over its UNC path (SMB only), Linux agents by mounting it read-only (with cifs-utils or nfs-common/nfs-utils) — and disconnects it afterwards. The backups are ordinary file backups: incremental and deduplicated, with retention, copy jobs, restore tests and browsing. Files go back onto the share, into a folder on any agent, or are downloaded in the browser. An agent that backs up several shares can run more than one job at a time (Jobs at once on the Agents page).

Windows and Linux machines

Agents run as a service on Windows 10, 11 and Server 2016 or newer (Windows 7 SP1, Server 2008 R2 SP1 and 2012 R2 through the legacy agent) and on 64-bit Debian, Ubuntu, AlmaLinux and Rocky Linux. They connect out to the console on TCP 8443, so no ports are opened on the clients, and they can be installed silently through GPO, Intune or an RMM tool, or from the console over WinRM or SSH.

  • Files and folders, from a VSS snapshot on Windows, also the folders of every user of a computer.
  • A Disk image of one, several or all disks of a Windows machine, with bare-metal restore from the recovery ISO, also onto different hardware or into a VM.
  • A Linux system backup of all local file systems and the disk layout, restorable onto an empty disk or as a new Proxmox VM.
  • One job can cover many computers (Several agents), each with its own history.

Not included: an agent for macOS; Linux system jobs do not support LUKS, software RAID (mdadm) or btrfs. Details in the guide for servers and PCs and the Windows bare-metal restore guide.

Virtual machines

Proxmox VE 7, 8 and 9, VMware ESXi 6.7, 7 and 8 with vCenter Server 7 and 8, and Hyper-V on Windows Server 2016 or newer are backed up without agents in the guests: by the agent on the Proxmox or Hyper-V host, or for ESXi by a proxy agent. After the first backup only changed blocks are read, and the VM backups can go to the NAS like any other job. Restores: whole VMs as a new VM or in place, single files, instant recovery on Proxmox VE and VMware. See the Proxmox VE, VMware ESXi and Hyper-V guides.

Databases and Microsoft 365

  • Databases: SQL Server, PostgreSQL and MySQL/MariaDB on the agent's machine, with log backups and restores to any point in time. See the database guide.
  • Microsoft 365: Exchange Online mail, calendars, contacts, OneDrive and SharePoint document libraries through Microsoft Graph with read-only permissions, run by any agent. Restores by browsing and downloading, or into a folder on an agent. See the Microsoft 365 guide.

Where the console runs

The console is a Linux server with PostgreSQL, usually a small VM (2 vCPU, 2–4 GB RAM, 20 GB disk). It does not store backup data and nothing is installed on the NAS. Ways to install it are on the download page: a ready-made VM image (OVA, qcow2, VHDX), the appliance ISO, the install script on Debian, Ubuntu, AlmaLinux or Rocky Linux, packages, or a Docker container on a Docker host with the compose plugin that you already run.

A second copy and ransomware protection

A NAS in the same building is one copy. SMB, SFTP and mounted disks have no immutability of their own, so a compromised account with write access could delete the backups. BackupZit adds:

  • Backup copy jobs that copy a job's backups from the NAS to a second target with their own retention, for example S3 or another site; only new data is sent.
  • Immutable targets: S3 with Object Lock in compliance mode, or the BackupZit Hardened repository on a Linux server of your own.
  • Rotating USB disks for offline copies, found by their volume label.
  • Detection of backups that look like ransomware or mass deletion, with an alert and paused retention.

The 3-2-1 guide shows a complete setup with a NAS, an immutable off-site copy and restore tests.

Status, alerts and restore tests

  • The dashboard counts the protected machines, VMs, databases and NAS shares; Needs attention lists failed jobs, missed schedules, offline agents and storage that is filling up.
  • Email, Slack, Microsoft Teams and webhook notifications; Reports as PDF and CSV, also emailed on a schedule.
  • Restore tests restore a random sample of the newest backups and verify it byte by byte; Check the stored data (monthly by default) reads everything in each repository, which finds a failing NAS disk or bit rot before you need the backup.

How to test it next to your current backup

  1. Leave your current backup as it is. Create a separate shared folder or SFTP user on the NAS for BackupZit, so the existing backups are never touched, and import the appliance as a small VM.
  2. Add the NAS as a storage target and check it with Test connection.
  3. Pick a few machines: a Windows server or PC with a disk image job, a Linux machine, a VM host or the Microsoft 365 tenant. Schedule the jobs at other times than the existing backups, so the NAS is not written by both at once.
  4. Back up a share of the NAS with a NAS / file share job to a second target.
  5. Restore, not just back up: single files in the browser, a folder back onto a share, a disk image into an empty VM from the recovery ISO. Turn on the automatic restore tests.
  6. Compare over a few weeks: each run page shows what was read, what was new and the compression ratio; Storage usage shows how fast the NAS fills.

BackupZit is a young project: the first public release was on 4 October 2026, and new versions come out often. Release candidates go to a separate testing update channel first.

Limits to know

  • BackupZit does not run as an app on the NAS; the console needs a Linux VM or server, the appliance or Docker.
  • SMB, SFTP and mounted NFS targets are not immutable; use S3 Object Lock or the hardened repository for that.
  • Deduplication works per agent, not between computers.
  • No macOS agent and no XCP-ng; Linux system jobs do not support LUKS, mdadm or btrfs.
  • Microsoft 365: no restore directly into mailboxes or OneDrive yet, no Teams chats.
  • The console and its guide come in 14 languages; paid support is provided in English only.

Next steps

Download BackupZit, see all storage targets, all features and the supported systems, or read the chapters Storage targets and Backup jobs & schedules in the user guide in the console. Related guides: 3-2-1 backup with immutable copies, free Acronis alternative for servers and PCs and open-source Veeam alternative. Questions are welcome in GitHub Discussions; companies can get commercial support from MaxZit (in English).

Synology and Active Backup for Business are trademarks of their owner. BackupZit and MaxZit are not affiliated with, endorsed by or connected to Synology.