- 220.127.116.11 Installing the Clone Plugin
- 18.104.22.168 Cloning Data Locally
- 22.214.171.124 Cloning Remote Data
- 126.96.36.199 Cloning and Concurrent DDL
- 188.8.131.52 Cloning Encrypted Data
- 184.108.40.206 Cloning Compressed Data
- 220.127.116.11 Cloning for Replication
- 18.104.22.168 Directories and Files Created During a Cloning Operation
- 22.214.171.124 Remote Cloning Operation Failure Handling
- 126.96.36.199 Monitoring Cloning Operations
- 188.8.131.52 Stopping a Cloning Operation
- 184.108.40.206 Clone System Variable Reference
- 220.127.116.11 Clone System Variables
- 18.104.22.168 Clone Plugin Limitations
The clone plugin, introduced in MySQL 8.0.17, permits cloning data
locally or from a remote MySQL server instance. Cloned data is a
physical snapshot of data stored in
includes schemas, tables, tablespaces, and data dictionary
metadata. The cloned data comprises a fully functional data
directory, which permits using the clone plugin for MySQL server
A local cloning operation clones data from the MySQL server instance where the cloning operation is initiated to a directory on the same server or node where MySQL server instance runs.
A remote cloning operation involves a local MySQL server instance (the “recipient”) where the cloning operation is initiated, and a remote MySQL server instance (the “donor”) where the source data is located. When a remote cloning operation is initiated on the recipient, cloned data is transferred over the network from the donor to the recipient. By default, a remote cloning operation removes existing user-created data (schemas, tables, tablespaces) and binary logs from the recipient data directory before cloning data from the donor. Optionally, you can clone data to a different directory on the recipient to avoid removing data from the current recipient data directory.
There is no difference with respect to data that is cloned by a local cloning operation as compared to a remote cloning operation. Both operations clone the same set of data.
The clone plugin supports replication. In addition to cloning data, a cloning operation extracts and transfers replication coordinates from the donor and applies them on the recipient, which enables using the clone plugin for provisioning Group Replication members and replicas. Using the clone plugin for provisioning is considerably faster and more efficient than replicating a large number of transactions (see Section 22.214.171.124, “Cloning for Replication”). Group Replication members can also be configured to use the clone plugin as an alternative method of recovery, so that members automatically choose the most efficient way to retrieve group data from seed members. For more information, see Section 126.96.36.199, “Cloning for Distributed Recovery”.
The clone plugin must be installed before you can use it. For installation instructions, see Section 188.8.131.52, “Installing the Clone Plugin”. For cloning instructions, see Section 184.108.40.206, “Cloning Data Locally”, and Section 220.127.116.11, “Cloning Remote Data”.
Performance Schema tables and instrumentation are provided for monitoring cloning operations. See Section 18.104.22.168, “Monitoring Cloning Operations”.