When you restore the databases and tables of an ApsaraDB RDS for MySQL instance, the RDS instance enters the Creating Temporary Instance state. This topic describes the meaning, duration, and influencing factors of the state. This topic also describes the usage notes for task execution and the mechanism for data replication between the primary and secondary RDS instances after the restoration is complete.
After I use the restoration feature for individual databases and tables to restore the data to the original RDS instance in the ApsaraDB RDS console, the RDS instance enters the Creating Temporary Instance state. The state indicates that the restoration task is in progress. Your RDS instance can run as expected in this state. For example, backup tasks can normally run. The period of time of the state varies based on the volume of data that you want to restore. If you restore a large amount of data, the RDS instance is in this state for a long period of time.
If a restoration task starts, you cannot suspend or interrupt the task.
If a restoration task is in progress, we recommend that you do not start another restoration task. If you start another restoration task, the "The operation failed. The RDS instance is not in a ready state." error message is displayed. You can run a restoration task only after no restoration tasks are in progress.
If read-only RDS instances are attached to the primary RDS instance and a restoration task is in progress on the primary RDS instance, the system automatically synchronizes data from the primary RDS instance to all read-only RDS instances after the restoration task is complete. This ensures data consistency between the primary and secondary RDS instances.