The Clone Plugin mysql> START SLAVE USER = ’ user_name ’ PASSWORD = ’ password ’ FOR CHANNEL ’ setup_channel ’; Or from MySQL 8.0.22 and 8.0.23: mysql> SELECT BINLOG_FILE, BINLOG_POSITION FROM performance_schema.clone_status; mysql> CHANGE SOURCE TO SOURCE_HOST = ’ source_host_name ’, SOURCE_PORT =  source_port_num , ... SOURCE_LOG_FILE = ’ source_log_name ’, SOURCE_LOG_POS =  source_log_pos , FOR CHANNEL ’ setup_channel ’; mysql> START REPLICA USER = ’ user_name ’ PASSWORD = ’ password ’ FOR CHANNEL ’ setup_channel ’; 5.6.7.7 Directories and Files Created During a Cloning Operation 5.6.7.8 Remote Cloning Operation Failure Handling When data is cloned, the following directories and files are created for internal use. They should not be modified. • #clone : Contains internal clone files used by the cloning operation. Created in the directory that data is cloned to. • #ib_archive : Contains internally archived log files, archived on the donor during the cloning operation. • *.#clone  files: Temporary data files created on the recipient while the existing data directory is replaced by a remote cloning operation. 1. Prerequisites are checked (see Remote Cloning Prerequisites). •If a failure occurs during the prerequisite check, the  CLONE INSTANCE  operation reports an error. 2. A backup lock is taken to block DDL operations. •If the cloning operation is unable to obtain a DDL lock within the time limit specified by the clone_ddl_timeout  variable, an error is reported. 3. User-created data (schemas, tables, tablespaces) and binary logs on the recipient are removed before data is cloned to the recipient data directory. •When user created data is removed from the recipient during a remote cloning operation, existing data in the recipient data directory is not saved and may be lost if a failure occurs. If the data to be replaced on the recipient is of importance, a backup should be taken before initiating a remote cloning operation. This section describes failure handing at different stages of a cloning operation. For informational purposes, warnings are printed to the server error log to specify when data removal starts and finishes: [Warning] [MY-013453] [InnoDB] Clone removing all user data for provisioning: Started... [Warning] [MY-013453] [InnoDB] Clone removing all user data for provisioning: Finished If a failure occurs while removing data, the recipient may be left with a partial set of schemas, tables, and tablespaces that existed before the cloning operation. Any time during the execution of a cloning operation or after a failure, the server is always in a consistent state. 4. Data is cloned from the donor. User-created data, dictionary metadata, and other system data are cloned. 1122