Customer Name Confidentiality
Data type MySQL 5.6 for WIN data capacity 6 G The fault type database was mistakenly deleted. The client himself tried various recovery tools and could not find the missing database files. Repair results using the excellent MySQL database fragment recovery tool to extract all the IBD files from the partition, according to the table structure of the two tables provided by the customer, generate frm files, with the combined IBD file into the new library, after starting the table data is fully OK. Customer satisfaction is a 12-hour time. The MySQL database is deleted, or the hacker deletes the library, deletes the table and deletes the data in the table, as long as the original partition is protected, and the data is not written in general can be recovered. Delete the data in the table InnoDB good recovery, MyISAM engine table is not good recovery, because myd file within each row write 20 byte block link pointer. Delete tables need to be restored, InnoDB engine storage in IBDATA1 or IBD files can be recovered, MyISAM engine is more troublesome to do fragments from partition recovery. Delete Database recovery. The recovery scenario needs to be restored with the delete table. Remember to protect the original partition in the event of a mis-operation. , do not import the old backup and other coverage operations,
MySQL database delete restore MySQL drop database restore MySQL drop table data recovery