From: Bill Davidsen <davidsen@tmr.com>
To: Justin Piszcz <jpiszcz@lucidpixels.com>
Cc: Steve Cousins <steve.cousins@maine.edu>,
Linux RAID <linux-raid@vger.kernel.org>
Subject: Re: Changing chunk size
Date: Fri, 16 Feb 2007 18:15:44 -0500 [thread overview]
Message-ID: <45D63B20.2090605@tmr.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0702161428200.24249@p34.internal.lan>
Justin Piszcz wrote:
>
>
> On Fri, 16 Feb 2007, Steve Cousins wrote:
>
>>
>>
>> Bill Davidsen wrote:
>>>
>>> I'm sure "slow" is a relative term, compared to backing up TBs of
>>> data and trying to restore them. Not to mention the lack of
>>> inexpensive TB size backup media. That's totally unavailable at the
>>> moment, I'll live with what I have, thanks.
>>
>> You don't backup your RAID arrays? Yikes! For certain data this
>> would be fine (data that you can recreate easily) but it sounds like
>> this isn't the case for you otherwise you'd just wipe the array and
>> recreate the data. There are other modes of failure than just the
>> drives themselves (file system corruption for instance) so it is wise
>> to do backups, even on "redundant" systems.
>>
>> Good luck,
>>
>> Steve
>
> I agree here, RAID is no substitute for backups.
>
Neither is a 2nd copy on another machine, if it isn't something you can
store off site, it's not a backup. One of the few things I liked about
working for {a major telco} was that they had a "smoking hole" recovery
policy, what do you do when the data center is a smoking hole. I don't
get that kind of budget in other places.
--
bill davidsen <davidsen@tmr.com>
CTO TMR Associates, Inc
Doing interesting things with small computers since 1979
next prev parent reply other threads:[~2007-02-16 23:15 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-15 17:16 Changing chunk size Bill Davidsen
2007-02-15 23:24 ` Neil Brown
2007-02-16 16:48 ` Bill Davidsen
2007-02-16 18:49 ` Steve Cousins
2007-02-16 19:28 ` Justin Piszcz
2007-02-16 23:15 ` Bill Davidsen [this message]
2007-02-16 23:09 ` Bill Davidsen
2007-02-18 1:51 ` berk walker
2007-02-18 20:17 ` Bill Davidsen
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=45D63B20.2090605@tmr.com \
--to=davidsen@tmr.com \
--cc=jpiszcz@lucidpixels.com \
--cc=linux-raid@vger.kernel.org \
--cc=steve.cousins@maine.edu \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.