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; it describes BackupZit only, so you can check it against what your environment needs.
- Only Proxmox VE? Use Proxmox Backup Server
- At a glance
- Proxmox VE in BackupZit
- The rest of a mixed environment
- One console, one set of rules
- Storage and immutability
- How to test it next to Proxmox Backup Server
- Limits
Proxmox and Proxmox Backup Server are trademarks of their owner. BackupZit and MaxZit are not affiliated with, endorsed by or connected to Proxmox. The names are used here only because many people search for them.
Only Proxmox VE? Use Proxmox Backup Server
Proxmox Backup Server is Proxmox's own backup server. For a setup that consists of Proxmox VE hosts only, it is the natural choice, and BackupZit does not claim to replace it there.
BackupZit exists for the other case: the Proxmox cluster is one part of the environment, and there are also Windows and Linux servers, PCs, VMware ESXi or Hyper-V hosts, SQL Server, PostgreSQL or MySQL databases, NAS shares or a Microsoft 365 tenant. Then the question is not which tool backs up Proxmox VE best, but whether one console for all of it is worth more than one tool per platform. The rest of this guide gives you the facts to decide that for your environment.
At a glance
| Area | In BackupZit | Main limits |
|---|---|---|
| Proxmox VE | VMs and containers of Proxmox VE 7, 8 and 9 from snapshots (containers on ZFS file by file, only changed files from the second backup on), changed block tracking, instant recovery, replicas, boot tests, host configuration | Container volumes that are directories on non-ZFS storage; replicas of containers on ZFS; some raw disks only while stopped |
| VMware and Hyper-V | ESXi 6.7–8 and vCenter 7/8 through a proxy agent; Hyper-V on Windows Server 2016 or newer, also failover clusters | No instant recovery for Hyper-V yet |
| Physical machines | Windows and Linux files, Windows disk images, Linux system backups, bare-metal restore, P2V into Proxmox VE | No macOS agent |
| Databases | SQL Server, PostgreSQL, MySQL/MariaDB with log backups and point-in-time restore | Only on the agent's own machine |
| Microsoft 365 | Exchange Online mail, calendars, contacts, OneDrive, SharePoint libraries | No restore into the mailbox yet; no Teams chats |
| NAS shares | SMB and NFS shares read by any agent, nothing installed on the NAS | — |
| Storage | SFTP, S3, SMB, Azure Blob, USB and local disks, hardened repository; deduplicated, compressed, encrypted | Deduplication per agent, not between computers |
Proxmox VE in BackupZit
The Linux agent runs on every Proxmox node and uses the node's own tools (qm, pct, pvesm, LVM, ZFS, Ceph); no API token or password is stored in the console. In Backup jobs choose the node's agent and Virtual machines (Proxmox VE, Hyper-V, VMware), then All VMs (and containers) on the host, All VMs (and containers) on the host except the ticked ones or single guests.
- Backup: a temporary snapshot (
backupzit_…) per guest; with the QEMU guest agent enabled, Proxmox freezes the file systems first. Disks are read in 1 MiB blocks by default (256 or 512 KiB per job under Advanced → VM deduplication block size), and running VMs on LVM-thin, ZFS, Ceph RBD or qcow2 files get changed block tracking with QEMU dirty bitmaps. - Containers on ZFS: backed up file by file from a temporary ZFS snapshot while they run; from the second backup on, only changed files are read. They are restored onto a ZFS storage as new subvolumes, and their files can be browsed and restored like those of a file backup.
- Restore: as a new guest with the next free ID, with its original ID, on any node with the agent (also in another cluster) and onto another storage. Restored VMs get a new generation ID.
- Instant recovery: Instantly, running from the backup starts a VM within seconds from the backup; Finish moves its disks to normal storage while it runs.
- Replicas: Keep replicas of the VMs keeps stopped, up-to-date copies on another node; Start replica runs one without a restore.
- Restore tests: random blocks of VM backups are checked, and the Boot test starts each VM from the backup without network to prove that it boots.
- Single files: Browse files opens NTFS, ext2/3/4 and XFS inside the backup, also on LVM; Download or Restore on agent.
- The node itself: a files job with Fill in the host configuration backs up
/etc, the cluster configuration database and/root, for rebuilding a failed node.
Limits: container volumes that are directories on non-ZFS storage and replicas of containers on ZFS are not supported; raw disks on directory, NFS or CIFS storage and thick LVM are backed up only while the guest is stopped; disks marked Backup: no, passed-through disks and bind mounts are skipped with a warning. A job backs up the guests on its agent's node, so in a cluster every node gets the agent and a job. Instant recovery is for VMs, not containers. Step by step: Proxmox VE backup guide.
The rest of a mixed environment
- VMware ESXi 6.7, 7 and 8 and vCenter Server 7 and 8: nothing is installed on the host; a BackupZit agent works as its proxy, with changed block tracking and quiesced snapshots through VMware Tools. Hosts with the free ESXi license work too (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. See the VMware ESXi guide.
- Hyper-V on Windows Server 2016 or newer and Windows 10/11: the Windows agent on the host uses recovery checkpoints and Resilient Change Tracking; one job covers a whole failover cluster. See the Hyper-V guide.
- Physical Windows and Linux machines: Files and folders, a Disk image of Windows disks and a Linux system backup, with bare-metal restore from a recovery ISO. A Windows image can be restored into a Proxmox VM with Restore to different hardware, and a Linux system backup can become a new Proxmox VM. See the guide for servers and PCs.
- Databases: SQL Server, PostgreSQL and MySQL/MariaDB with log backups and restores to any point in time. See the database guide.
- Microsoft 365: Exchange Online mail, calendars, contacts, OneDrive and SharePoint libraries through Microsoft Graph with read-only permissions. See the Microsoft 365 guide.
- NAS shares: a NAS / file share job backs up an SMB or NFS share through any agent that reaches it.
One console, one set of rules
The console is a small Linux VM with PostgreSQL (2 vCPU, 2–4 GB RAM, 20 GB disk); on Proxmox VE the quickest way is the ready-made image backupzit-appliance.qcow2 from the download page. It does not store backup data: the agents connect out to it on TCP 8443 and write the backups straight to the storage.
- Schedules, backup windows, retention and the Recovery point objective (RPO), hours are set the same way for every kind of job.
- The dashboard, Reports (PDF and CSV), email, Slack, Microsoft Teams, webhooks and Prometheus metrics cover all jobs.
- Four roles, LDAP / Active Directory, single sign-on with SAML or OpenID Connect, two-factor sign-in, optional four-eyes approval and an audit log apply to everything in the console.
Storage and immutability
Storage targets: SFTP, S3-compatible storage (AWS, Wasabi, Backblaze B2, MinIO, Google Cloud Storage), SMB shares, Azure Blob Storage, rotating USB disks, local or mounted disks and the BackupZit hardened repository. Every backup is deduplicated across the jobs of one agent on the same target, compressed with zstd and, with Encrypt backups (AES-256) on, encrypted on the agent; the Recovery key restores without the console. Immutable copies come from S3 Object Lock or the hardened repository, and a Backup copy job sends a second copy off site. The 3-2-1 guide shows a complete setup.
BackupZit writes only into its own repositories on these targets; it does not read or write the datastores of another backup server.
How to test it next to Proxmox Backup Server
- Leave your Proxmox Backup Server jobs as they are. Import the appliance as a small VM and give BackupZit a storage target of its own, for example an SFTP folder or an S3 bucket.
- Start with one node: install the agent, create a job for a few test guests and schedule it at other times than the existing backups of the same guests.
- Check how the guests were read. BackupZit takes its own temporary snapshot for each backup, and its changed block tracking uses dirty bitmaps of its own (named
backupzit-…) and leaves bitmaps of other software in place. The run page shows each disk and whether it was read as changed blocks only. - Add the parts of your environment that are not Proxmox VE: a Windows server as a disk image, a VMware or Hyper-V host, a database or the Microsoft 365 tenant.
- Restore, not just back up: a guest as a new guest next to the original, single files, an instant recovery, a disk image into a Proxmox VM with the recovery ISO. Turn on the automatic restore tests with the boot test.
- 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
- Proxmox VE: container volumes that are directories on non-ZFS storage are not backed up, and replicas of containers on ZFS are not supported; raw disks on directory, NFS or CIFS storage and thick LVM only while the guest is stopped; instant recovery only for VMs.
- No XCP-ng support and no macOS agent; no instant recovery for Hyper-V yet.
- Microsoft 365: no restore directly into mailboxes or OneDrive yet, no Teams chats.
- Deduplication works per agent, not between computers.
- The console runs on Linux (Debian 12+, Ubuntu 22.04+, AlmaLinux or Rocky Linux 9+, x86-64), the appliance or Docker; one organization per console.
- The console and its guide come in 14 languages; paid support is provided in English only.
Next steps
Download BackupZit, see the Proxmox features, all features and the supported systems, or read the user guide in the console. Broader overviews are the open-source Veeam alternative and open-source NAKIVO alternative guides. Questions are welcome in GitHub Discussions; companies can get commercial support from MaxZit (in English).
Proxmox, Proxmox VE and Proxmox Backup Server are trademarks of their owner. BackupZit and MaxZit are not affiliated with, endorsed by or connected to Proxmox.