From: Fam Zheng <famz@redhat.com>
To: John Snow <jsnow@redhat.com>
Cc: Qemu-block <qemu-block@nongnu.org>,
qemu-devel <qemu-devel@nongnu.org>,
Vladimir Sementsov-Ogievskiy <vsementsov@parallels.com>,
Stefan Hajnoczi <stefanha@redhat.com>,
"Denis V. Lunev" <den@openvz.org>
Subject: Re: [Qemu-devel] RFC: incremental backups: qmp-block-dirty-bitmap-diff
Date: Sun, 14 Feb 2016 16:02:32 +0800 [thread overview]
Message-ID: <20160214080232.GE31933@ad.usersys.redhat.com> (raw)
In-Reply-To: <56BA88E7.7010104@redhat.com>
On Tue, 02/09 19:48, John Snow wrote:
> - Reading an entire drive to populate a bitmap with the understanding
> that an incremental backup is soon to follow is inefficient if the drive
> is more than just a little dirty: it may have been quicker to just
> create a new full backup and bitmap.
Above all I think this is a good idea. Just as an alternative, can we add
another sync mode for drive-backup?
(QMP) drive-backup device=d0 target=target.qcow2 format=qcow2 sync=diff \
base=full-backup.qcow2
(the data of d0 will be compared against full-backup.qcow2 and only different
clusters will be copied to target.qcow2)
Fam
next prev parent reply other threads:[~2016-02-14 8:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-10 0:48 [Qemu-devel] RFC: incremental backups: qmp-block-dirty-bitmap-diff John Snow
2016-02-14 8:02 ` Fam Zheng [this message]
2016-02-22 22:48 ` John Snow
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=20160214080232.GE31933@ad.usersys.redhat.com \
--to=famz@redhat.com \
--cc=den@openvz.org \
--cc=jsnow@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@redhat.com \
--cc=vsementsov@parallels.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).