BackupZit

Open-source Veeam alternative: what BackupZit covers and what it does not

Many people look for a free or open-source replacement for a commercial backup suite. This guide goes through the jobs such a suite usually does — VM backup, agent backup, bare-metal restore, databases, Microsoft 365, immutable copies, instant recovery, restore tests, alerts and roles — and says for each one what BackupZit does today and where it stops.

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: every organization runs its own console on its 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; it describes BackupZit only, so you can check it against what your environment needs.

Veeam is a trademark of its owner. BackupZit and MaxZit are not affiliated with, endorsed by or connected to Veeam. The name is used here only because many people search for it.

At a glance

JobIn BackupZitMain limits
VM backupProxmox VE, VMware ESXi and vCenter, Hyper-V (also failover clusters), agentless with changed blocks onlyNo XCP-ng; some disk types per hypervisor
Agent backupWindows and Linux files, Windows disk images, Linux system backups, NAS sharesNo macOS agent
Bare-metal restoreWindows and Linux recovery ISOs, also onto different hardware or into a VMNot between UEFI and legacy BIOS
DatabasesSQL Server, PostgreSQL, MySQL/MariaDB with log backups and point-in-time restoreOnly servers on the agent's own machine; no single tables
Microsoft 365Exchange Online mail, calendars, contacts, OneDrive, SharePoint librariesNo restore into the mailbox yet; no Teams chats
Immutable and off-site copiesS3 Object Lock, hardened Linux repository, backup copy jobs, rotating USB disksSMB, SFTP and local disks are not immutable by themselves
Instant recoveryProxmox VE VMs and VMware VMs run straight from the backupNot for Hyper-V yet; VMware needs a Linux proxy agent
Restore testsAutomatic sample restores, full data checks, boot tests of Proxmox VMsBoot tests only for Proxmox VMs
Alerts and reportsEmail, Slack, Teams, webhooks, RPO, PDF/CSV reports, ransomware detection—
Roles and auditFour roles, LDAP/AD, SAML, OpenID Connect, two-factor, four-eyes approval, tamper-evident audit log—

Virtual machines: Proxmox VE, VMware and Hyper-V

All three hypervisors are backed up without an agent inside the VMs, into the same console, storage and retention rules.

  • Proxmox VE 7, 8 and 9: the agent runs on a node and backs up VMs and containers from snapshots; running VMs on LVM-thin, ZFS, Ceph RBD or qcow2 files get changed block tracking. Containers on ZFS are backed up file by file from a temporary ZFS snapshot while they run; from the second backup on, only changed files are read. Restore as a new guest or in place, single files, instant recovery, replicas and boot tests. Not yet: container volumes that are directories on non-ZFS storage, and replicas of containers on ZFS; raw disks on directory, NFS or CIFS storage and thick LVM only while the guest is stopped; passed-through disks and bind mounts are skipped with a warning. See the Proxmox VE guide.
  • VMware ESXi 6.7, 7 and 8 and vCenter Server 7 and 8: a BackupZit agent on any machine works as the host's proxy, with changed block tracking. Hosts with the free ESXi license work too (snapshots and restores over SSH). Optional hot-add (a Linux proxy agent in a VM, with vCenter or a licensed host) reads running VMs without a temporary copy on the datastore. Restore as a new VM or in place, single files and instant recovery over NFS. Not yet: a vCenter with several datacenters (add the other hosts directly), raw device mappings and independent disks, VMs with snapshots of their own; connected ISO images are not part of the backup. See the VMware ESXi guide.
  • Hyper-V on Windows Server 2016 or newer and Windows 10/11: the Windows agent on the host uses Resilient Change Tracking. Restore as a new VM on the same or another Hyper-V host, in place, or single files. With the agent on every node, one job covers all VMs of a failover cluster, and a VM keeps its history when it moves. Not yet: shared VHDX, VHD Set and pass-through disks, and instant recovery. See the Hyper-V guide.

XCP-ng is not supported.

Windows and Linux servers and PCs

Agents run as a service on the protected machines, connect out to the console (no open ports on the clients) and write directly to the storage. Under Backup jobs you choose the kind:

  • Files and folders on Windows and Linux, incremental, from a VSS snapshot on Windows. Single files can be downloaded in the browser with Browse files.
  • Disk image of one, several or all disks of a Windows machine (NTFS volumes, GPT and MBR disks), changed blocks only.
  • Single files from disk images: Browse files on an image run opens its NTFS volumes; Download gives one file as it is or several as a ZIP, or restore them on any agent.
  • Linux system: all local file systems (ext2/3/4, xfs, vfat, also on LVM) and the disk layout, to rebuild the machine on an empty disk.
  • NAS shares over SMB or NFS, read by any agent; nothing is installed on the NAS.

Supported: Windows 10, 11 and Server 2016 or newer (MSI), Windows 7 SP1, Server 2008 R2 SP1 and 2012 R2 (legacy MSI), and 64-bit Debian, Ubuntu, AlmaLinux and Rocky Linux. Agents can be pushed to Windows machines over WinRM and update themselves from the console. There is no agent for macOS. A Linux system job does not support LUKS-encrypted disks, software RAID (mdadm) or btrfs; it reports them 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 Windows recovery ISO is built once with the free Windows ADK and build-winpe.ps1 from the release, because Windows PE may not be redistributed. Write it to a USB stick with Rufus in ISO mode or attach it to a VM, and boot the machine from it. It appears in the console as a recovery agent; on the image backup run choose Restore this image to a disk. With Restore to different hardware BackupZit enables the disk controller drivers that are part of Windows, adds drivers with DISM (the ISO carries the VirtIO drivers) and rebuilds the boot files — so an image can go to new hardware, Hyper-V or a Proxmox VM.

For Linux, the Linux recovery ISO and Restore the whole system bring a system backup back onto a disk, or create a new Proxmox VM from it (physical-to-virtual). The target disk may be larger or smaller than the original as long as the data fits.

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.

SQL Server, PostgreSQL and MySQL

A Databases job uses the database server's own tools on the database machine: Microsoft SQL Server from 2012 on (including Express), PostgreSQL and MySQL/MariaDB. Full backups follow the schedule; log backups every few minutes allow restoring a single database to a point in time, under a new name or in place.

Not included: SQL Server differential backups and Always On availability groups, remote database servers (the agent backs up servers on its own machine), and restoring single tables (restore under a new name and copy the rows). MySQL users and privileges are not part of the dumps.

Microsoft 365

A Microsoft 365 job backs up Exchange Online mail (.eml), calendars (.ics), contacts (.vcf), OneDrive and SharePoint document libraries through Microsoft Graph, with read-only application permissions. You restore by browsing and downloading, or into a folder on any agent.

Not included: restoring directly into a mailbox or OneDrive (planned), Teams chats and channel messages (Teams files are in SharePoint and are backed up with it), SharePoint lists and pages, attachments of calendar events, contact photos and shared mailboxes without a user account. Microsoft limits how fast an app may read, so a first backup of large mailboxes can take hours. See the Microsoft 365 guide.

Immutable and off-site copies

Storage targets are added under Storage → Add storage target: SFTP, S3-compatible storage (AWS, Wasabi, Backblaze B2, MinIO, Google Cloud Storage), SMB shares, Azure Blob Storage, rotating USB disks, local disks and the BackupZit hardened repository. Backups are deduplicated, compressed and, with Encrypt backups (AES-256) on (the default), encrypted before they leave the agent. With the Recovery key they can be restored even without the console.

  • Immutable: S3 with Object Lock in compliance mode, or Hardened repository (backupzit-repo on Linux, immutable) on your own Linux server.
  • Off-site: a Backup copy job copies the backups of another job to a second target, with its own retention.

Limits: SMB, SFTP and local disks have no immutability of their own; on Azure and Google Cloud the immutability is set in the cloud, not in BackupZit; copies of disk images are restored with the command-line agent. The 3-2-1 guide shows the full setup.

Instant recovery and replicas

With Instantly, running from the backup in the restore form, a VM starts within seconds while its disks are still in the backup:

  • Proxmox VE: the agent serves the disks read-only from the backup and creates a new VM; you then move it to normal storage. For VMs, not containers.
  • VMware: a Linux proxy agent serves the disks over NFS as a datastore. With vCenter, Finish moves the VM with Storage vMotion while it keeps running.
  • Replicas (Proxmox VE): a job can keep stopped, up-to-date copies of its guests on another node; Start replica starts one without a restore.

Limits: no instant recovery for Hyper-V yet (planned) or through a Windows proxy agent; the VM is only as fast as the backup storage, so distant SFTP or S3 storage makes it slow. Disk images and Linux system backups are restored by writing them to a disk.

Restore tests

Under Settings → Restore tests:

  • Test every job's newest backup automatically (weekly by default): a random sample of files is restored and verified byte by byte; for disk images, random blocks.
  • Check the stored data (monthly by default): every piece of data in each repository is read and verified. On cloud storage it runs only when enabled, because it downloads everything.
  • Boot test for Proxmox VM backups: each VM of the newest backup is started from the backup with its network disconnected.

Test restore and Check data on a job's page start them at once. Boot tests exist only for Proxmox VMs; for Windows images the user guide suggests restoring into an empty VM from the recovery ISO.

Alerts, reports and ransomware detection

  • Email notifications and Chat & webhooks (Slack, Microsoft Teams, any HTTP endpoint) for failures, warnings and successes.
  • Recovery point objective (RPO), hours per job; a job that misses it is reported, which also catches an agent offline for days.
  • The Dashboard lists under Needs attention failed jobs, missed RPOs, offline agents and storage that is almost full.
  • Reports as PDF and CSV, also emailed on a schedule, and a Calendar of past and planned runs.
  • Backups that look like ransomware or mass deletion trigger an alert and pause the job's retention, so the last clean backups are kept.
  • A REST API and Prometheus metrics for your own monitoring.

Roles, sign-in and audit

  • Four roles: Administrator, Backup operator, Restore operator and Viewer.
  • Local users, LDAP / Active Directory, and single sign-on with SAML 2.0 or OpenID Connect.
  • Two-factor sign-in, which can be required for administrators or all users under Settings → Sign-in & security.
  • Single sign-on users get their role from their groups at every sign-in; with OpenID Connect the console asks for the groups scope when the provider offers it (Authelia, Keycloak, authentik), and Additional scopes covers other providers. A last administrator who lost the second factor gets back in with backupzit-server --reset-two-factor USER on the server.
  • Four-eyes approval (optional): deleting jobs or storage, shortening retention and similar changes wait for a second user under Approvals.
  • Users → Audit log records sign-ins and changes; each entry is chained to the previous one, so edits in the database are detected.
  • Settings → Console backup backs up the console itself, and console and agents update themselves with signed packages.

How to evaluate it next to your current backup

  1. Keep your current backup running. Import the appliance (OVA, qcow2 or VHDX) as a small VM and give BackupZit its own storage target, separate from the existing backups.
  2. Start with a few machines of each kind you run — a VM per hypervisor, a Windows server, a database — and schedule the jobs so they do not run at the same time as your existing jobs on the same machines.
  3. Mind the overlaps. VMware VMs with snapshots of their own are not backed up, so check that no snapshot is left behind. SQL Server 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. On PostgreSQL, BackupZit leaves an existing archive_command alone and then backs up without point-in-time recovery.
  4. Test restores, not just backups. Restore files, a VM as a new VM next to the original, a database under a new name, and a disk image into an empty VM from the recovery ISO. Turn on the automatic restore tests.
  5. Compare the results. Each run page shows what was read, what was new and the compression ratio; Reports and the storage view show success rates and growth over a few weeks.
  6. Go through the limits below and in the Not yet included part of each chapter of the user guide, and ask in GitHub Discussions if something you need 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 macOS agent and no XCP-ng support.
  • Not yet: instant recovery for Hyper-V, restore directly into Microsoft 365 mailboxes, Teams chats.
  • Hypervisor disk types not backed up: Proxmox container volumes that are directories on non-ZFS storage; VMware raw device mappings and independent disks; Hyper-V shared VHDX, VHD Set and pass-through disks. Replicas of Proxmox containers on ZFS are not supported. A vCenter with several datacenters cannot be added as one.
  • Disk images are for Windows; Linux machines use a Linux system job, which does not support LUKS, mdadm or btrfs and restores a whole system onto one disk.
  • Databases only on the agent's own machine; no SQL Server differential backups, Always On availability groups or single-table restores.
  • The console runs on Linux (Debian 12+, Ubuntu 22.04+, AlmaLinux or Rocky Linux 9+, x86-64), the appliance or Docker.
  • The console and its guide come in 14 languages; paid support is provided in English only.

Next steps

Download BackupZit, see all features and the supported systems, or read the user guide in the console. The step-by-step guides cover Proxmox VE, VMware ESXi, Hyper-V, Microsoft 365, Windows bare-metal restore and 3-2-1 backup with immutable copies. Two focused overviews look at virtual machines and deployment and at disk images and file backups of servers and PCs. Questions are welcome in GitHub Discussions; companies can get commercial support from MaxZit (in English).