Database page fragmentation splicing Share

First, fault description

Beijing One company due to the misuse administrator accidentally deleted XenServer server in a virtual machine, since this server storing important data of the company, and therefore linked to the virtual machine data recovery center data recovery. Data recovery center data recovery engineers to the customer site for initial inspection found that the client within the VPS server is unavailable, the virtual disk data is lost. Through communication, the customer has taken on-site data recovery data recovery form, send engineers to carry data recovery device access to the customer's site for data recovery.

Second, the data recovery process

Data recovery engineers carry hardware to the customer's site within the first all hard disk sector level client server mirroring to ensure that customers within the original server data security. Then fishes underlying data is analyzed to recover the deleted virtual machine.
Within the customer's server virtual machine disk storage structure LVM, a virtual machine disk Lite mode. Server data recovery engineers troubleshoot the underlying data have not yet found a part lvm information is updated,
see below
Database page fragmentation splicing Share
analysis to find the lvm information to try to restore virtual disk data area, but most of the virtual disk data area data being destroyed, only fragments are preserved database page a.
Data recovery engineers are turning to ways to fight the debris to restore the damaged database, data recovery engineers to analyze the starting location of the database, and then start from scratch in order to scan data fragmentation meet the database page, and finally the use of these databases page fragments in order to form a complete re mdf file checksum and file integrity,
as shown below:
Database page fragmentation splicing Share

After verification by Mdf file by data recovery engineers to build a new database environment, additional just recovered mdf files to just build a good database environment, the relevant tables to the latest data state, all data through normal inquiry, recent data integrity .
As shown below:
Database page fragmentation splicing Share

Third, client authentication, data recovery success

After the successful recovery of data in the server, by the customer engineer to verify all the data, all data are already proven successful recovery, server data recovery this success. Sentence summary of this data recovery process: Due to a large amount of damage to the underlying data server, data can not be recovered by conventional means, can only choose to fight the difficult way to recover the debris, but more difficult to fight fragmentation data recovery is large, only part data recovery company can do.

Guess you like

Origin blog.51cto.com/sun510/2420962