This topic describes the Creating Temporary Instance state of an ApsaraDB RDS for MySQL instance during database and table recovery. It covers the state's meaning, factors affecting its duration, important recovery considerations, and the data synchronization process between primary and read-only instances.
After you start a database and table recovery operation in the ApsaraDB RDS console and select restore to the original instance, the running state of the ApsaraDB RDS for MySQL instance changes to Creating Temporary Instance. This state indicates that the recovery task is in progress. Your instance remains fully operational during this process, and you can perform other operations such as initiating a backup. The duration of this state is proportional to the volume of data being recovered.
-
Once a recovery task starts, it cannot be paused or canceled.
-
While a recovery task is running, do not start another recovery operation. Otherwise, the system returns an error message such as "Operation failed. This operation is not supported in the current instance state." Wait for the current task to complete before starting another.
-
If a primary instance has read-only instances, the system automatically synchronizes data to all associated read-only instances after the recovery task for the primary instance is complete, ensuring data consistency between the primary and read-only instances.