A Study on the Improvement Method of Deleted Record Recovery in MySQL InnoDB


KIPS Transactions on Computer and Communication Systems, Vol. 6, No. 12, pp. 487-496, Dec. 2017
10.3745/KTCCS.2017.6.12.487,   PDF Download:
Keywords: Database Forensic, Record Recovery
Abstract

In MySQL InnoDB, there are two ways of storing data. One is to create a separate tablespace for each table and store it separately. Another is to store all table and index information in a single system tablespace. You can use this information to recover deleted data from the record. However, in most of the current database forensic studies, the former is actively researched and its structure is analyzed, whereas the latter is not enough to be used for forensics. Both approaches must be analyzed in terms of database forensics because their storage structures are different from each other. In this paper, we propose a method for recovering deleted records in a method of storing records in IBDATA file, which is a single system tablespace. First, we analyze the IBDATA file to reveal its structure. And introduce delete record recovery algorithm which extended to an unallocated page area which was not considered in the past. In addition, we show that the recovery rate is improved up to 68% compared with the existing method through verification using real data by implementing the algorithm as a tool.


Statistics
Show / Hide Statistics

Statistics (Cumulative Counts from September 1st, 2017)
Multiple requests among the same browser session are counted as one view.
If you mouse over a chart, the values of data points will be shown.


Cite this article
[IEEE Style]
J. S. Kyun, J. W. Jang, D. W. Jeoung, S. J. Lee, "A Study on the Improvement Method of Deleted Record Recovery in MySQL InnoDB," KIPS Transactions on Computer and Communication Systems, vol. 6, no. 12, pp. 487-496, 2017. DOI: 10.3745/KTCCS.2017.6.12.487.

[ACM Style]
Jung Sung Kyun, Jee Won Jang, Doo Won Jeoung, and Sang Jin Lee. 2017. A Study on the Improvement Method of Deleted Record Recovery in MySQL InnoDB. KIPS Transactions on Computer and Communication Systems, 6, 12, (2017), 487-496. DOI: 10.3745/KTCCS.2017.6.12.487.