content_image/742616.jpg
• mysqld  has flushed all modified pages of the .ibd  file from the buffer pool to the file. 

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

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

2. Wait until SHOW ENGINE 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 the MySQL Enterprise Backup product: 

1. Use MySQL Enterprise Backup to back up the InnoDB  installation. 

2. Start a second mysqld  server on the backup and let it clean up the .ibd  files in the backup. 

## Restoring from a Logical Backup 

You can use a utility such as mysqldump  to perform a logical backup, which produces a set of SQL statements that can be executed to reproduce the original database object definitions and table data for transfer to another SQL server. Using this method, it does not matter whether the formats differ or if your tables contain floating-point data. 

To improve the performance of this method, disable autocommit  when importing data. Perform a commit only after importing an entire table or segment of a table. 

## 15.6.1.5 Converting Tables from MyISAM to InnoDB 

If you have MyISAM  tables that you want to convert to InnoDB  for better reliability and scalability, review the following guidelines and tips before converting. 

<img src='content_image/742616.jpg'>

•Adjusting Memory Usage for MyISAM and InnoDB 

•Handling Too-Long Or Too-Short Transactions 

•Handling Deadlocks 

•Storage Layout 

•Converting an Existing Table 

•Cloning the Structure of a Table 

•Transferring Data 

•Storage Requirements 

•Defining Primary Keys 

•Application Performance Considerations 

•Understanding Files Associated with InnoDB Tables 

## Note 

Partitioned MyISAM  tables created in previous versions of MySQL are not compatible with MySQL 8.0. Such tables must be prepared prior to upgrade, either by removing the partitioning, or by converting them to InnoDB . See Section 24.6.2, “Partitioning Limitations Relating to Storage Engines” , for more information. 

