The table must already exist and not have been dropped or truncated since taking the backup. When an InnoDB table is truncated, or dropped and recreated, it gets a new table ID. Any ID mismatch between the table in the database and the backed-up table can prevent it from being restored. The requirement for matching table IDs is also the reason why you must restore to the same MySQL server from which the backup data came, not another server with a similar set of databases and tables.

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;

Issue this ALTER TABLE statement:

ALTER TABLE tbl_name DISCARD TABLESPACE;

Caution: This deletes the current .ibd file.

Copy the backup .ibd file back to the appropriate database directory.

Issue this ALTER TABLE statement:

ALTER TABLE tbl_name IMPORT TABLESPACE;

Release the write lock to complete the restore procedure:

UNLOCK TABLES;

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

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.

Use mysqlbackup with the --only-innodb option to back up the InnoDB installation.

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

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.

Shut down the dummy mysqld server.

Take a clean .ibd file from the backup.