RAID array Considerations - Any advice?
Solution 1:
If I could suggest a slight modification of your plans:
- Put the OS on two smaller disks and mirror them.
- Create a second array, preferably RAID 6 with a hot spare, and make it a dynamic partition within Windows so you can expand later.
Don't dynamically expand volumes that are on the system disk. I've heard bad things about that. Keep the system separate from the data for performance reasons but also for volume corruption reasons.
RAID 6 is to counter the higher possibility of encountering a URE while rebuilding a failed RAID set. (Some good reading on the topic here, here and here over at the Storage Mojo blog). Even with RAID controllers that scrub drives looking for problems, I recommend an array that can sustain at least two drive failures before data loss. Thus my recommendation for RAID 6. The hot spare makes sure the rebuild happens as quickly as possible even if it's 3AM and you turned your cell phone's text message alert off in your sleep (if you haven't done that yet, you will someday =) ).
In addition, I'm sure you know that RAID is not a backup so it would be good to archive the data to tape once in a while and put it in a bank vault.
Solution 2:
There was some good discussion yesterday about RAID5 vs. 6
All of Wesley's suggestions are spot on, you're better off w/ the "data array" completely separate from the system array, and for an archive, the possible performance hit of RAID6 shouldn't be an issue.