From mboxrd@z Thu Jan 1 00:00:00 1970 From: Paolo Bonzini Subject: Re: [question] incremental backup a running vm Date: Mon, 26 Jan 2015 12:28:34 +0100 Message-ID: <54C624E2.2010608@redhat.com> References: <201501211832330964659@sangfor.com.cn>, <54BF81F0.9070908@redhat.com>, <20150122232948.GQ12638@tesla.redhat.com>, <201501260907583380898@sangfor.com.cn> <201501261913435951960@sangfor.com.cn> Mime-Version: 1.0 Content-Type: text/plain; charset=gbk Content-Transfer-Encoding: 7bit Cc: qemu-devel , kvm , Stefan Hajnoczi , Fam Zheng To: Zhang Haoyu , Kashyap Chamarthy Return-path: Received: from mail-wi0-f171.google.com ([209.85.212.171]:33507 "EHLO mail-wi0-f171.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751208AbbAZL2j (ORCPT ); Mon, 26 Jan 2015 06:28:39 -0500 Received: by mail-wi0-f171.google.com with SMTP id l15so9180096wiw.4 for ; Mon, 26 Jan 2015 03:28:38 -0800 (PST) In-Reply-To: <201501261913435951960@sangfor.com.cn> Sender: kvm-owner@vger.kernel.org List-ID: 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. Paolo