qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Ricardo Almeida" <ric.almeida@gmail.com>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Online image backup
Date: Wed, 5 Dec 2007 21:25:03 +0000	[thread overview]
Message-ID: <8a6cde920712051325n193c5166m60e1c3135f1e23a1@mail.gmail.com> (raw)
In-Reply-To: <4756B1DD.4040009@develer.com>

Hi,

Discalmer: I'm just a user of QEmu :) <comments bellow>

> 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

>   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

>   4. ...repeat for all running VMs.
>

[...]

> The weak spot of this configuration is the third step of backup: if you
> perform an online copy (and that's your only real choice, since you
> don't want to powerdown the VMs every night just to backup them), you
> are copying a file while it's always modifying, and chances are high
> that the copy will be corrupted (i.e. different from any state the
> original went through), since you can't perform the copy with a single read.

See the above added steps :)
Is this a bad idea?

Regards and keep up the good work :),
Ricardo Almeida

  reply	other threads:[~2007-12-05 21:25 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-12-05 14:12 [Qemu-devel] Online image backup Lorenzo Mancini
2007-12-05 21:25 ` Ricardo Almeida [this message]
2007-12-10 10:45   ` Lorenzo Mancini
2007-12-10 17:41     ` Ricardo Almeida
  -- strict thread matches above, loose matches on Subject: below --
2007-11-20 11:23 Matteo Bertini
2007-11-20 23:02 ` Fabrice Bellard

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=8a6cde920712051325n193c5166m60e1c3135f1e23a1@mail.gmail.com \
    --to=ric.almeida@gmail.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 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).