libvirt 7.2.0 domainbackup
Peter Krempa
pkrempa at redhat.com
Mon Apr 12 06:28:15 UTC 2021
On Thu, Apr 08, 2021 at 15:53:14 +0200, Thomas Stein wrote:
> Cool! So just to be clear, if I start the backup at 1400 and it's finished at 1410, changes to the image at 1405 are not included?
Yes, exactly.
> It's the same quality as my current backup solution then. Thank you for your answer Peter.
If you do full backups (create just 1 overlay, copy over the full
original image, merge the 1 overlay back) then yes. If you were doing an
"incremental" backup (2 overlays when backing up, 1 overlay in normal
use) then that is not yet supported. The code for incremental backups
via 'virsh backup-begin' exists in libvirt but qemu doesn't yet support
the 'blockdev-reopen' command which is used by the incremental backup
code.
>
> cheers, t.
>
> Am 8. April 2021 15:46:56 MESZ schrieb Peter Krempa <pkrempa at redhat.com>:
> >On Wed, Apr 07, 2021 at 19:46:54 +0200, Thomas Stein wrote:
> >>
> >> Got a little bit further. "virsh backup-begin jitsi jitsi-backup.xml"
> >works
> >> and I have a backup file now. VM was running all the time. Question.
> >Is it
> >> save to use this function this way? Currently I do:
> >
> >The backup file you'll get will represent the state of the VM at the
> >time the backup operation has started, but should contain a full copy
> >of
> >the image from that time.
>
>
More information about the libvirt-users
mailing list