From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1J1g8z-0007Dx-Fj for qemu-devel@nongnu.org; Mon, 10 Dec 2007 05:45:49 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1J1g8x-0007AM-E7 for qemu-devel@nongnu.org; Mon, 10 Dec 2007 05:45:48 -0500 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1J1g8x-0007A0-7g for qemu-devel@nongnu.org; Mon, 10 Dec 2007 05:45:47 -0500 Received: from trinity.develer.com ([89.97.188.34]) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1J1g8w-0001wp-NK for qemu-devel@nongnu.org; Mon, 10 Dec 2007 05:45:47 -0500 Message-ID: <475D18D3.7060109@develer.com> Date: Mon, 10 Dec 2007 11:45:39 +0100 From: Lorenzo Mancini MIME-Version: 1.0 Subject: Re: [Qemu-devel] Online image backup References: <4756B1DD.4040009@develer.com> <8a6cde920712051325n193c5166m60e1c3135f1e23a1@mail.gmail.com> In-Reply-To: <8a6cde920712051325n193c5166m60e1c3135f1e23a1@mail.gmail.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Reply-To: qemu-devel@nongnu.org List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: qemu-devel@nongnu.org Ricardo Almeida wrote: >> Fabrice, that's just part of the problem. A full automated remote >> backup service for qemu VMs should work like this: >> >> 1. send a "savevm state" command to qemu; >> 2. wait for savevm completion; > > 2.1 Switch to snapshot mode How do you switch to snapshot mode *while* the VM is running, i.e. without stopping and restarting qemu? The only way I know to enter that mode is using the -snapshot switch at invocation time and I don't think it can be done online. >> 3. perform an *online* copy (cp, rsync, whatever) of the .qcow2 image, >> while it's still running in qemu; > > 3.1 Pause VM > 3.2 Apply snapshot changes to local and remote copy (remote must be > running something that can apply the update) > 3.3 Back to normal mode If executing step 2.1 is actually possible, you can skip step 3.1 and 3.2 because the remote copy is already consistent with the state the VM went throught at the time of execution of step 2.1 . If it was possible, it would be just fine for automated daily backups. -- Lorenzo Mancini