Case:
An important MySQL database server, 146GB*2, RAID1, about 130GB Data volumes, stored about 200 ~ 300 databases.After the administrator usually releases each database DUMP, it directly compresses it into a .gz package, and then all the important .gz packets compressed into a total .tar.gz package. These files were generated once a day to cover the original backup backupEssenceData files and backup files are all stored on the DATA volume.During a system maintenance, the administrator accidentally rolled all the files under the DATA rolling. After deleting, the system stopped the system immediately and did not do other operations, but there were still a large number of terminals accessing this server when deleting.The MySQL database file is required, namely MyD, FRM, Myi (reconstructed) file, or .gz package of each database, or the total .TAR.GZ backup package of all important databases.
Solution:
1. Full backup of the fault volume.2. Restore analysis of the total .TAR.GZ, but the restored file will be reported to about 50%, and the subsequent file list cannot be listed.According to analysis, the biggest reason is that there are still data writing damage files when deleting.3. Restore analysis of sub -package .gz files, and most of them recovered successfully.4. For the .gz database that did not recover successfully.Restore its MyD RM data file directly, and all data recovers successfully.