From: Kanoalani Withington <kanoa@cfht.hawaii.edu>
To: Roy Sigurd Karlsbakk <roy@karlsbakk.net>
Cc: jbradford@dial.pipex.com, jakob@unthought.net,
linux-kernel@vger.kernel.org, linux-raid@vger.kernel.org
Subject: Re: RAID backup
Date: Thu, 03 Oct 2002 10:00:07 -1000 [thread overview]
Message-ID: <3D9CA1C7.2000405@cfht.hawaii.edu> (raw)
In-Reply-To: 200210031326.47386.roy@karlsbakk.net
I have to pipe in here and agree that the idea of using a disk array
alone for backups is not a sound idea. Sure, backing up 2Tb to an old
exabyte drive isn't going to work, if you really have that much data you
need some more modern equipment.
Essentially I believe the idea of a redundant array sounds safer than it
really is in practice, especially when dealing with very large arrays
and with level 5 arrays. The reasons why this is so are manifold,
suffice to say that a few years of actually using such devices shows
that they have much more potential for catastrophic failure and latent
failure (you don't know it's broken until you go to use it and find out
it's broken) than a well designed tape archive or backup.
Not that disk to disk backups are a completely bad idea. In my
experience a combination works best. For example, automatic backups to
reserved disks or disk arrays on remote systems every night, but once a
week tape snapshots of that data. It's a lot of tapes but over time it
will prove to be worthwhile. If the data volume is too high, simple
backup scripts that write every file only once (essentially an archive)
to tape to make it more practical.
-Kanoa
Roy Sigurd Karlsbakk wrote:
>On Thursday 03 October 2002 13:20, jbradford@dial.pipex.com wrote:
>
>>Might it not be a good idea to DD the raw contents of each disk to a tape
>>drive, just incase you fubar the array? It would be time consuming, but at
>>least you could restore your data in the event that it gets corrupted.
>>
>
>er
>
>16 120GB disks?
>
next prev parent reply other threads:[~2002-10-03 19:58 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-03 11:20 RAID backup jbradford
2002-10-03 11:26 ` Roy Sigurd Karlsbakk
2002-10-03 11:36 ` jbradford
2002-10-03 20:00 ` Kanoalani Withington [this message]
2002-10-03 23:59 ` Effrem Norwood
2002-10-04 8:00 ` Lars Marowsky-Bree
2002-10-04 10:25 ` Illtud Daniel
2002-10-04 11:12 ` jbradford
2002-10-04 11:20 ` Alvin Oga
2002-10-04 12:52 ` Alan Cox
2002-10-04 12:52 ` Mr. James W. Laferriere
2002-10-04 13:24 ` Dr. David Alan Gilbert
2002-10-04 14:07 ` Russell King
2002-10-04 17:15 ` Dr. David Alan Gilbert
2002-10-04 21:45 ` Alvin Oga
2002-10-04 14:32 ` Luca Berra
2002-10-04 15:13 ` Richard B. Johnson
2002-10-04 15:31 ` Herman Oosthuysen
2002-10-04 16:11 ` Russell King
2002-10-04 18:51 ` Herman Oosthuysen
2002-10-04 21:37 ` RAID backup - media Alvin Oga
2002-10-04 18:58 ` RAID backup Kanoalani Withington
2002-10-04 21:51 ` RAID backup - mtx w/ tcl Alvin Oga
2002-10-04 21:59 ` Effrem Norwood
2002-10-04 22:22 ` Kanoalani Withington
2002-10-03 11:27 ` RAID backup Roy Sigurd Karlsbakk
-- strict thread matches above, loose matches on Subject: below --
2002-10-04 17:04 Cress, Andrew R
2002-10-05 3:13 Chris Adams
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=3D9CA1C7.2000405@cfht.hawaii.edu \
--to=kanoa@cfht.hawaii.edu \
--cc=jakob@unthought.net \
--cc=jbradford@dial.pipex.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-raid@vger.kernel.org \
--cc=roy@karlsbakk.net \
/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