RAID5 crash can not enter the system ORACLE database data recovery

Case:
The customer is an organ and unit, and the IBM System X3650M4 server runs the Oralce 11 database. The system uses 3 500GB hard disks to form the RAID 5 environment. OS is Windows Server 2008 R2.Customers upgraded the system on October 12 to install the system after the hard disk re -partitioning. The data was not backup before.After running for a period of time, the machine hard disk was on yellow light, the system collapsed, and the boot could not enter.Customers need to restore the ORALCE data spare parts and websites before the reinstalled system.

Solution:
1. The engineer of the data recovery center detects the RAID5 hard disk, one of which is damaged by a magnetic head, and the other hard disk has a serious bad duct. Two hard disks fail, causing Raid5 to collapse. 2. The engineer performs a complete physical mirror of the underlying hard disk. Then reorganize virtual RAID5 data. Analyze the data before the loss of partitions, extract the ORALCE database file, verify, and find that the data is not fresh. Therefore, it can only continue to repair another magnetic head to damage the hard disk. 3. In Zhongke’s capable of faith in the 100 -level cleaning room, the same model is replaced with the same model to match the magnetic head, and the underlying data of the hard disk of the mirror fault disk. 4. Continue to reorganize the virtual RAID5 data, analyze the Oralce database file before the loss of the partition, and verify that the data is as of October 12, which is the database file required by the customer. 5. Continue to analyze the entire set of data. After 1 working day, the ORALCE database required by customers and 100%recovery of Web website data. Customer satisfaction. Remarks: In this case, the original ORALCE database file and the web website data files are stored in the D drive and E drive before the partition. After the partition and installation system, the area is not covered by the new data. %recover.