The Clone Plugin Should this scenario occur, you can either rectify the cause of the failure and re-execute the cloning operation, or forgo the cloning operation and restore the recipient data from a backup taken before the cloning operation. Before MySQL 8.0.24, if a network error occurs during a cloning operation, the operation resumes if the error is resolved within five minutes. From MySQL 8.0.24, the operation resumes if the error is resolved within the time specified by the  clone_donor_timeout_after_network_failure  variable defined on the donor instance. The  clone_donor_timeout_after_network_failure  default setting is 5 minutes but a range of 0 to 30 minutes is supported. If the operation does not resume within the allotted time, it aborts and returns an error, and the donor drops the snapshot. A setting of zero causes the donor to drop the snapshot immediately when a network error occurs. Configuring a longer timeout allows more time for resolving network issues but also increases the size of the delta on the donor instance, which increases clone recovery time as well as replication lag in cases where the clone is intended as a replica or replication group member. Prior to MySQL 8.0.24, donor threads use the MySQL Server  wait_timeout  setting when listening for Clone protocol commands. As a result, a low  wait_timeout  setting could cause a long running remote cloning operation to timeout. From MySQL 8.0.24, the Clone idle timeout is set to the default wait_timeout  setting, which is 28800 seconds (8 hours). This section describes options for monitoring cloning operations. A cloning operation may take some time to complete, depending on the amount of data and other factors related to data transfer. You can monitor the status and progress of a cloning operation on the recipient MySQL server instance using the  clone_status  and  clone_progress  Performance Schema tables. The  clone_status  and  clone_progress  Performance Schema tables can be used to monitor a cloning operation on the recipient MySQL server instance only. To monitor a cloning operation on the donor MySQL server instance, use the clone stage events, as described in Monitoring Cloning Operations Using Performance Schema Stage Events. 1123 Note Monitoring Cloning Operations using Performance Schema Clone Tables 5.6.7.9 Monitoring Cloning Operations •If a failure occurs while cloning data, the cloning operation is rolled back and all cloned data removed. At this stage, the previously existing data on the recipient has also been removed, which leaves the recipient with no user data. 5. The server is restarted automatically (applies to remote cloning operations that do not clone to a named directory). During startup, typical server startup tasks are performed. •If the automatic server restart fails, you can restart the server manually to complete the cloning operation. •Monitoring Cloning Operations using Performance Schema Clone Tables •Monitoring Cloning Operations Using Performance Schema Stage Events •Monitoring Cloning Operations Using Performance Schema Clone Instrumentation •The Com_clone Status Variable