From: "Brian J. Murrell" <brian@interlinx.bc.ca>
To: LVM general discussion and development <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] Using LVM Mirroring to obtain a usable backup
Date: Wed, 16 Sep 2009 12:58:42 -0400 [thread overview]
Message-ID: <1253120322.16343.71.camel@pc.interlinx.bc.ca> (raw)
In-Reply-To: <1253119669.5326.32.camel@delo.gdit>
[-- Attachment #1: Type: text/plain, Size: 1428 bytes --]
On Wed, 2009-09-16 at 18:47 +0200, Ambrogio De Lorenzo wrote:
>
> snapshot is not a good choise for me.
It actually is. I snapshot all of my filesystems before every upgrade
and let the snapshots hang around until I am happy with the upgrade.
> I want to have an identical copy
> (like dd) on another identical disk, for fast recovery in case of
> failure.
Well, snapshots give you a very space efficient (if not performance
efficient due to the COW nature of snapshots) version of that. When you
create a snapshot and before your modify any data in the origin (the
volume you are creating a snapshot (a.k.a. copy) of your snapshot is an
identical copy (just as if you'd used dd) of the origin, without using
any additional space even!
You can go on to upgrading the origin and the snapshot will continue to
maintain the "copy" of the origin at the time the snapshot was created.
It's sweet.
> This is what I do with raid hardware, and I would like to know if is
> possible to do it with lvm mirroring.
I've never used LVM mirroring. Certainly you can do this with Linux's
MD software mirroring, but why bother when snapshots are so much easier?
> I'm looking also on mdadm to mirror a disk (or partition) but I think it
> is not usable when disk is already partitioned and used without mdadm.
Well, you will have that same problem with LVM. Planning is key in any
of this.
b.
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 197 bytes --]
next prev parent reply other threads:[~2009-09-16 17:48 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-16 13:59 [linux-lvm] Using LVM Mirroring to obtain a usable backup Ambrogio De Lorenzo
2009-09-16 15:05 ` André Gillibert
2009-09-16 16:47 ` Ambrogio De Lorenzo
2009-09-16 16:58 ` Brian J. Murrell [this message]
2009-09-16 19:15 ` Ambrogio De Lorenzo
2009-09-16 19:49 ` Brian J. Murrell
2009-09-16 20:03 ` André Gillibert
2009-09-16 20:22 ` Ambrogio De Lorenzo
2009-09-16 22:03 ` Kai Stian Olstad
2009-09-16 18:19 ` malahal
2009-09-16 19:03 ` Ambrogio De Lorenzo
2009-09-16 20:33 ` malahal
2009-09-17 10:05 ` Bryn M. Reeves
2009-09-17 15:06 ` Stuart D. Gathman
2009-09-17 15:34 ` Brian J. Murrell
2009-09-17 22:49 ` Stuart D. Gathman
2009-09-17 23:26 ` Les Mikesell
2009-09-18 0:58 ` Stuart D. Gathman
2009-09-18 1:51 ` Sven Eschenberg
2009-09-18 16:05 ` Mark H. Wood
2009-09-18 19:12 ` Stuart D. Gathman
2009-09-17 23:48 ` Brian J. Murrell
2009-09-18 1:55 ` Stuart D. Gathman
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=1253120322.16343.71.camel@pc.interlinx.bc.ca \
--to=brian@interlinx.bc.ca \
--cc=linux-lvm@redhat.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.