linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Christopher Smith <csmith@nighthawkrad.net>
To: Jeff Breidenbach <jeff@jab.org>
Cc: linux-raid@vger.kernel.org
Subject: Re: split RAID1 during backups?
Date: Thu, 27 Oct 2005 10:04:02 +1000	[thread overview]
Message-ID: <43601972.6020006@nighthawkrad.net> (raw)
In-Reply-To: <E1EU01c-0001sZ-00@toko.jab.org>

Jeff Breidenbach wrote:
> Hi all,
> 

[...]

> So - I'm thinking of the following backup scenario.  First, remount
> /dev/md0 readonly just to be safe. Then mount the two component
> paritions (sdc1, sdd1) readonly. Tell the webserver to work from one
> component partition, and tell the backup process to work from the
> other component partition. Once the backup is complete, point the
> webserver back at /dev/md0, unmount the component partitions, then
> switch read-write mode back on.

Isn't this just the sort of scenario LVM snapshots are meant for ?  It 
might not help with the duration aspect, but it will mean your services 
aren't down/non-redundant for the entire time it takes to backup.

> Everything on this system seems bottlenecked by disk I/O. That
> includes the rate web pages are served as well as the backup process
> described above. While I'm always hungry for perforance tips, faster
> backups are the current focus. For those interested in gory details
> such as drive types, NCQ settings, kernel version and whatnot, I
> dumped a copy of dmesg output here: http://www.jab.org/dmesg

I think this might be one of those situations where SCSI really does 
offer a significant performance advantage, although if you're actually 
filling up that 500G, it'll be a quite a bit more expensive.

See if you can get hold of a reasonably sized array using SCSI drives 
and do some comparitive benchmarking.

You might also want to experiment with different filesystems, although 
that may not be feasible...

CS

  parent reply	other threads:[~2005-10-27  0:04 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-10-24 10:57 split RAID1 during backups? Jeff Breidenbach
2005-10-24 11:22 ` Jurriaan Kalkman
2005-10-24 11:37 ` Brad Campbell
2005-10-24 19:05 ` Bill Davidsen
2005-10-25  4:30 ` Thomas Garner
2005-10-27  0:04 ` Christopher Smith [this message]
  -- strict thread matches above, loose matches on Subject: below --
2005-10-24 12:07 Jeff Breidenbach
2005-10-24 13:26 ` Paul Clements
2005-10-24 18:55 ` dean gaudet
2005-10-24 20:28 Jeff Breidenbach
2005-10-24 20:58 ` John Stoffel
2005-10-25 22:18 ` David Greaves
2005-10-25  3:37 Jeff Breidenbach
2005-10-25  4:07 ` dean gaudet
2005-10-25  8:35 ` Norman Schmidt
2005-10-25 17:51   ` John Stoffel
2005-10-25 19:20     ` Norman Schmidt
2005-10-25 18:04 ` John Stoffel
2005-10-25 18:13 ` Paul Clements
2005-10-25 20:05 ` Bill Davidsen
2005-10-26 18:15   ` Dan Stromberg
2005-10-25  5:01 Jeff Breidenbach
2005-10-26  8:17 Jeff Breidenbach
2005-10-27 13:23 ` Bill Davidsen
2005-10-30  3:06 Jeff Breidenbach

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=43601972.6020006@nighthawkrad.net \
    --to=csmith@nighthawkrad.net \
    --cc=jeff@jab.org \
    --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).