Version 2.33

Version 2.33

virtnbdrestore: Add support for data-file setting in qcow images (#261)

As with versions (>= v10.10.0), libvirt supports the qcow image data-file
setting. This allows to create metadata QCOW Images for RAW disk images or
direct attached LVM/ZFS/RBD volumes.

Bitmaps are then stored within the metadata QCOW image, allowing to create
incremental backups for these disks, too.

During restore, the QCOW image must be created with the correct data-file
setting and the virtual machine configuration must be adopted. The utility
will now adjust paths accordingly if -c option is specified.

See README for details on how to configure your virtual machine to support
incremental backups with RAW devices.

Full Changelog: v2.32...v2.33

Version 2.32

Version 2.32

• virtnbdrestore: handle exception if files in the backup folder are missing,
  show warning instead (#277)

Full Changelog: v2.31...v2.32

Version 2.31

Version 2.31

• virtnbdrestore: remove raw devices from xml config only if option --raw
  is not specified (#276)

Full Changelog: v2.30...v2.31

Version 2.30

Version 2.30

• handle lost CBT case by @dlunev in #272: virtnbdbackup will now issue a warning and fallback to an full backup, in case it detects any checkpoint/bitmap inconsistencies, instead of aborting the current incremental or differential backup.

Full Changelog: v2.29...v2.30

Version 2.29

Version 2.29

• virtnbdrestore: wrong vm config XML used if until option is used (#270)

Full Changelog: v2.28...v2.29

Version 2.28

Version 2.28

• virtnbdbackup:
  • improve overlap() performance. The call should be O(L) complexity (#265) ( @dlunev)

Full Changelog: v2.27...v2.28

Version 2.27

Version 2.27

• virtnbdbackup: Skip saving checksum information for raw images included with --raw option:
  The checksum calculated does not actually match during verify because certain
  parts of the images may be seeked instead of actually written. (#269)

Full Changelog: v2.26...v2.27

Version 2.26

Version 2.26

virtnbdbackup:

• Add info log message before and after extent query has finished.
• Enhance function to detect sparse/fstrimmed regions (#263).
• Enhance CI tests

Full Changelog: v2.25...v2.26

Version 2.25

Version 2.25

Detect QCOW2 formatted direct attached RAW Volumes (#264):

Some solutions such as OpenNebula will use direct attached LVM volumes in
virtual machines. These LVM volumes were treated like a RAW device, but
allow all required operations for full/incremental backup, as they are qcow2
formatted.

Changes introduced in v2.18 would exclude these devices from backup even if
--raw option is passed. Now during disk detection, use the disk format in
the driver type setting to correctly detect a lvm volume backed by qcow2,
and handle them just like regular qcow based images.

Full Changelog: v2.24...v2.25

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