8.3 Restoring a Single .ibd File

A table with a table-specific tablespace (stored in an .ibd file) can be restored individually without taking down the MySQL server. If you have a clean backup of an .ibd file, you can restore it to the MySQL installation from which it originated as follows:

  1. Prevent write operations for the table to be restored. This prevents users from modifying the table while the restore is in progress.

    LOCK TABLES tbl_name WRITE;
  2. Issue this ALTER TABLE statement:


    Caution: This deletes the current .ibd file.

  3. Put the backup .ibd file back in the proper database directory.

  4. Issue this ALTER TABLE statement:

  5. Restore is now complete and the write lock can be released:


In this context, a clean.ibd file backup means:

You can make such a clean backup .ibd file with the following method:

  1. Stop all activity from the mysqld server and commit all transactions.

  2. Wait until SHOW INNODB STATUS shows that there are no active transactions in the database, and the main thread status of InnoDB is Waiting for server activity. Then you can make a copy of the .ibd file.

Another method for making a clean copy of an .ibd file is to use ibbackup:

  1. Use ibbackup to back up the InnoDB installation.

  2. Run ibbackup --apply-log to create a consistent version of the backup database.

  3. Start a second (dummy) mysqld server on the backup and let it clean up the .ibd files in the backup. Wait for the cleanup to end.

  4. Shut down the dummy mysqld server.

  5. Take a clean .ibd file from the backup.