linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Brad Campbell <brad@wasp.net.au>
To: Jeff Breidenbach <jeff@jab.org>
Cc: linux-raid@vger.kernel.org
Subject: Re: split RAID1 during backups?
Date: Mon, 24 Oct 2005 15:37:58 +0400	[thread overview]
Message-ID: <435CC796.4000207@wasp.net.au> (raw)
In-Reply-To: <E1EU01c-0001sZ-00@toko.jab.org>

Jeff Breidenbach wrote:

> 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.

Why not do something like this ?

mount -o remount,ro /dev/md0 /web
mdadm --fail /dev/md0 /dev/sdd1
mdadm --remove /dev/md0 /dev/sdd1
mount -o ro /dev/sdd1 /target

<do backup here>

umount /target
mdadm -add /dev/md0 /dev/sdd1
mount -o remount,rw /dev/md0 /web

That way the web server continues to run from the md..
However you will endure a rebuild on md0 when you re-add the disk, but given everything is mounted 
read-only, you should not practically be doing anything and if you fail a disk during the rebuild 
the other disk will still be intact.

I second jurriaan's vote for rsync also, but I would be inclined just to let it loose on the whole 
disk rather than break it up into parts.. but then I have heaps of ram too..

Regards,
Brad
-- 
"Human beings, who are almost unique in having the ability
to learn from the experience of others, are also remarkable
for their apparent disinclination to do so." -- Douglas Adams

  parent reply	other threads:[~2005-10-24 11:37 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 [this message]
2005-10-24 19:05 ` Bill Davidsen
2005-10-25  4:30 ` Thomas Garner
2005-10-27  0:04 ` Christopher Smith
  -- 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=435CC796.4000207@wasp.net.au \
    --to=brad@wasp.net.au \
    --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).