Originally posted by: JohnVM
About backing it up - well, I dont really want to make anyone give me a big lesson, but could you tell me briefly what the difference between RAID0/RAID5 is? I know a LITTLE bit about them, but not much.
My main concern is having a lot of space, and I was under the impression that RAID0 is the way to do that -- if theres a better solution please let me know.
Anandtech FAQ on RAID
In summary though:
RAID 0 - striping. You get all the space of all the drives, and speed, but zero redundancy. If one fails, wave goodbye to all of your data.
RAID 5 - striping with parity. You lose one drive's worth of space, but if any one drive fails, you lose some speed, but no data. When you get a replacement drive, plug it in, and in a few hours, all will be well. It takes the controller awhile to read the data and the parity stripes, and calculate what the original data on the replaced drive should be. So you get speed and fault-tolerance, at the expense of the space of one drive.
I've got a Promise SX4000 - it is probably the PATA parent of the SATA thing that Fuchs linked to. It has higher CPU usage than most other hardware-based RAID 5 cards, but it is still negligible - maybe 5%. It doesn't even show up on my CPU usage graph.
Oh yeah, quick thing about the SX150 - it needs RAM. Check Promise's page for what it supports; I used 128MB PC100 ECC RAM in my SX4000.
For normal use it isn't faster than a single disk.
How many single disks are there that can manage
sustained, not burst speeds, of 85MB/sec? Not a huge increase, but it's definitely faster. And my SX4000 very nearly saturates the PCI bus when I'm testing burst speeds. If I had it on a 66MHz PCI bus, it'd probably do better. Access times though aren't much different than a single drive.
For the record, I've got two PC's - my main system uses two standalone disks. My secondary is now a fileserver and safe haven for data, but also a video editing station. RAID 5 gave it redundancy and speed.