Media Information:
IBM Server
Fault Description:
A critical IBM server in a business unit located in Qingdao suffered a failure, storing important financial data. The incident occurred just at the end of the month, which made the situation extremely urgent with 100,000 records at stake. After consulting several data recovery companies in Beijing, the customer chose Das Technology and immediately flew to Beijing on the same day to resolve the issue as quickly as possible.
Troubleshooting:
Upon receiving the server, our engineers conducted an initial inspection of the first five hard drives. The results showed that three of them had different levels of bad sectors. We communicated with the customer, who confirmed that the critical data included two sets of accounting books, and they were able to restore either .BAK backup files or MDF database files.
Data Recovery Process:
Option One:
Considering the urgency and the customer's specific needs, our engineers decided to analyze the RAID configuration parameters and reorganize the data accordingly. If the two sets of books were not affected by the bad sectors, this approach would significantly improve recovery efficiency, avoiding unnecessary time spent on full disk mirroring. After reorganizing the data, the A.BAK file from August 28th and the B.BAK file from July 28th were successfully verified in the customer’s environment, and all data was found to be 100% normal.
Option Two:
During further communication, we learned that the last backup for account set B was on July 28th, and the most recent update data was stored in the physical file B.MDF. However, this file was partially corrupted due to bad sectors, resulting in an IO error. At this point, disk cloning was the only option, but it would have been too time-consuming for the customer, who couldn't afford any delay.
Our engineers analyzed the database layout across each disk and opted for a local mirroring strategy. They identified the start and end positions of the mirror, bypassed the bad sector (JUMP10), and adjusted the log after the mirroring process was completed. This allowed us to extract all recoverable sectors efficiently.
Once the mirroring was complete, we successfully extracted the B.MDF file. However, attaching it directly to SQL 2008 failed. Initial attempts to repair the database using a simple logless attachment were unsuccessful, as the index table pages were damaged. Despite this, since only a month’s worth of data was missing and the damage was limited to three key tables, our SQL repair software was able to recover all the data in those tables, leading to a successful recovery.
Data Recovery Results:
Most of the critical financial data was successfully restored, ensuring the customer could resume operations without major disruptions.
Advice to Customers:
If your server fails, avoid making any unauthorized changes. Always contact a professional and certified data recovery company to handle the situation. Attempting to fix the problem yourself may lead to permanent data loss.
Fabric Roller Curtain,Fabric Roll Up Blinds,Fabric Roller Blinds For Windows,Lace Roller Blinds
Hebei Charlotte Enterprise Co., Ltd. , https://www.hbcharlotteawning.com