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: Thu, 17 Sep 2009 11:34:14 -0400 [thread overview]
Message-ID: <1253201655.2339.178.camel@pc.interlinx.bc.ca> (raw)
In-Reply-To: <Pine.LNX.4.64.0909171044250.6368@bmsred.bmsi.com>
[-- Attachment #1: Type: text/plain, Size: 1970 bytes --]
On Thu, 2009-09-17 at 11:06 -0400, Stuart D. Gathman wrote:
> Using dd from a snapshot does not help the OP.
Right.
> He says the dd will take
> 5-6 hours, and he needs a backup of the system *just before* the upgrade,
> not hours before.
Which a snapshot will achieve.
> The rollback also needs to be quick.
Which a snapshot will achieve.
> A snapshot with dd does the "instant" backup part ok, but rollback
> requires 5-6 hours to copy the snapsnot to a normal LV.
Why would you copy the snapshot anywhere? If you decided you needed a
roll-back, you boot from the snapshot of the root filesystem and have
the /etc/fstab in that snapshot mount any snapshots of other filesystems
he might have made. Personally, I keep separate /, /usr, and /var and
so snapshot them all before an upgrade and fix up the /etc/fstab in the
snapshot-of-/ to mount the /usr and /var snapshots (rather than the
origins).
AFAICT, the only issue the OP has with snapshots is that he fears an
upgrade might screw up his LVM configuration. Personally, I think that
is a low-probability fear, but everyone has to have their own comfort
level I guess.
> The OP is correct that creating and breaking a RAID1 mirror does what
> he needs.
Indeed.
> I always build my VGs on md* devices.
I typically have not. I typically don't mirror anything except my
backup volume, which fully (as in bare metal restore able) backs up
every filesystem I have in my network. For that reason I feel that
mirroring the disks in all the machines is overkill.
But granted, building systems on broken mirrors is easy enough and
allows one the flexibility of mirroring at a later date if one wants.
In fact I always thought/felt, that given that the MD superblock is at
the end of a device (or partition), shrinking the filesystem on a
partition and then trying to create an MD mirror with that partition
should be doable. Never tried though.
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-17 15:34 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
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 [this message]
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=1253201655.2339.178.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox