qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Paolo Bonzini <pbonzini@redhat.com>
To: Zhang Haoyu <zhanghy@sangfor.com.cn>,
	qemu-devel <qemu-devel@nongnu.org>, kvm <kvm@vger.kernel.org>
Cc: Fam Zheng <famz@redhat.com>, Stefan Hajnoczi <stefanha@redhat.com>
Subject: Re: [Qemu-devel] [question] incremental backup a running vm
Date: Wed, 21 Jan 2015 11:39:44 +0100	[thread overview]
Message-ID: <54BF81F0.9070908@redhat.com> (raw)
In-Reply-To: <201501211832330964659@sangfor.com.cn>



On 21/01/2015 11:32, Zhang Haoyu wrote:
> Hi,
> 
> Does drive_mirror support incremental backup a running vm?
> Or other mechanism does?
> 
> incremental backup a running vm requirements:
> First time backup, all of the allocated data will be mirrored to destination,
> then a copied bitmap will be saved to a file, then the bitmap file will log dirty for
> the changed data.
> Next time backup, only the dirty data will be mirrored to destination.
> Even the VM shutdown and start after several days,
> the bitmap will be loaded while starting vm.
> Any ideas?

Drive-mirror is for storage migration.  For backup there is another job,
drive-backup.  drive-backup copies a point-in-time snapshot of one or
more disks corresponding to when the backup was started.

Incremental backup is being worked on.  You can see patches on the list.

Paolo

  reply	other threads:[~2015-01-21 10:39 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 [this message]
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
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=54BF81F0.9070908@redhat.com \
    --to=pbonzini@redhat.com \
    --cc=famz@redhat.com \
    --cc=kvm@vger.kernel.org \
    --cc=qemu-devel@nongnu.org \
    --cc=stefanha@redhat.com \
    --cc=zhanghy@sangfor.com.cn \
    /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).