Hi JimQ-
Glad you're excited, but we have more planning to do.
So, with a 4 drive RAID, you're looking at some serious performance. Also heat. Better to use an external housing. Both the heat and the power needs can have negative effect when all is installed internally. The port multiplier housing that The hatter recommends is a sweetheart. That (or similar), with 4 drives, each direct connected to a PCI controller (4 eSATA port) would give you a great RAID setup.
So, what is this port multiplication about, you say? Well, this is a hardware based process of allowing all drives in the external cabinet to be connected as "one" using one data cable. This is great to allow for additional eSATA ports to be used elsewhere, but there is a performance hit. Using the direct connection of each drive allows for the maximum performance achievable.
Logistically, as suggested, using a single drive for OS and Applications, and then using the RAID to do the work would probably be a good way to go.
So, now that we have a boot drive, and a 4 drive RAID, we have to protect all that data that we are processing. Remember, in a RAID 0, when one drive goes down, all is lost. So, we need a backup scheme for the 4 drive RAID 0 set.
As sweet as a 4 drive RAID 0 sounds, the reality is you have to duplicate the hardware capacity to duplicate the data. We could just connect a couple of external firewire interfaced housings, and do the backups manually. But, we wouldn't want to forget to backup.
A more automatic approach might be more beneficial....RAID. This means run a second RAID set. This could get spendy....
There is another way.... combining RAID types accross multiple sets, or nested RAID.
Using a RAID 1 set to mirror the RAID 0 set (RAID 1+0) would provide "automatic" redundancy of data. In this way, if one drive in the RAID 0 set went down, the drives in the RAID 1 set would have the data stored. Better, if the hardware supports it, and requiring hardware RAID (thought to be better than software RAID anyways), would be a RAID 5+0 (RAID 50). This gives increased safety of data should a disk or two fail.
What this all means, bottom line, in a 4 640GB drive nested RAID set will give you 1.2TB of data capacity accross the set, yet data integrity is maintained in case of drive failure.
Yeah, gets confusing, but it's your business, and your livelyhood, so we can't make these decisions lightly. The four guys in the shop would be real p
**d off if you lost all their work due to some hardware failure....
A bit of reading might be good.
Nested RAID Levels and the parent page,
RAID may help educate you a bit regarding the subject.
OK- so back to it...
So, let's say that we have our boot drive, and our 4 drive RAID 10 in an external enclosure.
Do we want to keep all the data on the RAID set? Once processed, and the plan is finalized, I think best to have a place for that file to reside, or archive, if you will.
Well, we have that second internal bay, yet, and a big ol' 1TB drive would hold quite a bit of data.
Maybe this would be just the spot for our archive drive....
Now, I've possibly completely muddied the once seemingly clear waters of this topic. But, playing Devil's advocate is sometimes better than allowing one to blissfully spend hard earned dollars.
Then again, keeping to the K.I.S.S rule, just run a single boot drive, a 2 1TB drive RAID 0, and backup to a 1TB internal might be all a guy really needs.....To do that, I'd install a
150GB 10K Raptor as the boot, two 1TB Hitachi drives in an
OWC housing, connected to a FirmTek/Seritek controller card, backed to another 1TB Hitachi inside the tower.
Hey, except for the 1TB drives (mine are WD 640GB drives) sounds like my setup.......
Oh, and my Vectorworks still runs on OS 9....outdated, maybe, but a great tool!
BTW, I like The hatters suggestion a lot. Especially the way it has room to grow.....
And, lastly, keep the X800XT. Only the
X850 is faster (a bit), and the X1900 is PCIe (for dual core G5's), not AGP.