Skip to content

v2.0.4-beta

Latest

Choose a tag to compare

@sentry0 sentry0 released this 19 Oct 11:56

Fixes

  • "Bitmap already exists: virtnbdbackup.0" backups. VMSnap removed only libvirt's checkpoint metadata when starting a new backup period, leaving the bitmaps behind on the disk, so the next full backup failed. Checkpoints are now deleted together with their bitmaps.
  • Running and paused VMs. QEMU keeps a running VM's bitmaps in memory and only writes them to the image on shutdown, so VMSnap couldn't see or remove them. Bitmaps are now listed and removed through QEMU (QMP) for running/paused VMs, which also cleans up bitmaps orphaned by earlier versions. (libvirt marks a domain "tainted: custom-monitor" when this happens; it's harmless.)
  • Bi-annual pruning. The pruning window was measured from six months back instead of the start of the current half, so the previous half's backups were deleted on the first run of a new half. It now waits 90 days into the half, as documented.
  • Invalid --groupBy is rejected up front (exit code 10) instead of backing up into a folder named undefined.

New

  • --groupBy guard. A VM can only have one incremental chain, because checkpoints belong to the VM. VMSnap now refuses (exit code 10) to start a new chain when the VM's existing backups in --output use a different --groupBy, instead of silently wiping the existing chain's checkpoints. Pass --force to switch anyway.
  • --copy. Takes a standalone full copy into vmsnap-copy-{period} folders without creating or deleting checkpoints, so a second schedule (e.g. a quarterly copy) can run alongside a VM's backup chain. One copy per period; works with --prune.

See the README sections "One Backup Chain Per VM" and "Standalone Copies".

Full changelog: v2.0.3-beta...v2.0.4-beta