linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Phil Turmel <philip@turmel.org>
To: hansbkk@gmail.com
Cc: Nataraj <incoming-centos@rjl.com>,
	linux-raid@vger.kernel.org, linux-lvm@redhat.com
Subject: Re: [linux-lvm] Q: LVM over RAID, or plain disks? A:"Yes" = best of both worlds?
Date: Tue, 30 Nov 2010 08:13:00 -0500	[thread overview]
Message-ID: <4CF4F85C.1020806@turmel.org> (raw)
In-Reply-To: <AANLkTing5ApAXM2o0M+pxNvg01mHewNgGGBiUXM3aLzZ@mail.gmail.com>

Hi Hans, (?)

On 11/30/2010 02:34 AM, hansbkk@gmail.com wrote:
> On Tue, Nov 30, 2010 at 2:14 PM, Nataraj <incoming-centos@rjl.com> wrote:
>>> TopRAID1's LVM is likely to be running over a RAID6 set , so I'm not
>>> depending on the TopRAID mirroring for reliability, just using it for
>>> the above volume cloning.
>>
>> Your raid 1 backups won't mirror any snapshots of your LV's unless you
>> specifically setup mirroring of the snapshots after they exist.
> 
> Ah, getting clearer to me, I was thinking I'd be mirroring the LV
> itself, but you're right, taking a snapshot and mirroring that is a
> much better idea.

I think you are making this overly complex, insisting on a RAID1 operation to backup from on filer to the other.  Consider having each disk on filer #2 configured as a single LVM PV/VG, so it can stand alone in a rotation.  The try the alternate below.

> So here's a summary of steps, please confirm:
>   - create a snapshot of a given volume

Here's where you are over-complicating things:
>   - create a new RAID1 mdN between that and a physical partition (blank?)
>   - let that get sync'd up
>   - break the RAID (fail the partition?), remove the drive

As an alternate, with simpler recovery semantics:
  Create matching LV on non-RAID PV/VG on filer #2
  dd + netcat + dd or other technique to dup the snapshot on filer #1 to filer #2

>   - delete the snapshot

Now, you have a single disk in your backup set that can be mounted on either filer, and either copied back into service, or in an emergency, used directly (live) in filer #1.

This approach also gives you the *option* to implement the backup transfer with file system conversions, compression, free space removal, or any other administrative adjustments you need.  A RAID mirror can only duplicate the raw block device.

HTH,

Phil

  reply	other threads:[~2010-11-30 13:13 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-28 15:30 Q: LVM over RAID, or plain disks? A:"Yes" = best of both worlds? hansbkk
2010-11-28 18:34 ` Leslie Rhorer
2010-11-29 11:01   ` hansbkk
2010-11-29 15:29     ` Keld Jørn Simonsen
2010-11-29 16:00       ` hansbkk
2010-11-30  0:42         ` Neil Brown
2010-11-30  5:35           ` hansbkk
2010-11-30  6:47             ` Neil Brown
     [not found] ` <AANLkTimGkMJGiJC+7L+Pu3+yf-J_s0Ex3hM2-g-0+UqQ@mail.gmail.com>
     [not found]   ` <4CF3F7A0.2080108@rjl.com>
2010-11-30  5:20     ` [linux-lvm] Q: " hansbkk
     [not found]       ` <4CF4A472.20107@rjl.com>
2010-11-30  7:34         ` hansbkk
2010-11-30 13:13           ` Phil Turmel [this message]
2010-11-30 15:39             ` hansbkk
2010-11-30 16:56               ` Phil Turmel
2010-12-01  4:45                 ` hansbkk
2010-12-01 12:50                   ` Phil Turmel
2010-12-01 19:47                     ` hansbkk

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=4CF4F85C.1020806@turmel.org \
    --to=philip@turmel.org \
    --cc=hansbkk@gmail.com \
    --cc=incoming-centos@rjl.com \
    --cc=linux-lvm@redhat.com \
    --cc=linux-raid@vger.kernel.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).