public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Anders Karlsson <anders@trudheim.com>
To: Riley Williams <Riley@Williams.Name>
Cc: Clemens Schwaighofer <cs@tequila.co.jp>,
	LKML <linux-kernel@vger.kernel.org>
Subject: RE: Two RAID1 mirrors are faster than three
Date: 15 May 2003 11:51:14 +0100	[thread overview]
Message-ID: <1052995874.3248.20.camel@tor.trudheim.com> (raw)
In-Reply-To: <BKEGKPICNAKILKJKMHCACEECDAAA.Riley@Williams.Name>

[-- Attachment #1: Type: text/plain, Size: 1607 bytes --]

Hi Riley,

>  > With normal mirroring (one original, one copy) you do have the
>  > redundancy and the speed boost at reads, but at mirroring with one
>  > original and two copies (I know AIX does this), you get in to a
>  > scenario that is quite handy. Say you run a large database in a
>  > 24/7 operation. You want to back the database up, but you can only
>  > get 5-10 minutes downtime on it. You then quiesce the database,
>  > split off the second copy from the mirror, mount that as a
>  > separate file system and back that up while the original with its
>  > first copy has already stepped back into full use.
>  >
>  > Once you finished your backup, you add your split-off copy back to
>  > the original and primary copy and you are back where you started.
> 
> Does this cause any problems, with the third disc now being out of
> date compared to the first two?

No, it should not cause problems as when you add the split-off copy back
into the mirror, it is treated as 'stale' and will get synchronised with
the original. 

I would be very surprised if the Linux software md driver worked any
diffrently than this. Perhaps someone that knows it in-depth can add to
the conversation?

With the facilities of LVM 'snapshots' now being available, this
practice of splitting off one copy from a three-way mirror is perhaps
becoming redundant, but people will likely take the approach of "if it
ain't broken, don't fix it" and leave old backup methods as they are.
So if you work in the sysadm field, you might well come across this
practice.

Regards,

/Anders

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

  reply	other threads:[~2003-05-15 10:38 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-12  2:10 Two RAID1 mirrors are faster than three Chuck Ebbert
2003-05-12  4:35 ` Clemens Schwaighofer
2003-05-12  5:10   ` Anders Karlsson
2003-05-12  5:41     ` Paul P Komkoff Jr
2003-05-12  7:23       ` Anders Karlsson
2003-05-12  8:40     ` Clemens Schwaighofer
2003-05-12  9:30       ` [OT] " Anders Karlsson
2003-05-12 11:20         ` Paul P Komkoff Jr
2003-05-12 14:29           ` Valdis.Kletnieks
2003-05-13  2:24         ` Clemens Schwaighofer
2003-05-13  7:41           ` Anders Karlsson
2003-05-12 14:56       ` Lars Marowsky-Bree
2003-05-15  7:21     ` Riley Williams
2003-05-15 10:51       ` Anders Karlsson [this message]
2003-05-19  8:19         ` Jakob Oestergaard
  -- strict thread matches above, loose matches on Subject: below --
2003-05-12 16:32 Chuck Ebbert

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=1052995874.3248.20.camel@tor.trudheim.com \
    --to=anders@trudheim.com \
    --cc=Riley@Williams.Name \
    --cc=cs@tequila.co.jp \
    --cc=linux-kernel@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