This topic explains the "Creating temporary instance" state that an ApsaraDB RDS for MySQL instance enters during database and table restoration. It covers what this state means, factors that affect its duration, precautions, and how data is synchronized between the primary and read-only instances after restoration.
When you start a database and table restoration from the ApsaraDB RDS console and select the restore to the original instance option, your ApsaraDB RDS for MySQL instance enters the Creating temporary instance state. Your instance remains fully operational during this time and can be used for other tasks, such as performing a backup operation. The restoration takes longer for larger data volumes.
-
Once a restoration task begins, it cannot be paused or interrupted.
-
Do not start another restoration task while one is in progress. Otherwise, the system returns an error message: "Operation failed. This operation is not supported in the current instance state." Wait for the current restoration task to complete before you start the next one.
-
If the primary instance has read-only instances, the system automatically synchronizes the restored data to all of them after the primary instance is restored, ensuring data consistency.