Skip to content

Releases: abbbi/virtnbdbackup

Version 0.21

13 May 18:41
Compare
Choose a tag to compare
  • Add support for backup of raw disk images during full backup using option --raw:

Version 0.20

10 May 14:59
Compare
Choose a tag to compare
  • Add Support for backup of transient domains in cluster environments.
  • Update README

Version 0.19

01 May 19:17
Compare
Choose a tag to compare
  • If libvirthelper failed to setup backup job because of exception, an already freezed guest filesystem was not thawed.
  • Fix tests.

Version 0.18

30 Apr 08:56
Compare
Choose a tag to compare
  • During backup to stdout it was attempted to close non opened file handle resulting in backup error
  • Include used libnbd version in backup log
  • Fix some pylint warnings
  • Update README

Version 0.17

04 Apr 09:03
Compare
Choose a tag to compare
  • Remove sh module from requirements, obsoleted by subprocess module

Version 0.16

03 Apr 19:28
Compare
Choose a tag to compare
  • Code cleanup, fix pylint warnings
  • Update README

Version 0.15

02 Apr 19:33
Compare
Choose a tag to compare
  • Minor code changes, move some functions to common class
  • Use makedirs for targetfolder to support nested target pathes.
  • Updated README with more informations about backup workflow.

Version 0.14

30 Mar 20:59
Compare
Choose a tag to compare

Code cleanups
Change shebang so executables appear in process list with real name instead of python3 executable

Version 0.13

30 Mar 14:23
Compare
Choose a tag to compare

Write backup to partial file first

In case backup utility receives signal or fails otherwise,
the backup data is written to the regular target file and
it is assumed everything is OK.

Now virtnbdbackup writes the data to a partial file first
and renames the file as last step. During incremental
backup the target directory is checked for possible existance
of partial backups and backup is aborted with error.

Version 0.12

30 Mar 10:48
Compare
Choose a tag to compare
Using option -p and -l inc has also created an checkpoint

but did not save any data for it. As such, a user can
break its backup chain by trying to estimate the backup
size.

Enforce backup level copy if option -p is set, so no
checkpoint is created to ensure an consistent backup
chain.