| Name | Modified | Size | Downloads / Week |
|---|---|---|---|
| Parent folder | |||
| SHA256SUMS | < 15 hours ago | 367 Bytes | |
| backupzit-appliance-vhdx.zip | < 15 hours ago | 1.5 GB | |
| backupzit-appliance.qcow2 | < 16 hours ago | 1.5 GB | |
| backupzit-appliance.ova | < 16 hours ago | 1.5 GB | |
| backupzit-appliance.iso | < 16 hours ago | 1.1 GB | |
| backupzit-recovery-linux.iso | < 16 hours ago | 359.7 MB | |
| SOURCE-CODE.txt | < 17 hours ago | 1.7 kB | |
| build-winpe.ps1 | < 17 hours ago | 3.8 kB | |
| install.sh | < 17 hours ago | 8.6 kB | |
| backupzit-server_0.43.4_amd64.deb | < 17 hours ago | 63.9 MB | |
| manifest.json | < 17 hours ago | 3.5 kB | |
| manifest.json.sig | < 17 hours ago | 89 Bytes | |
| backupzit-server-0.43.4-1.x86_64.rpm | < 17 hours ago | 64.2 MB | |
| backupzit-repo_0.43.4_amd64.deb | < 17 hours ago | 3.3 MB | |
| backupzit-agent-0.43.4-1.x86_64.rpm | < 17 hours ago | 9.5 MB | |
| backupzit-agent-0.43.4-x64-legacy.msi | < 17 hours ago | 10.0 MB | |
| backupzit-agent-0.43.4-x64.msi | < 17 hours ago | 10.0 MB | |
| backupzit-agent_0.43.4_amd64.deb | < 17 hours ago | 9.3 MB | |
| backupzit-repo-0.43.4-1.x86_64.rpm | < 17 hours ago | 3.3 MB | |
| BackupZit 0.43.4 source code.tar.gz | < 17 hours ago | 5.8 MB | |
| BackupZit 0.43.4 source code.zip | < 17 hours ago | 6.5 MB | |
| README.md | < 17 hours ago | 1.5 kB | |
| Totals: 22 Items | 6.1 GB | 0 | |
Proxmox VE 9
BackupZit now supports Proxmox VE 7, 8 and 9. Tested on Proxmox VE 9.2 (Debian 13, kernel 7.0) on a node upgraded from 8.4: backup of VMs and containers, restore as a new VM (started) and as a new container, instant recovery, the automatic restore test with boot test and the data check.
Backing up the Proxmox host configuration
The user guide (Proxmox VE → Backing up the host configuration) describes how to protect the node itself — storage definitions, network, users, firewall, certificates and the settings of every VM and container — with an ordinary files job on the node's agent (/etc with /etc/pve, and /var/lib/pve-cluster), a consistent copy of the configuration database made by a command before the backup, and how to rebuild a failed node.
Clear message when the clock is wrong
S3 and Azure storage refuse requests from a computer whose clock is more than about 15 minutes off. The message now says so — "the clock of this computer differs from the storage's by more than 15 minutes: correct the time (turn on time synchronization)" — instead of only "the difference between the request time and the server's time is too large". The connection test in the console names the console's clock. Troubleshooting guide in all 14 languages.
Update the console and then the agents (Agents → Update all).
Releases are signed with the BackupZit release key; consoles verify them before installing.