Hmc-150-workflow-fcp-raid

[newsynoseman]

I couldn't find a thread that really addresses my question, so ... here goes:

My HMC-150, my MacBook Pro and I travel all over. I shoot on SDHC cards, which plug directly into my laptop. I copy the "private" folder to 2 Seagate GoFlex portable drives via the FW800 port. When I return to the studio, I put one of the GoFlex drives on the shelf and log and transfer everything with FCP 6.06 from the other portable drive to my Mac Pro, configured with three 2TB Seagate Barracuda XT drives configured in a RAID 0 as my scratch disc. I have Time Machine set up on a 1 TB external drive, which also is designated as my autosave drive. My non-time-coded files -- photos, x-rays, scanned documents, etc. -- are stored on the internal OS drive in the FCP project folder, and backed up on the external drive.

Now, I know there's a lotta talk about RAID 0 not providing mirroring. And while I've never had a drive fail in 8 years, it seems to me the worst that can happen if one (or more) of the RAID drives fails is I'll lose my media files, which I can simply log and transfer again from the portable drive on the shelf, and the FCP project file, which is backed up on the external drive.

So I get the performance advantage of the RAID 0 and still have redundancy.

The question is this: are there flaws in my thinking?

 

[dwelter]

And the winner of the HMC-150 Shoot and Backup Award goes to...
NEWSYNOSEMAN!

Seems the minute you put a back up copy on a GoFlex on the shelf, then have your Project files backing up to Time Machine- You're Golden.

RAID 0 (block-level striping without parity or mirroring) has no (or zero) redundancy. It provides improved performance and additional storage but no fault tolerance. Hence simple stripe sets are normally referred to as RAID 0. Any disk failure destroys the array, and the likelihood of failure increases with more disks in the array (at a minimum, catastrophic data loss is twice as likely compared to single drives without RAID). A single disk failure destroys the entire array because when data is written to a RAID 0 volume, the data is broken into fragments called blocks. The number of blocks is dictated by the stripe size, which is a configuration parameter of the array. The blocks are written to their respective disks simultaneously on the same sector. This allows smaller sections of the entire chunk of data to be read off the drive in parallel, increasing bandwidth. RAID 0 does not implement error checking, so any error is uncorrectable. More disks in the array means higher bandwidth, but greater risk of data loss.