From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from eggs.gnu.org ([2001:4830:134:3::10]:36552)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <jd_jedi@convirture.com>) id 1XjA1B-0005Q8-Dx
	for qemu-devel@nongnu.org; Tue, 28 Oct 2014 12:53:21 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <jd_jedi@convirture.com>) id 1XjA14-0005Tx-Db
	for qemu-devel@nongnu.org; Tue, 28 Oct 2014 12:53:13 -0400
Received: from gproxy2-pub.mail.unifiedlayer.com ([69.89.18.3]:41820)
	by eggs.gnu.org with smtp (Exim 4.71)
	(envelope-from <jd_jedi@convirture.com>) id 1XjA14-0005Tg-45
	for qemu-devel@nongnu.org; Tue, 28 Oct 2014 12:53:06 -0400
Received: from [107.3.157.240] (port=58324 helo=[192.168.15.208])
	by box899.bluehost.com with esmtpsa (TLSv1:DHE-RSA-AES128-SHA:128)
	(Exim 4.82) (envelope-from <jd_jedi@convirture.com>)
	id 1XjA0w-0001sw-T1
	for qemu-devel@nongnu.org; Tue, 28 Oct 2014 10:52:58 -0600
Message-ID: <544FC9E7.50205@convirture.com>
Date: Tue, 28 Oct 2014 09:52:55 -0700
From: Jd <jd_jedi@convirture.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: [Qemu-devel] Dirty block tracking : External file
List-Id: <qemu-devel.nongnu.org>
List-Unsubscribe: <https://lists.nongnu.org/mailman/options/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.nongnu.org/archive/html/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <https://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: qemu-devel@nongnu.org

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