Skip to content

Releases: abbbi/virtnbdbackup

Version 2.44

18 Jan 10:32

Choose a tag to compare

Version 2.44

  • Remote backup fails: "unsupported flags (0x2) in function qemuBackupBegin":
    If system executing virtnbdbackup ships newer libvirt library version than
    remote system, VIR_DOMAIN_BACKUP_BEGIN_PRESERVE_SHUTDOWN_DOMAIN flag was
    added even if not yet supported by the remote system. Now flags are only
    activated if remote system is running on a version supporting the flags, too.
    (#298)
  • Enhance logging: log both local and remote libvirt versions.

Full Changelog: v2.43...v2.44

Version 2.43

04 Jan 10:51

Choose a tag to compare

Version 2.43

  • Small code cleanups
  • Fix got an unexpected keyword argument 'stacklevel' issue on older
    distributions (#297)

Full Changelog: v2.42...v2.43

Version 2.42

10 Dec 20:57

Choose a tag to compare

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

10 Dec 08:29

Choose a tag to compare

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

03 Dec 09:11

Choose a tag to compare

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

10 Nov 12:59
2cbd4dc

Choose a tag to compare

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

10 Oct 06:01

Choose a tag to compare

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

26 Sep 13:01

Choose a tag to compare

Version 2.37

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

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

Version 2.36

25 Sep 19:00

Choose a tag to compare

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

13 Sep 15:38

Choose a tag to compare

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)