Re: best backup strategy for full backup's
many thanks again for your help now, i am ready for switching ;-)
Re: best backup strategy for full backup's
On Mon, Mar 10, 2025 at 11:48:58 -, Michael Niehren wrote: > One additional question ... > > if i have same snapshots in a vm, the "backup-begin" do only an backup of the > currently running snapshot, right ? The backup job always backs-up only the current guest-visible state of the disks. Technically a snapshot is a point-in-time in the past you might want to return to. The state represented by the snapshot is thus different from what you are backing up. With external snapshots the backup will be identical as if you merged in all the layers created by the snapshots.
Re: best backup strategy for full backup's
One additional question ... if i have same snapshots in a vm, the "backup-begin" do only an backup of the currently running snapshot, right ?
Re: best backup strategy for full backup's
On Mon, Mar 10, 2025 at 11:27:40 -, Michael Niehren wrote: > 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" ? No you can issue 'domfsthaw' right when 'backup-begin' finishes. The backup image contains data from the point in time when the backup job *started* irrelevant how long it takes. qemu ensures that all blocks that would be overwritten by the guest are first copied to the backup image before overwriting them in the disk image.
