Not able to backup a running VM #126
-
Version used Describe the bug
Directory - If I then run a full backup i get the following error Contradicting the first error. Running libvirtd - libvirtd (libvirt) 9.0.0 Expected behavior Hypervisor information:
Logfiles: Workaround: |
Beta Was this translation helpful? Give feedback.
Replies: 7 comments
-
hi, this looks strange to me, the backup folder includes a type copy backup, which cant be used as base
so there was in fact a copy backup executed instead of a full backup. I would need the log from the first backup I guess the virtual machine was offline (powered off) during the first backup, then the backup mode "auto" did If the folder already includes an copy backup, no inc or full backups can be executed on this folder anymore, so this |
Beta Was this translation helpful? Give feedback.
-
Hi there , Upgraded to - virtnbdbackup -V 1.9.36 Replicate Issue
Expected : On first run into a empty folder in auto to be a fullcopy |
Beta Was this translation helpful? Give feedback.
-
hi, the behavior is expected if the virtual machine is offline like it was in your case. You attempted an auto mode backup
if a virtual machine is offline no full backup can be created because we cannot add an checkpoint for a full backup So you have to make sure virtual machine is online if you want the auto backup mode to create a full backup See the Notes section in: https://github.com/abbbi/virtnbdbackup#backup-operation [..] If the virtual domain is not in running state (powered off) virtnbdbackup supports copy and inc/diff backup modes. Incremental and differential backups will then save the changed blocks since last created checkpoint. As no new checkpoints can be defined for offline domains, the Backup mode full is changed to mode copy. |
Beta Was this translation helpful? Give feedback.
-
Hi , sudo virtnbdbackup -d terraform-jenkins-1 -l auto -o /media/rob/KvmBackups/MonthlyBackups/Jenkins -v |
Beta Was this translation helpful? Give feedback.
-
your qcow image files are too old, they still use the old v2 format. See also: |
Beta Was this translation helpful? Give feedback.
-
Hi ,
Please can you re-open issue .
Many thanks
Rob
… On 14 Aug 2023, at 09:43, Michael Ablassmeier ***@***.***> wrote:
Can't make bitmap 'virtnbdbackup.0' persistent in 'libvirt-1-format': Cannot store dirty bitmaps in qcow2 v2 files+
your qcow image files are too old, they still use the old v2 format.
For persistent bitmaps, you need to convert them to v3 format using qemu-img.
See also:
https://github.com/abbbi/virtnbdbackup#backup-fails-with-cannot-store-dirty-bitmaps-in-qcow2-v2-files <https://github.com/abbbi/virtnbdbackup#backup-fails-with-cannot-store-dirty-bitmaps-in-qcow2-v2-files>
—
Reply to this email directly, view it on GitHub <#125 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AHZR7OOVONAXNGAY3CLHJE3XVHQL7ANCNFSM6AAAAAA3OHNL7M>.
You are receiving this because you modified the open/close state.
|
Beta Was this translation helpful? Give feedback.
-
hi, its not an issue in virtnbdbackup, you have to adjust your image files qcow version using qemu-img like |
Beta Was this translation helpful? Give feedback.
hi,
its not an issue in virtnbdbackup, you have to adjust your image files qcow version using qemu-img like
described in the README. Ive converted this into an discussion.