What this guide covers
BackupZit is free and open source under the GNU AGPLv3, with no limits on hosts, 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 is for readers who search for an Altaro VM Backup or Hornetsecurity VM Backup alternative; it does not compare prices or features of other products and describes BackupZit only.
- At a glance
- Hyper-V
- VMware ESXi and vCenter
- Proxmox VE for hosts you move
- A second copy off-site
- Immutable copies and ransomware
- Restores per hypervisor
- Monitoring and alerts
- How to test it
- Limits
Hornetsecurity, Altaro and Altaro VM Backup are trademarks of their respective owners. BackupZit and MaxZit are not affiliated with, endorsed by or connected to Hornetsecurity or Altaro. The names are used here only because many people search for an alternative.
At a glance
| Area | In BackupZit | Main limits |
|---|---|---|
| Hyper-V | Agent on the host, RCT, failover clusters, application-consistent option, excluded disks, vTPM | No instant recovery yet; no shared VHDX, VHD Set or pass-through disks |
| VMware | ESXi 6.7–8 (also the free license), vCenter 7 and 8, CBT, hot-add, several proxies per vCenter | One datacenter per vCenter; no RDM or independent disks |
| Proxmox VE | VMs and containers in the same console | No conversion between hypervisors |
| Copies | Backup copy jobs with their own retention; S3 Object Lock, hardened repository | SMB, SFTP and local disks are not immutable |
| Restores | New VM or in place, single files, instant recovery (Proxmox VE, VMware) | Replicas and boot tests only for Proxmox VE |
| Alerts | Dashboard, RPO, email, Slack, Teams, webhooks, reports | — |
Hyper-V
The Windows agent runs on the Hyper-V host — Windows Server 2016 or newer with the Hyper-V role, or Windows 10/11 with Hyper-V — and backs up its VMs without anything inside the guests. It uses the Hyper-V PowerShell module and the Windows Virtual Disk API; the console stores no Hyper-V credentials.
- Changed blocks only: each backup takes a temporary recovery checkpoint, which switches on Resilient Change Tracking (RCT). The first backup reads the whole disks, later ones only the blocks RCT reports as changed. The VM's configuration (generation, CPU, memory, network adapters, secure boot, TPM) is stored with it.
- Which VMs: All VMs (and containers) on the host, All VMs (and containers) on the host except the ticked ones — for example without the BackupZit console's VM — or ticked VMs.
- Consistency: Windows guests flush their applications through VSS, Linux guests with the Hyper-V daemons freeze their file systems; otherwise the checkpoint is crash-consistent, and the run page shows which kind each VM got. Require application-consistent checkpoints makes a VM fail instead of falling back — for Active Directory, SQL Server and Exchange. Old guests without VSS can be listed under VMs that may be crash-consistent.
- Exclude disks: data disks backed up another way are left out by file name pattern (
*-data.vhdx) or full path. - vTPM: generation 2 VMs keep their vTPM (BitLocker does not ask for the recovery key) when restored in place, on the same host or on a host with the original host's guardian certificate.
Failover clusters: with the agent on every node, the console recognises the cluster, and one job under Hyper-V failover clusters (virtual machines) covers All clustered VMs. Each VM is backed up by the node it runs on; after a live migration its history continues without a new full backup. Not backed up: shared VHDX, VHD Set and pass-through disks; shielded VMs are not supported. Step by step: Hyper-V guide.
VMware ESXi and vCenter
Nothing is installed on ESXi or in the VMs: any Windows or Linux agent works as the host's Proxy agent, takes the snapshots, reads the changed blocks and writes them to the storage. Hosts are added under Agents → VMware ESXi hosts → Add an ESXi host or vCenter Server.
- Versions: ESXi 6.7, 7 and 8, or vCenter Server 7 and 8 with its hosts; VMs moved with vMotion keep being backed up.
- Free ESXi license: snapshots and restores go over SSH. Changed block tracking can only be switched on while a VM is off; until a backup finds it off once, every backup reads the whole disks and warns.
- Consistency: with VMware Tools in the guest the snapshot is quiesced; without them it is crash-consistent.
- Hot-add: a Linux proxy agent running as a VM that sees the datastores reads the snapshot's disks in place, with vCenter or a licensed host. Without it, the disks of a running VM are copied thin on its datastore for a moment and read from there.
- Further proxies (new in 0.55, vCenter): a Linux agent in a VM on each ESXi host. Each backup is then split: every VM goes to the proxy on its own host and is read there through hot-add, the rest to the main proxy, all at the same time; the job shows the parts as one start. The first backup into a new repository is not split. All proxies need agent 0.55.
Not yet: a vCenter with several datacenters (add the other hosts directly), raw device mappings, independent disks, VMs with snapshots of their own. Step by step: VMware ESXi guide.
Proxmox VE for hosts you move
Hosts that move to Proxmox VE 7, 8 or 9 stay in the same console, storage and retention: the Linux agent on each node backs up VMs and containers from snapshots, with changed block tracking for running VMs on LVM-thin, ZFS, Ceph RBD and qcow2, and Proxmox VE has the most restore options. See the Proxmox VE guide.
VM backups are restored onto the same hypervisor; BackupZit does not convert a Hyper-V or VMware VM backup into a Proxmox VE VM. A Windows machine with the agent inside, physical or virtual, can be imaged with a Disk image job and restored into a Proxmox VE VM with Restore to different hardware; a Linux machine backed up with a Linux system job is restored with As a new Proxmox VM (see Windows bare-metal restore).
A second copy off-site
A Backup copy job copies the backups of a VM job to a second storage target, for example from the NAS to S3 or a hardened repository in another building:
- The agent of the source job copies existing backups; the hosts are not read again, and only data not yet at the destination is sent, encrypted with the destination's key.
- After each backup of the source job (the default) keeps the copy current; a nightly schedule and Limit the upload speed to (MB/s) suit a slow line.
- The copy has its own retention, for example 7 daily on the NAS and 12 monthly off-site.
- Whole VMs and single files are restored from the copy like from the original, for Hyper-V, VMware and Proxmox VE.
- For an offline copy, a copy job can write to rotating USB disks found by their volume label.
Immutable copies and ransomware
- S3 Object Lock: on a bucket with Object Lock, every file is locked in compliance mode for N days; nobody, not even someone with the storage keys, can delete or overwrite it before then. After each backup the agent extends the locks of all data the retention keeps, since 0.55 16 objects at a time with the progress on the run page.
- Hardened repository:
backupzit-repoon a Linux server of your own. Agents and the console can only add files, which get the immutable flag for a period set on that server, not in the console. - Encrypt backups (AES-256) on the agent before data leaves it; keep the Recovery key offline.
- A backup with a sudden jump in new data is marked suspicious: an alert goes out and the job's retention pauses until someone clicks Reviewed — resume retention.
- Optional Four-eyes approval: deleting jobs or storage targets and shortening retention wait for a second user.
The 3-2-1 guide shows a complete setup.
Restores per hypervisor
Restores start on the backup's page in Activity or in the Restore wizard (Whole VM or container, Files from a VM or container), which lists the VMs of all hypervisors.
| Restore | Hyper-V | VMware | Proxmox VE |
|---|---|---|---|
| As a new VM | yes, new MAC addresses | yes, new UUID and MAC addresses | yes, next free ID |
| In place | yes, keeps ID and MAC addresses | yes, keeps UUID and MAC addresses | yes, original ID |
| Other host | any host with the agent; a Cluster Shared Volume as a cluster role | another host or datastore | any node with the agent |
| Single files | NTFS, ext2/3/4, XFS, also on LVM | the same | the same |
| Instant recovery | not yet | yes, through a Linux proxy agent | yes |
| Replicas, boot tests | no | no | yes |
Instantly, running from the backup starts a VM within seconds while its disks are still in the backup. Finish moves it to normal storage while it runs (on a single ESXi host with a short shutdown); Discard VM deletes it with its changes. Such a VM is only as fast as the backup storage. A Hyper-V restore copies the disks first; instant recovery for Hyper-V is planned. Restore tests read random blocks of VM backups on all three hypervisors.
Monitoring and alerts
- The Dashboard counts the protected VMs and lists under Needs attention failed jobs, missed schedules, agents that have not connected for 15 minutes and storage that is filling up.
- A VM that could not be backed up makes the run failed and is named; the other VMs are kept, and retention is skipped so its older restore points stay.
- Recovery point objective (RPO), hours per job: one alert when the newest good backup gets too old, also when a schedule was removed or a host is offline for days.
- Email for failures, warnings or successes and a daily report; Slack, Microsoft Teams and webhooks under Chat & webhooks; Reports as PDF and CSV, also as Scheduled reports; a REST API and Prometheus metrics.
How to test it next to your current VM backup
- Leave your current VM backup as it is. Import the appliance (VHDX for Hyper-V, OVA for VMware) as a small VM and give BackupZit its own storage target.
- Pick a few VMs per host and schedule them at other times than the existing jobs of the same VMs, so two tools do not take checkpoints or snapshots of a VM at once.
- Watch the overlaps. On VMware, VMs with snapshots of their own are not backed up, so check that no other tool leaves a snapshot behind. On Windows 10/11 hosts turn off automatic checkpoints for server VMs.
- Restore, not just back up: a VM as a new VM next to the original, single files from a VM, and on VMware an instant recovery through a Linux proxy. Keep the automatic restore tests on.
- Compare over a few weeks: each run page shows what was read, what was new and the compression ratio; Reports and Storage usage show success rates and 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
- Hyper-V: no instant recovery yet, no replicas or boot tests; shared VHDX, VHD Set and pass-through disks are not backed up; shielded VMs are not supported.
- VMware: one datacenter per vCenter; no raw device mappings, independent disks or VMs with snapshots of their own; instant recovery and hot-add need a Linux proxy agent; further proxies need a vCenter connection.
- VM backups are restored onto the same hypervisor; no XCP-ng.
- Immutability only on S3 Object Lock or the hardened repository; you bring the storage, MaxZit hosts none.
- The console runs on Linux (Debian 12+, Ubuntu 22.04+, AlmaLinux or Rocky Linux 9+), 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 Hyper-V, VMware and ransomware protection features, or read the chapters Hyper-V virtual machines and VMware ESXi virtual machines in the user guide in the console. Step-by-step guides: Hyper-V backup, VMware ESXi backup, Proxmox VE backup and 3-2-1 backup with immutable copies; a broader overview is the open-source NAKIVO alternative guide. Questions are welcome in GitHub Discussions; companies can get commercial support from MaxZit (in English).
Hornetsecurity, Altaro and Altaro VM Backup are trademarks of their respective owners. BackupZit and MaxZit are not affiliated with, endorsed by or connected to Hornetsecurity or Altaro.