Version 2.24

Version 2.24

virnbdbackup:

• Add option --no-sparse-detection (#263): The feature implemented as
  with version 2.21 requires to query the complete base:allocation
  bitmap during incremental backup.
  Depending on the Hypervisor hardware and the virtual machine disk size,
  querying the base:allocation bitmap may take longer than to simply treat
  fstrimmed blocks the same way as changed blocks and include them in the
  backup.
  The option introduced can be used to disable the new behavior and can
  enhance backup times for specific users.

See also:

https://github.com/abbbi/virtnbdbackup?tab=readme-ov-file#fstrim-and-incremental-backup-sizes

Full Changelog: v2.23...v2.24

Version 2.23

Version 2.23

virtnbdbackup:

• Log created nbd socket information in URI format, so it can be re-used with external tools more easily.
• Add human readable backup sizes in log output.

Full Changelog: v2.22...v2.23

Version 2.22

Version 2.22

• Test enhancements:
  • check btrfs filesystem stats in restored VM.
  • run checksum verify after all backups.
• virtnbdbackup:
  • If NBD connection drops, catch correct exception. (#254)
  • Provide better error message if checkpoint inconsistency is detected.

Full Changelog: v2.21...v2.22

Version 2.21

Version 2.21

virtnbdbackup: Detect dirty regions containing only zeroes during
incremental backup (fstrim) (#250)

Before, any dirty block being part of the incremental/differential bitmap
would be backed up, even if not required. Thanks to the input and
enhancements by

Roman Grigoriev (grigoriev177 at gmail.com) and
Denis V. Lunev (den at openvz.org)

the zeroed block regions are now compared to the base:allocation
bitmap and detected as such.

This reduces the amount of data backed up if virtual machines have disks
configured with discard=unmap option and use fstrim to free unused space.

Full Changelog: v2.20...v2.21

Version 2.20

Version 2.20

• virtnbdmap: add option -H for better debugging, code cleanup
• virtnbdmap: fix situations where multiple blocks in row are required to map the correct data.

Full Changelog: v2.19...v2.20

Version 2.19

Version 2.19

• virtnbdmap sometimes fails to correctly map disk images due to
  block offsets spanning multiple frames in the stream format, resulting in
  Input/Output errors accessing the disk partition data (#249)

Full Changelog: v2.18...v2.19

Version 2.18

Version 2.18

• If auto backup mode is switched to incremental and --raw option
  is passed, backup would fail instead of showing an warning that
  raw devices are excluded (#239)

Full Changelog: v2.17...v2.18

Version 2.17

Version 2.17

• Add rpm package build for fedora 41 (#234)
• virtnbdbackup: Remote backup fails if spaces exist in image path (#235)
• virtnbdrestore: Remote restore would fail if target path contains spaces.

Full Changelog: v2.16...v2.17

Version 2.16

Version 2.16

• virtnbdrestore: If domain with multiple disks is restored and config
  adjustment is requested, only the path to the last disk is updated. (#232).
  Thanks Richard Stephens for report and fix.
• virtnbdrestore: fix logic for adjusting the vm name

Full Changelog: v2.15...v2.16

Version 2.15

Version 2.15

• Update Dockerfile and README
• virtnbdrestore: use absolute path to disk files during local restore.
• virtnbdrestore: make absolute path mandatory for remote restore.

Full Changelog: v2.14...v2.15