Prev: Event ID 12289, VSS
Next: GPO
From: Falcon ITS on 29 Jan 2010 22:18
Hello,

You can recover if you use an identical mainboard and identical
devices. Otherwise you will have drivers, bindings, etc deal with.
RAID is mainly for Disk Redundancy not main board redundancy.

I prefer hardware RAID, if you are going to do it, do it right. Also,
try to stick with GOOD mainstream RAID. i.e. Adaptec, LSI, Mylex. Stay
away from low end RAID controllers.

Cheers,


Miguel Fra / Falcon ITS
http://www.falconits.com

From: Bill Kearney on 30 Jan 2010 10:21
> You can recover if you use an identical mainboard and identical
> devices. Otherwise you will have drivers, bindings, etc deal with.
> RAID is mainly for Disk Redundancy not main board redundancy.

This is incorrect. He didn't ask about recovering the whole OS. He asked
about accessing it from another instance of an OS already on the other
machine. He can do what he's asking using a software mirrored volume. I
know, I've done it.

> I prefer hardware RAID, if you are going to do it, do it right. Also,
> try to stick with GOOD mainstream RAID. i.e. Adaptec, LSI, Mylex. Stay
> away from low end RAID controllers.

Unless, of course, the same type hardware RAID can't be setup on the new
machine. Many motherboard-based RAID sets can't be setup on a different
machine. Not unless they make a card-based RAID controller that actually
supports this. I've yet to work with one that did so reliably.

Then there's the other problem of the RAID vendor not keeping drivers
updated for new OSes. Adaptec has, more than once, abandoned perfectly good
RAID hardware by not supporting upgraded drivers.

-Bill

 | 
Pages: 1
Prev: Event ID 12289, VSS
Next: GPO