From: Lukas Laukamp <lukas@laukamp.me>
To: Javier Guerra Giraldez <javier@guerrag.com>
Cc: Stefan Hajnoczi <stefanha@gmail.com>, kvm@vger.kernel.org
Subject: Re: [User Question] How to create a backup of an LVM based maschine without wasting space
Date: Sat, 13 Oct 2012 12:28:18 +0200 [thread overview]
Message-ID: <50794242.3020407@laukamp.me> (raw)
In-Reply-To: <CAFkDaoTDcPnngc5HQWYe+E=hothmOB2TVeuT4X3Q+B7pA5TB-g@mail.gmail.com>
Am 12.10.2012 23:53, schrieb Javier Guerra Giraldez:
> On Fri, Oct 12, 2012 at 3:56 PM, Lukas Laukamp <lukas@laukamp.me> wrote:
>> I think that it must be possible to create an image with a size like the
>> used space + a few hundret MB with metadata or something like that.
> the 'best' way to do it is 'from within' the VM
>
> the typical workaround is to mount/fsck a LVM snapshot (don't skip the
> fsck, or at least a journal replay)
>
> beyond that, there are a few utilities for specific filesystems:
> PartImage [1], dump/restore [2], and i'm sure some others. I don't
> know how would these behave with unclean images, which is what you get
> if you pull the image under the VM's feet.
>
>
> [1] http://www.partimage.org/Main_Page
> [2] http://dump.sourceforge.net/
>
>
So when I boot the VM with for example a live debian system, what would
be the best method to backup the complete disk /dev/vda with only the
data which is on it over a secure network connection to a destination in
the network.
Best Regards
next prev parent reply other threads:[~2012-10-13 10:28 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-12 6:52 [User Question] How to create a backup of an LVM based maschine without wasting space Lukas Laukamp
2012-10-12 8:42 ` Stefan Hajnoczi
[not found] ` <5077DB9F.6050809@laukamp.me>
2012-10-12 9:17 ` Lukas Laukamp
2012-10-12 10:11 ` Stefan Hajnoczi
2012-10-12 10:16 ` Lukas Laukamp
2012-10-12 10:47 ` Stefan Hajnoczi
2012-10-12 10:50 ` Lukas Laukamp
2012-10-12 11:36 ` Stefan Hajnoczi
2012-10-12 11:51 ` Lukas Laukamp
2012-10-12 12:59 ` Stefan Hajnoczi
2012-10-12 13:02 ` Lukas Laukamp
2012-10-12 14:25 ` Stefan Hajnoczi
2012-10-12 14:36 ` Javier Guerra Giraldez
2012-10-12 15:51 ` Lukas Laukamp
2012-10-12 19:18 ` Stefan Hajnoczi
2012-10-12 18:14 ` Lukas Laukamp
2012-10-12 19:13 ` Stefan Hajnoczi
2012-10-12 19:26 ` Lukas Laukamp
2012-10-12 20:43 ` Stefan Hajnoczi
2012-10-12 20:56 ` Lukas Laukamp
2012-10-12 21:53 ` Javier Guerra Giraldez
2012-10-13 10:28 ` Lukas Laukamp [this message]
2012-10-13 22:25 ` Lukas Laukamp
2012-10-15 3:06 ` Javier Guerra Giraldez
2012-10-15 6:17 ` Lukas Laukamp
2012-10-18 12:57 ` Avi Kivity
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=50794242.3020407@laukamp.me \
--to=lukas@laukamp.me \
--cc=javier@guerrag.com \
--cc=kvm@vger.kernel.org \
--cc=stefanha@gmail.com \
/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.