So to archive my goal to have an zstd compressed backup image,
i can currently not use the new approach with backup-begin ?
Instead i have to use the old approach with the overlay file and use qemu-img
convert compression_type=zstd ...
for doing the backup and if finished blockcommit the overlay
one more ...
what would happen, if i create the qcow2 image with zstd compression enabled and
use the '--reuse-external' flag ?
Would qemu write compressed data in it or not ?
Hi together,
actually i only do full-backup's of my virtual machines.
I use the for the backup the "old" strategy:
- virsh snapshot-create-as $vmname overlay --disk-only --atomic --no-metadata
--quiesce
- copy the qcow2 image file
- virsh blockcommit $vmname $device --active --wait --pivot
- the
ok, so only setting the compression type to zstd in the backupxml would be
possible from libvirt, right ?
An implementation only in the backup job would be great, that would fit my
needs.
Maybe some more flags in the backupxml file would be useful. I used for
compressing
on the zstd call
"--sparse --rsyncable -B128 "
as the files are later transfered with rsync. The compression level would also
b
Hi,
currently i use on all VM's qcow2-Images with zlib compression. If i do an
Backup, the Backup-Image will
be compressed with zstd Level 3 to shrink the image for transfering it over not
so fast internet connections.
So, why not directly using zstd compression on the images. Are there any
re
Ok, just to be sure, that i understand it right:
To be consistent on backup i have to do an:
- virsh domfsfreeze $vmname
- virsh backup-begin $vmname
- virsh domfsthaw $vmname
Do i have to wait for the "virsh domfsthaw $vmname" until the backup is
finished or
just after the "backup-begin" ?
many thanks again for your help
now, i am ready for switching ;-)
One additional question ...
if i have same snapshots in a vm, the "backup-begin" do only an backup of the
currently running snapshot, right ?
