rebuilding RAID info
 

I'm about to add a RAID O to my system.

Let's say I'm in the middle of a project, and one drive in the RAID fails.
Is this how I would deal with that?

1) replace drive
2) copy the original video files from backup disk onto the RAID array
3) when the editing system asks, "where is clip x?", I show it - and then it will find all the other clips?
or is it necessary to show the NLE where each clip is?

What takes the most time in rebuilding the array - just copying the original files into the array?

thanks

Re: rebuilding RAID info
 

I'll let more knowledged people chime in....

But your Raid 0 doesn't allow for any of that. If your drive fails......So does the raid. If you haven't made a backup, then say bye bye...

If having a swappable, or recoverable drive is important, and still want to retain Raid 0 speeds, you'll need to pony up on extra drives, and use a Raid array that allows for both speed and redundancy....

I just googled the first one. But there's better samples out there..

Re: rebuilding RAID info
 

I'm saying once the RAID fails, you replace the bad drive and reload all the original footage (which has been backed up on another external hard drive.

Re: rebuilding RAID info
 

"Waht Robert said." If you've rebuilt your RAID0, including the drive letter and folder structure where the copies of source files are located to be the same as the previous one before it failed, it may not know anything bad happened.

Regardless, scratch media (rendered temp files) can be regenerated by the NLE application; you may just have a short wait the first time you open a project. Source files should only be on a RAID0 if they are copies of your archive. I don't know about other NLE's but in the case of Adobe, yes, once you show it where one of the offline files is, the rest of the files in that location will be identified.

Re: rebuilding RAID info
 

thanks for the info. by the way, do you put the "scratch" area on the RAID 0 too? I thought most people had a separate disk for projects and scratch, but also wondered if that would slow down previews that need to access the scratch files?