Version 2.42

• virtnbdrestore: add --compress option: if enabled, NBD server used for
  restore will make use of the qcow compression driver. This way, restored
  data within the qcow image is compressed according to the image compression
  type setting. This will be beneficial for images that contained many compressed blocks, as
  the restored images will be way smaller. (#295)

Full Changelog: v2.41...v2.42

Version 2.41

• Disable building rust bindings when creating venv (#293)
• Small code cleanups
• Use tqdm logging_redirect_tqdm to not break progress bars (#294)

Full Changelog: v2.40...v2.41

Version 2.40

• Add OpenSUSE 16 to build scripts
• Use trixie for docker container
• venv/create.sh fails to successfully build libnbd without python setuptools
  (#290)
• Add support for VIR_DOMAIN_BACKUP_BEGIN_PRESERVE_SHUTDOWN_DOMAIN: As with
  libvirt version 11.10, this flag prevents VM shutdown while an backup job is
  still active. The VM is in that scenario reset and paused instead of
  terminated allowing the backup to finish. Once the backup finishes the VM
  process is terminated. See: https://libvirt.org/kbase/live_full_disk_backup.html#shutdown-of-the-guest-os-during-backup

Full Changelog: v2.39...v2.40

Version 2.39

• Add fedora 42 to build scripts.
• Gracefully handle network attached disk devices, show error message and
  hint (#286)

Full Changelog: v2.38...v2.39

Version 2.38

[Francisco Javier]

• virtnbdbackup: reuse existing sftp connections during backup. (#283)

[Michael Ablassmeier]

• virtnbdmap: replaying changes may fail with "[Errno 22] Invalid argument":
  the NBD device sometimes needs some time to settle, wait until it is seekable
  to the end of the block list instead of failing.
• virtnbdbackup: During full backup, all old checkpoints are removed.
  Sometimes there might be situations where bitmaps are not existent anymore.
  Now, during full backup, checkpoint consistency is validated prior to
  removal, and checkpoints tied to non-existent bitmaps will be removed with
  VIR_DOMAIN_CHECKPOINT_DELETE_METADATA_ONLY flags enabled, to allow flawless
  full backups. The utility will issue WARNINGS in this case.

See discussion (#285)

Full Changelog: v2.37...v2.38

Version 2.37

• Add missing nbdkit and python plugin to docker container image. (#282)

Full Changelog: v2.36...v2.37

Version 2.36

• virtnbdbackup: add --pause option: Suspend and resume virtual machine
  while starting backup job. This can be useful for virtual machines where
  freezing file systems using the qemu guest agent is not possible.

Full Changelog: v2.35...v2.36

Version 2.35

• virtnbdrestore: fix restore issue in case virtual machine is using
  volume based disk configuration: the restore process attempted to identify
  the volumes which do not exist anymore. Adjust virtual machine config and
  reset the volume base setting to a file based notation. (#280)

Version 2.34

• virtnbdbackup: show hint about virtual machine config adjustment
  possibility in case raw devices are attached.
• virtnbdrestore: do not show warning if no data-file setting is found in
  qcow json file.
• Add RHEL10 RPM build to github workflow
• Do not make vm6.tests fail if /tmp/datafile.raw is missing.

Full Changelog: v2.33...v2.34

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 devices and
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