Download Latest Version backupzit-appliance.ova (1.4 GB)
Home / v0.48.0
Name Modified Size InfoDownloads / Week
Parent folder
SOURCE-CODE.txt 2026-11-06 1.7 kB
build-winpe.ps1 2026-11-06 3.8 kB
install.sh 2026-11-06 8.6 kB
backupzit-server_0.48.0_amd64.deb 2026-11-06 64.3 MB
manifest.json 2026-11-06 4.6 kB
manifest.json.sig 2026-11-06 89 Bytes
backupzit-server-0.48.0-1.x86_64.rpm 2026-11-06 64.7 MB
backupzit-repo_0.48.0_amd64.deb 2026-11-06 3.3 MB
backupzit-agent-0.48.0-1.x86_64.rpm 2026-11-06 9.5 MB
backupzit-agent-0.48.0-x64-legacy.msi 2026-11-06 10.1 MB
backupzit-agent-0.48.0-x64.msi 2026-11-06 10.1 MB
backupzit-agent_0.48.0_amd64.deb 2026-11-06 9.4 MB
backupzit-repo-0.48.0-1.x86_64.rpm 2026-11-06 3.3 MB
BackupZit 0.48.0 source code.tar.gz 2026-11-06 6.3 MB
BackupZit 0.48.0 source code.zip 2026-11-06 6.9 MB
README.md 2026-11-06 2.5 kB
Totals: 16 Items   187.9 MB 7

Hyper-V

From the questions in discussion [#10]:

  • Require application-consistent checkpoints (new job option, also for jobs of a failover cluster): a running VM is backed up only from a checkpoint the guest prepared with VSS. If that is not possible, the VM is not backed up and the run fails (with a notification) instead of taking a crash-consistent checkpoint. The other VMs of the job are still backed up and can be restored from that run. Meant for Active Directory, SQL Server, Exchange and other databases. Needs agents 0.48.0 or newer; older agents get a failed run asking to update them.
  • Live migration during a backup: a VM that moves to another node while it is being backed up is still backed up completely. Until now the backup's checkpoint stayed on the VM (silently) until the next backup; now the node the VM moved to removes it within a few minutes, and the run says that the VM moved.
  • vTPM and BitLocker: backups of Generation 2 VMs with a virtual TPM also keep the vTPM (guest state file and key protector). Restored as a new VM on the same host, or on a host with the original host's guardian certificate, the VM gets its vTPM back and BitLocker does not ask for the recovery key. On other hosts the VM gets a new, empty vTPM and the restore explains how to avoid that. Shielded VMs (Host Guardian Service) are not supported.
  • A restore on a cluster node adds the VM as a cluster role only when the VM was clustered or its files are on a Cluster Shared Volume; before, a restored local VM also became a role that could not fail over.

REST API and webhooks

  • OpenAPI specification: the console serves it at /api/v1/openapi.json (no token needed); the file is also in the repository: internal/server/openapi.json (github.com). A test keeps it in step with the code.
  • Restore over the API: POST /api/v1/runs/{id}/restore restores files of a backup into a folder on an agent, or to the original location (role: restore operator; in the audit log).
  • GET /api/v1/runs/{id} also returns the output of the commands before and after a backup.
  • Webhooks (run.finished) now also carry agent_id, duration_s, files, bytes, bytes_read, bytes_stored and snapshot, so a dashboard needs no extra API call.

Guides updated in all 14 languages.

Releases are signed with the BackupZit release key; consoles verify them before installing.

Source: README.md, updated 2026-11-06