Rescue MySQL 5.7 Data Without Backups: Step‑by‑Step with dbsake & ibd2sql

Data loss in MySQL can be catastrophic, especially when no backups exist and the server is deployed as a single point of failure. This article presents a practical rescue workflow for MySQL 5.7 using two powerful open‑source utilities: dbsake for extracting table definitions from .frm files, and ibd2sql for converting .ibd data files into executable SQL.

Step 1 – Recover Table Structure with dbsake

Install dbsake :

# curl -s get.dbsake.net > dbsake
# chmod 755 dbsake

Use the installed binary to dump the table definition from the .frm file:

# ./dbsake frmdump /data/mysql/mysql57_1/data/test/t2.frm

The command outputs the complete CREATE TABLE SQL for the target table.

Step 2 – Recover Data with ibd2sql

First, create the recovered table in a fresh MySQL 8.0 instance using the SQL generated in Step 1.

Then, obtain and set up the ibd2sql tool:

# wget https://github.com/ddcw/ibd2sql/archive/refs/heads/main.zip
# unzip main.zip
# cd ibd2sql-main
# python3 main.py /data/mysql/mysql57_1/data/test/t2.ibd \
    --sdi-table /data/mysql/mysql8/data/recover/t2.ibd \
    --sql --ddl --complete-insert --mysql5

The script reads the .ibd file, uses the SDI file produced by dbsake for schema information, and emits SQL statements that recreate the data.

Parameter Explanation (ibd2sql)

/data/mysql/mysql57_1/data/test/t2.ibd – Path to the source .ibd file from the MySQL 5.7 data directory.

--sdi-table /data/mysql/mysql8/data/recover/t2.ibd – Path where dbsake stores the intermediate SDI file containing schema metadata.

--sql – Instructs ibd2sql to generate SQL statements for data insertion.

--ddl – Generates the CREATE TABLE DDL.

--complete-insert – Produces full INSERT statements with all column values.

--mysql5 – Indicates that the source database version is MySQL 5, ensuring correct parsing of the .ibd format.

After the command finishes, the .ibd file is transformed into executable SQL, allowing you to restore the lost data and avoid a career‑ending incident.