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, an agent on every machine reports to it, and the images go to storage you choose. 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; it describes BackupZit only. File backups and the wider picture for physical machines are in the guide for servers and PCs.
- At a glance
- From one PC to many
- Disk image jobs
- Schedules and retention
- Encryption and storage
- How images are checked
- Single files from an image
- Recovery media
- Restoring a whole machine
- Linux machines
- How to test it
- Limits
Macrium and Macrium Reflect are trademarks of their respective owners. BackupZit and MaxZit are not affiliated with, endorsed by or connected to Macrium. The names are used here only because many people search for an alternative.
At a glance
| Job | In BackupZit | Main limits |
|---|---|---|
| Image jobs | All internal disks, or one disk whole or in part; one job for many Windows machines | Windows (NTFS) only |
| Size | One VSS snapshot, used blocks only, only new data uploaded | Every image reads all used blocks again |
| Storage | SFTP, SMB, S3, Azure Blob, hardened repository, local and rotating USB disks; AES-256 | Immutability only on S3 Object Lock or the hardened repository |
| Checks | Restore tests of random blocks, a check of all stored data | No automatic boot test for images |
| Single files | Browse, download, restore to any agent | In the console only on network storage; no drive-letter mount |
| Whole machines | Recovery ISO; same or different hardware; into Proxmox VE or Hyper-V VMs | Not between UEFI and legacy BIOS |
From one PC to many
Each machine gets the agent, a service that connects out to the console (no open ports on the clients) and writes its images directly to the storage: the Windows MSI for Windows 10, 11 and Server 2016 or newer, the legacy MSI for Windows 7 SP1, Server 2008 R2 SP1 and 2012 R2, with the same image features.
- Create enrollment token on Agents gives one code (BZ1-…) for any number of machines. Install silently through GPO, Intune or an RMM tool (
msiexec /i backupzit-agent.msi /qn ENROLLCODE="BZ1-..."), or from the console with Install on a machine from here over WinRM. - In the job form the Agent list offers All Windows agents and Choose agents…. Such a Disk image job images all internal disks of every machine it covers; with All Windows agents, machines that enroll later join within a minute. Each machine keeps its own repository, history and retention, and Run backup now on all agents starts them all.
- Names and tags (a site, a department) help to find agents; they do not limit who sees them. Users can start Back up now from the icon next to the clock; jobs and schedules are set only in the console.
Disk image jobs
Under Backup jobs, a Disk image job for one machine shows the Disks of the selected agent. Choose All disks — every internal disk with a partition table, also disks added later; USB and SD disks, mounted VHD/VHDX files and removable media are left out — or tick one disk, whole or only some partitions.
- VSS: the image is read from a Volume Shadow Copy snapshot while Windows keeps running; all volumes are snapshotted together, so a database on D: and its logs on E: match.
- Used blocks only: on NTFS volumes only the clusters in use are read; small partitions such as the EFI partition are read whole.
- Only new data is uploaded: every image reads the used blocks again, but blocks already in the machine's repository are not stored again, so the second image usually uploads only a few percent. New data is compressed with zstd and encrypted.
- Each image is a complete restore point on its own. GPT and MBR disks, UEFI and BIOS boot are supported.
Schedules and retention
- Schedule: At specific times on the days you tick (one day gives a weekly image), Repeatedly, every few hours or minutes, Once a month, After another job or Manually only. A machine that was off runs its backup when its agent is back.
- Keep backups: Most recent, Daily, Weekly and Monthly; for a weekly image, 4 weekly and 12 monthly keep about a year. Retention also deletes the data no kept image uses.
- Backup window: start only between, Limit the upload speed to (MB/s) for working hours, and a Recovery point objective (RPO), hours that alerts once when the newest good image gets too old.
A weekly image plus daily file backups of the user folders is a common combination.
Encryption and storage
Images go to a target under Storage targets: SFTP, an SMB share, S3-compatible storage, Azure Blob Storage, the BackupZit Hardened repository, a local path or rotating USB disks.
- Encrypt backups (AES-256) is on by default: everything is encrypted on the machine before it leaves it. Keep the Recovery key away from the backups; with it and the storage credentials, images can be restored even without the console.
- Rotating USB / removable disks (offline copies): name the disks BZBACKUP1, BZBACKUP2 … and add one target with the label
BZBACKUP*; the connected disk is found whatever its drive letter. Each disk holds a complete backup; a run without a disk fails with an alert. - Backup copy jobs copy the images to a second target with their own retention, for example from the NAS to S3 or a USB disk; only new data is sent.
- Immutable copies: S3 Object Lock in compliance mode, or the hardened repository.
Keep the images themselves on network storage (SFTP, SMB, S3, Azure or a hardened repository): browsing files in the console works only there, and copies of disk images are restored with the command-line agent. See the 3-2-1 guide.
How images are checked
- Restore tests (weekly by default, Settings → Restore tests) read random blocks of the newest image and verify them against the stored checksums — storage access, credentials, key and data in one go. Test restore on the job page starts one at once.
- Check the stored data (monthly by default) reads every piece of data in each repository, which finds a failing NAS disk or bit rot; Check data starts it at once, and a check that finds damaged data offers Repair.
- An image with a sudden jump in new data is marked suspicious, an alert goes out and retention pauses.
Readable blocks do not prove that Windows starts. There is no automatic boot test for disk images, so restore one into an empty VM now and then (see below).
Single files from an image
On the image run (or in the Restore wizard under Files from a disk image) click Browse files: the console opens the NTFS volumes inside the image. Tick files and folders, then Download them — one file as it is, several as a ZIP — or choose Or restore them on an agent to put them into a folder on any agent (D:\Restore\C\Users\…). The audit log records downloads.
Browsing needs the image on network storage; for images on a local or USB disk, the command-line agent lists and copies files (image-ls, image-extract). BackupZit does not mount an image as a drive letter.
Recovery media
A machine whose disk is gone boots from a recovery ISO on a USB stick (or attached to a VM) and appears in the console as a recovery agent. One stick serves every Windows machine whose disks and network card it sees.
- Windows: Windows PE may not be redistributed, so the ISO is built once with the free Windows ADK, its Windows PE add-on and
build-winpe.ps1from the release:.\build-winpe.ps1 -AgentExe .\backupzit-agent.exe -Out .\backupzit-recovery.iso -DriverDir C:\Driversbackupzit-agent.execomes from any machine with the agent;-DriverDiradds storage and network drivers, such as VirtIO for Proxmox VE VMs. Copied to the console's/var/lib/backupzit/dist, the ISO is offered on Recovery media. - Linux: the recovery ISO is published with every release.
- Create recovery code on Recovery media gives a
recovery.jsonfor abackupzitfolder on the stick, so it connects without typing. A code is valid for 30 days; without one, the recovery system asks for the address and a code.
Restoring a whole machine
On the image run, or under Disk image / bare metal in the wizard, choose Restore this image to a disk: Restore on agent (the recovery agent, or a running machine with a spare disk) and the Target disk, which is erased. It must reach the end of the original's last partition and have the same sector size; partitions keep their sizes. For an All disks image pick the Disk of the backup and restore the system disk first.
- Leave the disk offline afterwards when the original disk is in the same machine, so Windows does not change the copy's disk IDs.
- Restore to different hardware for a new mainboard, controller or NVMe drive: the Windows drivers for common disk controllers start at boot again, drivers from the ISO and Additional drivers are added with DISM, and the boot files are rebuilt.
- Physical to virtual: boot an empty VM with the same firmware type from the ISO — in Proxmox VE with a VirtIO disk and network card (ISO built with VirtIO), in Hyper-V generation 2 for UEFI and 1 for BIOS — and restore with Restore to different hardware. It is also the simplest proof that an image boots.
Not possible: restoring between UEFI and legacy BIOS. There is no live disk-to-disk clone; to move a machine onto a new disk, restore an image onto it. Windows activation may ask to be repeated. Step by step: Windows bare-metal restore.
Linux machines
Linux machines get a Linux system job instead of an image: all local file systems (ext2/3/4, xfs, vfat, also on LVM) file by file, plus the disk layout and boot code. Restore the whole system → Onto a disk from the Linux ISO recreates it on a larger or smaller disk (if the data fits), or As a new Proxmox VM. Not yet: LUKS, mdadm and btrfs; a whole-system restore recreates one disk.
How to test it next to your current imaging tool
- Keep your current images running. Import the BackupZit appliance as a small VM (OVA, qcow2 or VHDX) and give it its own storage target, so the existing images are never touched.
- Start with a few machines: a server and two or three PCs in one job with Choose agents…, scheduled at other times than your current imaging.
- Build the recovery media first and restore one image into an empty VM — never over a disk in use. A copy that runs next to the original reports as the same agent; the console holds that agent's runs until one of the two machines is shut down.
- Get single files back with Browse files and Download.
- Compare over a few weeks: each run page shows the data read, the new data uploaded and the compression ratio; Storage usage shows the growth.
- 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
- Disk images are for Windows (NTFS, GPT and MBR disks); Linux uses a Linux system job. No agent for macOS.
- Every image reads all used blocks again; deduplication keeps the upload small, not the read.
- No live disk-to-disk clone, no drive-letter mount of an image, no automatic boot test of images.
- Browsing files in the console needs network storage; copies of disk images are restored with the command-line agent.
- The target disk needs the same sector size and enough room for the original partitions; no restore between UEFI and legacy BIOS; the Windows recovery ISO is built once with the Windows ADK.
- No hosted storage or cloud console; everyone who can sign in to a console sees all its agents.
- The console and its guide come in 14 languages; paid support is provided in English only.
Next steps
Download BackupZit, see the disk image features and the supported systems, or read Disk images & bare-metal recovery in the user guide in the console. Related guides: Windows bare-metal restore, free Acronis alternative for servers and PCs, 3-2-1 backup with immutable copies and the overview for all areas. Questions are welcome in GitHub Discussions; companies can get commercial support from MaxZit (in English).