Description of the Creating Temporary Instance state for an ApsaraDB RDS for MySQL instance

Updated at:

When you restore individual databases and tables of an ApsaraDB RDS for MySQL instance to the original instance in the ApsaraDB RDS console, the instance enters the Creating Temporary Instance state. This state indicates that the restoration task is in progress. The instance remains fully operational during this state — backup tasks and other operations continue to run normally.

Creating Temporary Instance state

Duration

The duration of this state depends on the volume of data being restored. Larger datasets result in longer restoration times.

Limitations

  • A restoration task cannot be suspended or interrupted after it starts.

  • Only one restoration task can run at a time. If you start another restoration task while one is already in progress, the following error is returned: The operation failed. The RDS instance is not in a ready state. Wait for the current task to complete before starting another.

  • If read-only instances are attached to the primary instance and a restoration task is in progress, the system automatically synchronizes data from the primary instance to all read-only instances after the restoration task is complete. This ensures data consistency between the primary and secondary instances.