easyrider said:
I can see the speed benefits from having the files being worked on in RAID 0, but I wouldn't store them on the RAID array in case of any instability.
As I found out only recently, if your array fails and/or your motherboard blows, retrieving your data is not easy.
The reason I have windows on the RAID array is no matter how much system RAM you have, Windows insists on using the Page File, and the RAID array has the quickest read/write speed. I have in the past put the page file on another drive and even on another partition, but it wasn't as quick as having it on the RAID array.
After a good few years of chopping and changing, my set up now is,
4 x 36 GB Raptors in RAID 0 (Windows / Programs / work in progress)
2 x 250 GB Storage Drives (1 with completed tasks on and the other with saved work in progress)
1 x 120 GB external store drive with image of RAID O array taken
1 x 500 GB external storage drive with images of the 250 GB drives taken.
I use Acronis for creating the backups/images and their 'secure zone' option which creates a partition at the end of the array and stores incremental images of the array. You can then boot into this partition which loads Acronis enabling you to restore any saved points if needed.
If you’re doing any work as either a job or just for fun, backups are very important I've found. Here are some recent problems I've had.
1. RAID array corrupts - Deleted array and restored from image on the 120 GB drive
2. RAID drive failed - Deleted array, replaced drive, created new array and restored image as above
3. PSU blew taking MB with it - New MB, (Optional) deleted array and restored image as above (If the new MB had a different RAID controller I would still have had saved and accessible all my completed work and work in progress)
I'm not saying the is the only/best way to go, and some might say it's overkill, but this set up works best for me at the moment and hopefully keeps backups for every eventuality.
Sorry for going on a bit
...
Jack