IMHO it is still not clear that this provides snapshot semantics ... (snapshot of the stopped VM).
> On November 21, 2017 at 11:41 AM Emmanuel Kasper <e.kas...@proxmox.com> wrote: > > > The VM goes to normal operation after the backup is started, not at end of > backup. > > Signed-off-by: Emmanuel Kasper <e.kas...@proxmox.com> > --- > vzdump.adoc | 7 +++++-- > 1 file changed, 5 insertions(+), 2 deletions(-) > > diff --git a/vzdump.adoc b/vzdump.adoc > index 7643ec6..d354732 100644 > --- a/vzdump.adoc > +++ b/vzdump.adoc > @@ -64,8 +64,11 @@ depending on the guest type. > This mode provides the highest consistency of the backup, at the cost > of a downtime in the VM operation. It works by executing an orderly > shutdown of the VM, and then runs a background Qemu process to backup > -the VM data. After the backup is complete, the Qemu process resumes > -the VM to full operation mode if it was previously running. > +the VM data. After the backup is started, the VM goes to full > +operation mode if it was previously running. + > +By starting the backup background process when the VM is shut down, we > +make sure that no pending writes are contained in the VM page cache when we > +start the backup, thus ensuring consistency of the backup data. > > `suspend` mode:: > > -- > 2.11.0 > > > _______________________________________________ > pve-devel mailing list > pve-devel@pve.proxmox.com > https://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel _______________________________________________ pve-devel mailing list pve-devel@pve.proxmox.com https://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
