| But did you know: | | | | reasemble your data without the correct order. |
| All drives must move in parallel to proper track | | | | Has the Raid been reinitialised? - if not DO NOT allow |
| lowering sustainedperformance | | | | a reinitialisation |
| Very limited scalability at a very high inherent cos | | | | Are you able to supply the Raid controller? |
| *Questions for the reader: | | | | Capacity of the drives (how many GB for each drive) |
| How many drives have failed? are they logical, | | | | What type of drives (IDE ,SCSI, SATA) |
| electrical or physicalfailures. Are the drives a matched | | | | Block Size used? (offset of starting block) |
| set. Do you know if the failure ofthe two drives was | | | | Details - additional RAID information - this additional |
| at the same time or has one drive failed and | | | | information could be about target data, what the |
| thesecond went out at a later date? | | | | technicains can do a quality control on? What makes |
| Keep the order of the drives - number them before | | | | this important for you to go ahead with the recovery |
| removing any drives. This is an extremly important | | | | as there are Raid systems now over 2TB and the |
| step as you can imagine how many ordering | | | | recovery lab needs to know what to recover to get |
| combinations the technicians would have to try to | | | | your business back up and running in the minimal time. |