Sử dụng Forcing Innodb Recovery để khôi phục dữ liệu MySQL

Sử dụng Forcing Innodb Recovery để khôi phục dữ liệu MySQL

Sử dụng Forcing Innodb Recovery để khôi phục dữ liệu MySQL. Xem chi tiết tại đây!

Để đảm bảo nội dung cụ thể và tính chính xác của thông tin, bài viết này chúng tôi mạn phép sử dụng thuần Tiếng Anh chuyên ngành để chia sẻ. Mong các bạn thông cảm!

Thông tin tham khảo :

MySQL Forcing InnoDB Recovery

1. Check the  size

So the size is 15242880

2. Edit /etc/my.cnf and force recovery and log size.

3. Restart Mysql service

Now and database should start, but with innodb_force_recovery in my.cnf all Insert and Update operation will be ignored.

Once you have restarted the MySQL server with innodb_force_recovery in place, you have to dump the corrupted databases.

Single Database

All Databases

Once you have the databases dumped successfully, stop MySQL completely and move the ib* files from /var/lib/mysql/ out of the directory.

4. Remove innodb_force_recovery and innodb_log_file_size

Remove innodb_force_recovery & innodb_log_file_size two lines from /etc/my.cnf and start MySQL service. Then Restore database into their respective database.

All Databases

Once restore completed, try to repair all the database.

Thats all.. check your mysql logs. A simple query for finding all of your InnoDB tables in case you want to specifically target the corruption.


The database must not otherwise be used with any nonzero value of innodb_force_recovery.

As a safety measure, InnoDB prevents users from performing INSERT, UPDATE, or DELETE operations when innodb_force_recovery is greater than 0.

Under the mysqld section of the config file you can add innodb_force_recovery = 0 – 6.

Levels 1-4 are pretty safe as most data is preserved. Setting the level to 5 or 6 gets a bit more risky as you could lose some data.

Chia sẻ bài viết

Bình luận