What this guide covers
BackupZit is free and open source under the GNU AGPLv3, with no limits on machines or storage. It is self-hosted: you run one console on your own server, the agents on the machines report to it, and the backups go to storage you choose. There is no cloud service and no hosted storage, 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; it describes BackupZit only.
- At a glance
- Agents for Windows and Linux
- File backups
- Windows disk images
- Linux system backups
- Bare-metal restore
- Restoring files
- Storage and ransomware protection
- Status, alerts and restore tests
- How to test it
- Limits
Acronis is a trademark of its owner. BackupZit and MaxZit are not affiliated with, endorsed by or connected to Acronis. The name is used here only because many people search for it.
At a glance
| Job | In BackupZit | Main limits |
|---|---|---|
| Agents | Windows 10, 11, Server 2016 or newer; Windows 7 SP1, Server 2008 R2 SP1 and 2012 R2 (legacy agent); 64-bit Debian, Ubuntu, AlmaLinux, Rocky Linux | No macOS agent |
| File backups | Incremental, from VSS on Windows, folders of every user, one job for many computers, NAS shares | — |
| Disk images | One, several or all disks of a Windows machine, used and changed blocks only | Windows (NTFS) only; Linux uses a Linux system job |
| Linux systems | All local file systems and the disk layout, restorable onto an empty disk or as a Proxmox VM | No LUKS, mdadm or btrfs; a whole-system restore recreates one disk |
| Bare-metal restore | Windows and Linux recovery ISOs, also onto different hardware or into a VM | Not between UEFI and legacy BIOS; the Windows ISO is built once with the Windows ADK |
| File restore | Browse and download in the console, into a folder or to the original location, also from disk images | Browsing needs network storage |
| Storage | SFTP, S3, SMB, Azure Blob, rotating USB disks, local disks, hardened repository; AES-256 encryption | No hosted cloud storage; immutability only on S3 Object Lock or the hardened repository |
Agents for Windows and Linux
An agent runs as a service on every protected machine, connects out to the console (no open ports on the clients) and writes the backups directly to the storage. Supported:
- Windows 10, 11 and Windows Server 2016 or newer (MSI), and Windows 7 SP1, Server 2008 R2 SP1 and 2012 R2 (legacy MSI) with the same features, including VSS and disk images;
- 64-bit Debian, Ubuntu, AlmaLinux and Rocky Linux (deb and rpm packages).
On Agents, Create enrollment token gives a code (BZ1-…) for any number of machines. Paste it into the Windows installer, install silently through GPO, Intune or an RMM tool (msiexec /i backupzit-agent.msi /qn ENROLLCODE="BZ1-..."), or let the console install the agent itself with Install on a machine from here — over WinRM on Windows and SSH on Linux. Agents update themselves from the console with signed packages and never during a running backup. Click an agent on the Agents page to give it a name and tags, such as a site; tags only help to find agents and do not give or limit access.
On Windows the agent shows an icon next to the clock with the backup state; users can start Back up now from it, while jobs, schedules and retention are set only in the console. There is no agent for macOS.
File backups
A Files and folders job backs up the paths you enter, incrementally; on Windows from a VSS snapshot, so open files such as Outlook PST files and databases are consistent. Useful options:
- For every user of the computer adds Desktop, Documents, Downloads, Pictures or the whole user profile of every user, also users added later and folders moved by OneDrive.
- Several agents (all agents, all Windows or Linux agents, or chosen ones) makes one job for many computers; agents that enroll later join it automatically. Each computer keeps its own history.
- Excludes by name pattern (
*.tmp,node_modules) or full path, and wildcards in paths. - Schedules (fixed times, every 15 minutes to 12 hours, monthly, after another job), a backup window, a speed limit for working hours, and retention by recent, daily, weekly and monthly backups.
- A NAS / file share job backs up an SMB or NFS share through any agent, without installing anything on the NAS.
Data is deduplicated across the backups and jobs of one agent on the same storage (not between computers), compressed with zstd and encrypted. A run with files that could not be read ends with a warning and lists them; the rest is backed up.
Windows disk images
A Disk image job captures a whole disk — partition table, boot partitions, Windows, programs and data — so a machine can come back exactly as it was. Choose All disks (every internal disk, also disks added later) or one disk, whole or only some partitions.
- The image is taken from a VSS snapshot while Windows runs; with All disks every volume of every disk comes from one snapshot, so the disks are consistent with each other.
- Only used blocks are read (NTFS allocation map), and blocks already in the repository are not uploaded again — the second image of a machine usually uploads only a few percent.
- GPT and MBR disks, UEFI and BIOS boot are supported. USB and SD disks, mounted VHD/VHDX files and removable media are left out of All disks.
- A weekly image plus daily file backups is a common combination.
Disk images are for Windows (NTFS volumes). Linux machines use a Linux system job instead.
Linux system backups
A Linux system job backs up every local file system (ext2/3/4, xfs, vfat, also on LVM) file by file with owners, permissions, ACLs and extended attributes, plus the disk layout: partition tables, LVM volume groups, file system UUIDs and the boot code. It does not copy the running disk block by block, because Linux has no built-in snapshot of a running disk; databases should be dumped first or backed up with a database job. Tested with Debian, Ubuntu 22.04 and Rocky Linux 9 (the same applies to AlmaLinux and RHEL 9); Ubuntu 22.04 and RHEL-like 9 systems need agent 0.50.0 or newer.
Not supported yet: encrypted disks (LUKS), software RAID (mdadm) and btrfs; the job reports these instead of writing an incomplete backup. Systems spread over several disks are backed up, but a whole-system restore recreates one disk.
Bare-metal restore
The machine to restore boots from a recovery ISO on a USB stick (or attached to a VM), connects to the console as a recovery agent, and you choose the backup to write onto its disk.
- Windows: because Windows PE may not be redistributed, the Windows recovery ISO is built once on any Windows PC with the free Windows ADK and
build-winpe.ps1from the release. On the image backup run choose Restore this image to a disk, the recovery agent and its disk. Restore to different hardware enables the built-in disk controller drivers, adds drivers with DISM (for example VirtIO for Proxmox) and rebuilds the boot files. - Linux: the Linux recovery ISO is published with every release and boots on BIOS and UEFI machines. Restore the whole system → Onto a disk recreates the layout and files; the target may be larger or smaller as long as the data fits. Or restore the system as a new Proxmox VM: it gets the CPU type x86-64-v2-AES, and a system with SELinux relabels its files once on the first boot.
- Physical to virtual: a Windows image restored into a Proxmox VE or Hyper-V VM, or a Linux system as a new Proxmox VM.
Limits: restoring between UEFI and legacy BIOS is not possible, a Windows image needs a target disk that reaches the end of the original's last partition and has the same sector size, and Windows activation may ask to be repeated on new hardware. Step by step: Windows bare-metal restore.
Restoring files
- On a backup run, Browse files shows the folders as they were; download one file, or several as a ZIP, straight in the browser.
- Restore files from this backup onto any agent — also a replacement PC — with Restore into a folder (nothing existing is touched) or Restore to original location, optionally only some paths. Each restored file can be verified against its checksum.
- Single files from a disk image without restoring the disk: browse the NTFS volumes of the image, then Download the ticked files or restore them to any agent.
- Without the console: any machine with the agent can restore from the storage with the recovery sheet and the recovery key.
Browsing in the console works for backups on network storage (SFTP, S3, SMB, Azure or a hardened repository); for a local or USB disk of an agent, restore by path.
Storage and ransomware protection
Storage targets: SFTP, S3-compatible storage (AWS, Wasabi, Backblaze B2, MinIO, Google Cloud Storage), SMB shares on a NAS, Azure Blob Storage, rotating USB disks (found by their volume label, whatever the drive letter), local disks and the BackupZit hardened repository on your own Linux server.
- Encrypt backups (AES-256) is on by default: data is encrypted on the machine before it leaves it. Keep the Recovery key away from the backups.
- Immutable copies with S3 Object Lock or the hardened repository; a Backup copy job keeps a second copy elsewhere, for example nightly to the NAS and copied to S3 or a USB disk.
- Backups that look like ransomware or mass deletion trigger an alert and pause the job's retention, so the last clean backups are kept.
Limits: you bring your own storage — MaxZit hosts none. SMB, SFTP and local disks are not immutable by themselves. The 3-2-1 guide shows a complete setup.
Status, alerts and restore tests
- The Dashboard lists under Needs attention failed jobs, missed RPOs, offline agents, computers without a backup job and storage that is almost full.
- Email, Slack, Microsoft Teams and webhook notifications; Reports as PDF and CSV, also emailed on a schedule.
- Automatic restore tests (weekly by default) restore a sample of files, or read random blocks of disk images, and verify them; a check of the stored data (monthly by default) reads everything in each repository.
- Roles (Administrator, Backup operator, Restore operator, Viewer), LDAP / Active Directory, SSO and two-factor sign-in.
How to test it next to your current tool
- Keep your current backups running. Import the BackupZit appliance as a small VM (OVA, qcow2 or VHDX) and give it its own storage target.
- Start with a few machines: a Windows server or PC with a disk image job and a file job, and a Linux machine with a Linux system job. Schedule them outside the times of your existing backups.
- Mind the overlaps. If you add a Databases job for SQL Server, its full backups without log backups are taken COPY_ONLY, so they do not disturb other backup plans; turn on log backups only where no other tool backs up the logs.
- Build and test the recovery media first: the Windows recovery ISO once with the Windows ADK, the Linux ISO from the release. Restore an image into an empty VM — the easiest way to prove that it boots.
- Restore files from a file backup and from an image, and turn on the automatic restore tests.
- Go through the limits below and the Not yet included parts of the user guide, and ask in GitHub Discussions if something is unclear.
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
- No agent for macOS.
- Disk images are for Windows (NTFS volumes, GPT and MBR disks); Linux system jobs do not support LUKS, mdadm or btrfs, and a whole-system restore recreates one disk.
- No restore between UEFI and legacy BIOS; the Windows recovery ISO has to be built once with the Windows ADK.
- No hosted storage or cloud console: you run the console (Linux, the appliance or Docker) and bring the storage.
- The console and its guide come in 14 languages; paid support is provided in English only.
BackupZit also backs up virtual machines (Proxmox VE, VMware, Hyper-V), databases and Microsoft 365 — see the overview for all areas.
Next steps
Download BackupZit, see the file backup and disk image features and the supported systems, or read the user guide in the console. Related guides: Windows bare-metal restore, 3-2-1 backup with immutable copies, open-source Veeam alternative and open-source NAKIVO alternative. Questions are welcome in GitHub Discussions; companies can get commercial support from MaxZit (in English).