The Clone Plugin •The donor and recipient MySQL server instances must run on the same operating system and platform. For example, if the donor instance runs on a Linux 64-bit platform, the recipient instance must also run on that platform. Refer to your operating system documentation for information about how to determine your operating system platform. • InnoDB  permits creating some tablespace types outside of the data directory. If the donor MySQL server instance has tablespaces that reside outside of the data directory, the cloning operation must be able access those tablespaces. You can query the  INFORMATION_SCHEMA.FILES  table to identify tablespaces that reside outside of the data directory. Files that reside outside of the data directory have a fully qualified path to a directory other than the data directory. •The recipient must have enough disk space for the cloned data. By default, recipient data is removed prior to cloning the donor data, so you only require enough space for the donor data. If you clone to a named directory using the  DATA DIRECTORY  clause, you must have enough disk space for the existing recipient data and the cloned data. You can estimate the size of your data by checking the data directory size on your file system and the size of any tablespaces that reside outside of the data directory. When estimating data size on the donor, remember that only  InnoDB  data is cloned. If you store data in other storage engines, adjust your data size estimate accordingly. •Plugins that are active on the donor, including any keyring plugin, must also be active on the recipient. You can identify active plugins by issuing a  SHOW PLUGINS  statement or by querying the INFORMATION_SCHEMA.PLUGINS  table. •The donor and recipient must have the same MySQL server character set and collation. For information about MySQL server character set and collation configuration, see Section 10.15, “Character Set Configuration” . •The same  innodb_page_size  and  innodb_data_file_path  settings are required on the donor and recipient. The  innodb_data_file_path  setting on the donor and recipient must specify the same number of data files of an equivalent size. You can check variable settings using  SHOW VARIABLES syntax. •If cloning encrypted or page-compressed data, the donor and recipient must have the same file system block size. For page-compressed data, the recipient file system must support sparse files and hole punching for hole punching to occur on the recipient. For information about these features and how to identify tables and tablespaces that use them, see Section 5.6.7.4, “Cloning Encrypted Data” , and Section 5.6.7.5, “Cloning Compressed Data” . To determine your file system block size, refer to your operating system documentation. •A secure connection is required if you are cloning encrypted data. See Configuring an Encrypted Connection for Cloning. •The  clone_valid_donor_list  setting on the recipient must include the host address of the donor MySQL server instance. You can only clone data from a host on the valid donor list. A MySQL user with the  SYSTEM_VARIABLES_ADMIN  privilege is required to configure this variable. Instructions for setting the  clone_valid_donor_list  variable are provided in the remote cloning example that follows this section. You can check the  clone_valid_donor_list  setting using  SHOW VARIABLES  syntax. mysql> SHOW VARIABLES LIKE ’clone_valid_donor_list’; mysql> SHOW VARIABLES LIKE ’innodb_page_size’; mysql> SHOW VARIABLES LIKE ’innodb_data_file_path’; mysql> SELECT FILE_NAME FROM INFORMATION_SCHEMA.FILES; +---------------+--------+ | version | 8.0.17 | +---------------+--------+ 1115