7.6.6.14 Clone Plugin Limitations

The clone plugin is subject to these limitations:

• The donor and recipient can use different patch releases within the same MySQL server series. For example, cloning is supported between MySQL 26.7.0 and MySQL 26.7.2 in either direction.

• Cloning across MySQL server series is supported only from an LTS donor to the immediately following LTS recipient. For example, cloning from MySQL 9.7 LTS to MySQL 28.4 LTS is supported if MySQL 28.4 is the next LTS series after MySQL 9.7.

• Other cross-series cloning operations are not supported. This includes cloning when either server is an Innovation release, cloning to an older LTS series, and cloning that skips an LTS series. For example, cloning from MySQL 26.7 Innovation to MySQL 26.10 Innovation, from MySQL 28.4 LTS to MySQL 9.7 LTS, or from MySQL 9.7 LTS to MySQL 30.4 LTS is not supported.

• Only a single MySQL instance can be cloned at a time. Cloning multiple MySQL instances in a single cloning operation is not supported.

• The X Protocol port specified by mysqlx_port is not supported for remote cloning operations (when specifying the port number of the donor MySQL server instance in a CLONE INSTANCE statement).

• The clone plugin does not support cloning of MySQL server configurations. The recipient MySQL server instance retains its configuration, including persisted system variable settings (see Section 7.1.9.3, “Persisted System Variables”.)

• The clone plugin does not support cloning of binary logs.

• The clone plugin only clones data stored in InnoDB. Other storage engine data is not cloned. MyISAM and CSV tables stored in any schema including the sys schema are cloned as empty tables.

• Connecting to the donor MySQL server instance through MySQL Router is not supported.

• Local cloning operations do not support cloning of general tablespaces that were created with an absolute path. A cloned tablespace file with the same path as the source tablespace file would cause a conflict.