From: "Zhang Haoyu" <zhanghy@sangfor.com.cn>
To: Paolo Bonzini <pbonzini@redhat.com>,
Kashyap Chamarthy <kashyapc@fedoraproject.org>
Cc: Fam Zheng <famz@redhat.com>,
Stefan Hajnoczi <stefanha@redhat.com>,
qemu-devel <qemu-devel@nongnu.org>, kvm <kvm@vger.kernel.org>
Subject: Re: [Qemu-devel] [question] incremental backup a running vm
Date: Mon, 26 Jan 2015 20:25:06 +0800 [thread overview]
Message-ID: <201501262024561264834@sangfor.com.cn> (raw)
In-Reply-To: 54C624E2.2010608@redhat.com
On 2015-01-26 19:29:03, Paolo Bonzini wrote:
>
> On 26/01/2015 12:13, Zhang Haoyu wrote:
> > Thanks, Paolo,
> > but too many internal snapshots were saved by customers,
>> switching to external snapshot mechanism has significant impaction
> > on subsequent upgrade.
>
> In that case, patches are welcome. :)
>
> > Another problem:
> > drive_backup just implement one time backup,
> > but I want VMWare's VDP-like backup mechanism.
> > The initial backup of a virtual machine takes comparatively more time,
>> because all of the data for that virtual machine is being backed up.
> > Subsequent backups of the same virtual machine take less time, because
> > changed block tracking (log dirty) mechanism is used to only backup the dirty data.
> > After inittial backup done, even the VM shutdown, but subsequent backup also only
>> copy the changed data.
>
> As mentioned before, patches for this are on the list.
>
I see, thanks, Paolo.
> Paolo
next prev parent reply other threads:[~2015-01-26 12:34 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-21 10:32 [Qemu-devel] [question] incremental backup a running vm Zhang Haoyu
2015-01-21 10:39 ` Paolo Bonzini
2015-01-22 23:29 ` Kashyap Chamarthy
2015-01-26 1:07 ` Zhang Haoyu
2015-01-26 9:29 ` Paolo Bonzini
2015-01-26 11:13 ` Zhang Haoyu
2015-01-26 11:28 ` Paolo Bonzini
2015-01-26 12:25 ` Zhang Haoyu [this message]
2015-01-23 11:09 ` Kashyap Chamarthy
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=201501262024561264834@sangfor.com.cn \
--to=zhanghy@sangfor.com.cn \
--cc=famz@redhat.com \
--cc=kashyapc@fedoraproject.org \
--cc=kvm@vger.kernel.org \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).