From: Jd <jd_jedi@convirture.com>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] Dirty block tracking : External file
Date: Tue, 28 Oct 2014 09:52:55 -0700 [thread overview]
Message-ID: <544FC9E7.50205@convirture.com> (raw)
Hi
We are looking for dirty block tracking feature in qemu/kvm for
implementing more efficient incremental backup. I saw some patches
around it, but from the conversation could not figure out if it is
complete or not. If it is complete, can some one point to the branch /
label from which I can get it.
Could of questions around the feature.
* Does this work with qcow format only ? Or for any format ? Can I
use it with ceph, gluster, etc,,etc.
* How does dirty block tracking to file get affected by snapshots
? One would assume that it would mark all the blocks changed since
tracking begun, irrespective of snapshots pull / rebase....etc. This way
one might copy more blocks than necessary, but is accurate. And this
allows the user to do different snapshot operations irrespective of
backups which is a big thing from users perspective.
Thanks
/Jd
next reply other threads:[~2014-10-28 16:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-28 16:52 Jd [this message]
2014-10-29 1:08 ` [Qemu-devel] Dirty block tracking : External file Fam Zheng
2014-10-29 14:17 ` Stefan Hajnoczi
2014-10-29 14:17 ` Stefan Hajnoczi
2014-10-29 14:17 ` Stefan Hajnoczi
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=544FC9E7.50205@convirture.com \
--to=jd_jedi@convirture.com \
--cc=qemu-devel@nongnu.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.