On 11/13/2014 1:05 PM, John Larkin wrote:
> On Wed, 12 Nov 2014 20:41:31 -0700, Don Y <
th...@is.not.me.com> wrote:
[elided]
>>> On my desktop PCs (ProLiants with hot-plug RAID) I occasionally pull
>>> out a drive for one reason or another, and poke in a replacement. It
>>> takes about 1.5 hours to resync them.
>>
>> What level RAID? What size volume? Does it scrub? Or, are you left
>> to "discover" your losses down the road (when you decide you *need*
>> a particular file)?
>
> I think it's raid1, namely the same data on two drives. 62G drives for
> C:, which is the OS and my apps. I have other drives, local and USB
> and network, for the big stuff.
Wait until you are dealing with TB+ drives and *have* to do a rebuild
(not *choose* to do one but, instead, find yourself with a failed array).
You will sweat *bullets* for hours!
I think you will also discover that your mirror'ed arrangement is
just false security. Many implementations only "check" files as
you access them (so, any files that you don't access regularly,
can develop problems and you won't know about those problems *or*
that they are harbingers of more to come!). Some implementations
only grab the accessed file off of *one* volume and don't even
look at the second volume unless the first throws a read error.
So, the second volume (your "backup"!) could be trash before you
ever need it!
You really want an array that scrubs continuously to give you some
assurance that your data *is* still recoverable. Of course, this
often comes at some performance cost (not much for a workstation
but a fair bit for a file server that sees traffic) as the array
is CONSTANTLY being read and checked and (silently) rewritten as
errors are encountered (i.e., BEFORE you would have stumbled on
them).
>> You should also see if you can "move" an array (or portions of it)
>> to another "identical" machine. E.g., anticipate how you will
>> deal with a general hardware failure (bad motherboard, etc.).
>
> I do that now and then, clone my work PC to the identical machines at
> home and in the cabin. It always works.
>
> The weird thing is that a drive is always a slot1 drive or a slot2
Exactly. And, you will find that moving either/both of them to a different
make/model machine will leave you with *nothing* (except an offer to
INITIALIZE the drives!).
> drive. I can pull a drive from my work machine, either one, and plug
> in a replacement, and the drives sync. The pulled drive can be used to
> boot another machine, but only in the corresponding slot. Once a
> cloned machine boots, I hot-plug a drive into the empty slot and, in
> an hour or so, I have two identical drives in that one, too.
You want to make sure you keep two of each such machine and hope they
don't both die at the same time.
I have 6 RAID appliances -- all different. If one of them craps out,
it's "manual recovery mode" for me! I cant just pull the drives from
the failed NAS box and install them in another (different make/model)
and HOPE to be able to access the data.
For this reason, I have been moving my archives onto "home grown"
storage arrays so I can ensure the disks are "accessible" without
relying on a (proprietary) RAID implementation. This is a much
lower performance approach -- but, if one of the boxes dies, I
can plug the drives into any of the other machines, here, and
access them directly from there.
All of these are reasons why you *really* want to rehearse the various
types of failures that you are likely to encounter on each machine
(e.g., motherboard goes flakey and starts writing crap on BOTH drives;
software bug corrupts a volume; etc.)
There is no worse feeling than watching an archive crash! And, wondering
if your precautions against this scenario are adequate (and that you
remember them! Each RAID implementation I've seen has its own wonky
user interface... and, there are no "do overs" there!).
Years ago, I kept my (40GB) archive on 4G external SCSI drives (when they
were $1000/each) that were kept "off-line" (on a shelf in a closet). I
mounted one of them, one day, to pull something off of it. And, the
drive was unreadable!
"Yikes!"
OK, I've anticipated this -- each of the drives had a cloned copy
available (like your RAID mirror -- except the drives are unplugged/off
most of the time).
Installed the backup drive -- and *it* was unreadable!!
"WTF???"
Turns out, the OS had a bug in the disk driver that would scramble
certain make/model drives. I was lucky enough to have a dozen of
them! :<
On another machine (different OS), I began feeding MO disks to rebuild
a copy of the archive. Then, installed two fresh copies on the two
"failed" drive. Of course, I held my breath as each MO disk was read
wondering if I would encounter an unrecoverable read error (and have
to resort to the *tape* copy of the archive)
>>> We've used floppies, tape, hard drive cartriges, CDs, DVDs, and USB
>>> sticks for backup. I don't think we've ever lost anything important.
>>>
>>> Just make lots of copies.
>>
>> Yup. I keep two copies on "high throughput" media (enterprise grade
>> magnetic disk); a copy on commodity media (CD/DVD); some things
>> on tape (DLT/SDLT/Ultrium) and others on MO. *NOTHING* "on-line"
>> unless its being accessed!
>>
>> But, like good gardens, they need to be "tended" regularly!
>>
>> Also, thinking hard about what's *really* important to save is
>> time well spent. In the past year, I've been purging my archives
>> of everything "client related" (they were warned... if they haven't
>> kept a copy or requested mine... <shrug> let them find a service
>> if they don't want to handle it themselves!)
>
> I never throw anything away! Not even old D-size vellum drawings.
I moved all of my drawings onto electronic media many years ago.
Map/drawing file just takes up too much space in the house!
Having *done* that, SWMBO later decided she needed one to store
her artwork... <frown> So, no net gain in free space, here.
(and, she had to have the super huge "Arch E"-size file... TWO
of them! :-/ *AND*, somehow has managed to *fill* them!!)
I've "officially" ended support for those folks so why bother holding
onto stuff for them? (it can also be regarded as a *liability* on
my part as I'd still have to safeguard their trade secrets, etc.)
Of course, that makes it a virtual CERTAINTY that I'll receive a
call from someone desperately looking for something!! <shrug>