MySQL :: MySQL 5.7 Reference Manual :: 15.7.6.1 Transportable Tablespace Examples

MySQL 5.7 Reference Manual / ... / Transportable Tablespace Examples

15.7.6.1 Transportable Tablespace Examples

Note

If you are transporting tables that are encrypted using the InnoDB tablespace encryption, see Limitations and Usage Notes before you begin for additional procedural information.

Example 1: Copying an InnoDB Table From One Server To Another

This procedure demonstrates how to copy a regular InnoDB table from a running MySQL server instance to another running instance. The same procedure with minor adjustments can be used to perform a full table restore on the same instance.

On the source server, create a table if one does not exist:

mysql> use test;
mysql> CREATE TABLE t(c1 INT) engine=InnoDB;

On the destination server, create a table if one does not exist:
```
mysql> use test;
mysql> CREATE TABLE t(c1 INT) engine=InnoDB;
```
On the destination server, discard the existing tablespace. (Before a tablespace can be imported, InnoDB must discard the tablespace that is attached to the receiving table.)
```
mysql> ALTER TABLE t DISCARD TABLESPACE;
```
On the source server, run FLUSH TABLES ... FOR EXPORT to quiesce the table and create the .cfg metadata file:
```
mysql> use test;
mysql> FLUSH TABLES t FOR EXPORT;
```
The metadata (.cfg) is created in the InnoDB data directory.

Note

FLUSH TABLES ... FOR EXPORT is available as of MySQL 5.6.6. The statement ensures that changes to the named table have been flushed to disk so that a binary table copy can be made while the server is running. When FLUSH TABLES ... FOR EXPORT is run, InnoDB produces a .cfg file in the same database directory as the table. The .cfg file contains metadata used for schema verification when importing the tablespace file.
Copy the .ibd file and .cfg metadata file from the source server to the destination server. For example:
```
shell> scp /path/to/datadir/test/t.{ibd,cfg} destination-server:/path/to/datadir/test
```
Note

The .ibd file and .cfg file must be copied before releasing the shared locks, as described in the next step.
On the source server, use UNLOCK TABLES to release the locks acquired by FLUSH TABLES ... FOR EXPORT:
```
mysql> use test;
mysql> UNLOCK TABLES;
```
On the destination server, import the tablespace:
```
mysql> use test;
mysql> ALTER TABLE t IMPORT TABLESPACE;
```
Note

The ALTER TABLE ... IMPORT TABLESPACE feature does not enforce foreign key constraints on imported data. If there are foreign key constraints between tables, all tables should be exported at the same (logical) point in time. In this case you would stop updating the tables, commit all transactions, acquire shared locks on the tables, and then perform the export operation.

Example 2: Copying an InnoDB Partitioned Table From One Server To Another

This procedure demonstrates how to copy a partitioned InnoDB table from a running MySQL server instance to another running instance. The same procedure with minor adjustments can be used to perform a full restore of a partitioned InnoDB table on the same instance.

On the source server, create a partitioned table if one does not exist. In the following example, a table with three partitions (p0, p1, p2) is created:
```
mysql> use test;
mysql> CREATE TABLE t1 (i int) ENGINE = InnoDB PARTITION BY KEY (i) PARTITIONS 3;
```
In the /datadir/test directory, you will see a separate tablespace (.ibd) file for each of the three partitions.
```
mysql> \! ls /path/to/datadir/test/
db.opt  t1.frm  t1#P#p0.ibd  t1#P#p1.ibd  t1#P#p2.ibd
```
On the destination server, create the same partitioned table:
```
mysql> use test;
mysql> CREATE TABLE t1 (i int) ENGINE = InnoDB PARTITION BY KEY (i) PARTITIONS 3;
```
In the /datadir/test directory, you will see a separate tablespace (.ibd) file for each of the three partitions.
```
mysql> \! ls /path/to/datadir/test/
db.opt  t1.frm  t1#P#p0.ibd  t1#P#p1.ibd  t1#P#p2.ibd
```
On the destination server, discard the tablespace for the partitioned table. (Before the tablespace can be imported on the destination server, the tablespace that is attached to the receiving table must be discarded.)
```
mysql> ALTER TABLE t1 DISCARD TABLESPACE;
```
The three .ibd files that make up the tablespace for the partitioned table are discarded from the /datadir/test directory, leaving the following files:
```
mysql> \! ls /path/to/datadir/test/
db.opt  t1.frm  
```
On the source server, run FLUSH TABLES ... FOR EXPORT to quiesce the partitioned table and create the .cfg metadata files:
```
mysql> use test;
mysql> FLUSH TABLES t1 FOR EXPORT;
```
Metadata (.cfg) files, one for each tablespace (.ibd) file, are created in the /datadir/test directory on the source server:
```
mysql> \! ls /path/to/datadir/test/
db.opt t1#P#p0.ibd  t1#P#p1.ibd  t1#P#p2.ibd
t1.frm  t1#P#p0.cfg  t1#P#p1.cfg  t1#P#p2.cfg
```
Note

FLUSH TABLES ... FOR EXPORT statement ensures that changes to the named table have been flushed to disk so that binary table copy can be made while the server is running. When FLUSH TABLES ... FOR EXPORT is run, InnoDB produces a .cfg metadata file for the table's tablespace files in the same database directory as the table. The .cfg files contain metadata used for schema verification when importing tablespace files. FLUSH TABLES ... FOR EXPORT can only be run on the table, not on individual table partitions.
Copy the .ibd and .cfg files from the source server database directory to the destination server database directory. For example:
```
shell> scp /path/to/datadir/test/t1*.{ibd,cfg} destination-server:/path/to/datadir/test
```
Note

The .ibd and .cfg files must be copied before releasing the shared locks, as described in the next step.
On the source server, use UNLOCK TABLES to release the locks acquired by FLUSH TABLES ... FOR EXPORT:
```
mysql> use test;
mysql> UNLOCK TABLES;
```
On the destination server, import the tablespace for the partitioned table:
```
mysql> use test;
mysql> ALTER TABLE t1 IMPORT TABLESPACE;
```

Example 3: Copying InnoDB Table Partitions From One Server To Another

This procedure demonstrates how to copy InnoDB table partitions from a running MySQL server instance to another running instance. The same procedure with minor adjustments can be used to perform a restore of InnoDB table partitions on the same instance. In the following example, a partitioned table with four partitions (p0, p1, p2, p3) is created on the source server. Two of the partitions (p2 and p3) are copied to the destination server.

On the source server, create a partitioned table if one does not exist. In the following example, a table with four partitions (p0, p1, p2, p3) is created:
```
mysql> use test;
mysql> CREATE TABLE t1 (i int) ENGINE = InnoDB PARTITION BY KEY (i) PARTITIONS 4;
```
In the /datadir/test directory, you will see a separate tablespace (.ibd) file for each of the four partitions.
```
mysql> \! ls /path/to/datadir/test/
db.opt  t1.frm  t1#P#p0.ibd  t1#P#p1.ibd  t1#P#p2.ibd t1#P#p3.ibd
```
On the destination server, create the same partitioned table:
```
mysql> use test;
mysql> CREATE TABLE t1 (i int) ENGINE = InnoDB PARTITION BY KEY (i) PARTITIONS 4;
```
In the /datadir/test directory, you will see a separate tablespace (.ibd) file for each of the four partitions.
```
mysql> \! ls /path/to/datadir/test/
db.opt  t1.frm  t1#P#p0.ibd  t1#P#p1.ibd  t1#P#p2.ibd t1#P#p3.ibd
```
On the destination server, discard the tablespace partitions that you plan to import from the source server. (Before tablespace partitions can be imported on the destination server, the corresponding partitions that are attached to the receiving table must be discarded.)
```
mysql> ALTER TABLE t1 DISCARD PARTITION p2, p3 TABLESPACE;
```
The .ibd files for the two discarded partitions are removed from the /datadir/test directory on the destination server, leaving the following files:
```
mysql> \! ls /path/to/datadir/test/
db.opt  t1.frm  t1#P#p0.ibd  t1#P#p1.ibd
```
Note

When ALTER TABLE ... DISCARD PARTITION ... TABLESPACE is run on subpartitioned tables, both partition and subpartition table names are allowed. When a partition name is specified, subpartitions of that partition are included in the operation.
On the source server, run FLUSH TABLES ... FOR EXPORT to quiesce the partitioned table and create the .cfg metadata files.
```
mysql> use test;
mysql> FLUSH TABLES t1 FOR EXPORT;
```
The metadata files (.cfg files) are created in the /datadir/test directory on the source server. There is a .cfg file for each tablespace (.ibd) file.
```
mysql> \! ls /path/to/datadir/test/
db.opt  t1#P#p0.ibd  t1#P#p1.ibd  t1#P#p2.ibd t1#P#p3.ibd
t1.frm  t1#P#p0.cfg  t1#P#p1.cfg  t1#P#p2.cfg t1#P#p3.cfg
```
Note

FLUSH TABLES ... FOR EXPORT statement ensures that changes to the named table have been flushed to disk so that binary table copy can be made while the server is running. When FLUSH TABLES ... FOR EXPORT is run, InnoDB produces a .cfg metadata file for the table's tablespace files in the same database directory as the table. The .cfg files contain metadata used for schema verification when importing tablespace files. FLUSH TABLES ... FOR EXPORT can only be run on the table, not on individual table partitions.
Copy the .ibd and .cfg files from the source server database directory to the destination server database directory. In this example, only the .ibd and .cfg files for partition 2 (p2) and partition 3 (p3) are copied to the data directory on the destination server. Partition 0 (p0) and partition 1 (p1) remain on the source server.
```
shell> scp t1#P#p2.ibd  t1#P#p2.cfg t1#P#p3.ibd t1#P#p3.cfg destination-server:/path/to/datadir/test
```
Note

The .ibd files and .cfg files must be copied before releasing the shared locks, as described in the next step.
On the source server, use UNLOCK TABLES to release the locks acquired by FLUSH TABLES ... FOR EXPORT:
```
mysql> use test;
mysql> UNLOCK TABLES;
```
On the destination server, import the tablespace partitions (p2 and p3):
```
mysql> use test;
mysql> ALTER TABLE t1 IMPORT PARTITION p2, p3 TABLESPACE;
```
Note

When ALTER TABLE ... IMPORT PARTITION ... TABLESPACE is run on subpartitioned tables, both partition and subpartition table names are allowed. When a partition name is specified, subpartitions of that partition are included in the operation.

PREV HOME UP NEXT

User Comments