Sata Raid

But did you know:

All drives must move in parallel to proper track lowering sustained
performance
Very limited scalability at a very high inherent cos

*Questions for the reader:

How many drives have failed? are they logical, electrical or physical
failures. Are the drives a matched set. Do you know if the failure of
the two drives was at the same time or has one drive failed and the
second went out at a later date?

Keep the order of the drives - number them before removing any drives. This is an extremly important step as you can imagine how many ordering combinations the technicians would have to try to reasemble your data without the correct order.

Has the Raid been reinitialised? - if not DO NOT allow a reinitialisation

Are you able to supply the Raid controller?

Capacity of the drives (how many GB for each drive)
What type of drives (IDE ,SCSI, SATA)

Block Size used? (offset of starting block)
Details - additional RAID information - this additional information could be about target data, what the technicains can do a quality control on? What makes this important for you to go ahead with the recovery as there are Raid systems now over 2TB and the recovery lab needs to know what to recover to get your business back up and running in the minimal time. Sometimes critical data can be put up on ftp ( up to 2GB if this could help get business active in the case of recovered emails)

Guy explains SATA RAID in front of a greenscreen