Docs

RDS for MySQL

Data recovery

Batch rollback

This topic describes the notes, limitations, and operation steps for rolling back instances in the RDS for MySQL console.

Prerequisites

A Volcano Engine account has been created and the real-name authentication has been completed. For account registration and real name authentication, refer to How to Register an Account and Real-name authentication.

VPC service access authorization has been completed. For the authorization method, refer to Cross-service access authorization.

An instance has been created. For details, see Creating an instance.

Precautions

The rollback feature is associated with the backup cycle and the number of days to retain backups in the automatic backup settings. It provides rollbacks based on data backups and log backups (binlog) within the retention period. To ensure data security, the backup cycle for automatic backups must be set to at least twice a week.

If the database and table that must be rolled back do not exist or are deleted by mistake, you should first log in to the database and create the database and table, and then use the console for rollback.

If the table is not available in the cold backup before the rollback, disaster recovery will fail.

When you create a table with foreign key constraints under the same database with the same name, the table build fails due to the foreign key conflict, and MySQL creates the table with a different foreign key constraint name.

If the selected database to be recovered is empty, the recovery process will not create an empty bak database for this empty database.

The time for data recovery from a backup set is directly proportional to the data volume of the instance.

Limitation

Currently, rollback is supported only for primary nodes, not for read-only nodes and standby nodes.

Currently, only specified databases and tables can be rolled back, and the rolled-back databases and tables will be written back to the original instance.

In a batch rollback, up to 10 instances can be selected.

When using batch rollback for database and table-level recovery, you can select up to 500 databases or data tables in a single instance. The number of tables cannot exceed 50,000.

In the following scenarios, the fast recovery mode will fail, and the system will switch to the normal mode for restoration.

After a full or incremental physical backup, the fast recovery mode fails if a DDL statement is executed on databases and tables without first running a USE statement.

The fast recovery mode fails when restoring a table that was renamed after a full or incremental physical backup.

After a full or incremental physical backup, the fast recovery mode will fail if a table is renamed, a DML operation is performed on the table, and the table is then renamed back to its original name.

Procedure

Log on to the RDS for MySQL console.

In the upper-left corner of the top menu bar, select the project and region for the instance.

tip

If the project of the instance has not been set, the project should be selected as All resources.

Click Instances in the left-side navigation bar.

On the Instances page, select the target instances and click ... in the lower-left corner > Rollback.

tip

If the verification of any instance fails at the time of batch rollback, no instances will be submitted.

Set the relevant parameters on the Create rollback task page, as shown below.

Select the recovery mode. You can select Normal or Fast mode.

tip

After enabling the fast recovery mode, the system will optimize and accelerate eligible recovery tasks to improve overall recovery efficiency. If the task does not support the fast recovery mode, the system will automatically switch to the normal recovery mode to continue the task.

Select the databases and tables to roll back. Once you have made your selections, click Next step.

tip

The source of database table information is the current actual database table record of the database, and missing database table information can be entered manually. The steps for manual entry are as follows:

On the Create rollback task page, click Manual entry.

In the drop-down list in the Manual entry window, select instances.

In the Enter databases and tables text box, enter the databases and tables to roll back. You can enter up to 500 databases and tables separated by line breaks. You can also click Batch enter database and table names in the Manual entry window, and enter the names in batches in the Batch enter database and table names window, separated by commas (,), semicolons (;), or Enter.

Click OK.

Up to 5,000 databases are displayed for each expanded instance, and up to 5,000 tables are displayed for each expanded database.

Search libraries or tables via regular expressions or fuzzy matching. When searching for libraries and tables at the same time, the search results for the libraries and tables will be output based on "and logic".

Set up the rollback configuration, and specify the rollback time and names for the databases and tables. After the settings are completed, click OK, and then click OK in the pop-up dialog box to submit the rollback task.

Set backtime for instances in turn: You can set different backtime for different instances, and the backtime range is automatically calculated based on instance backups and Binlog logs. first.

Batch rollback time: You can set the rollback time for all instances to be rolled back in batches. Different instances support different rollback times. When setting the batch rollback time, the available time range is the intersection of the rollback time ranges supported by each instance.

Set the restored database and table name: By default, it is named with "original name_timestamp". Batch adjustment is supported to add a prefix, suffix, or both to the original names. The library table name should meet the principle of "starting with a letter and ending with a letter or number".

tip

If the modified name conflicts with the original database, the task will fail.

tip

You can click the Terminate button in the Batch tasks have been initiated dialog box. After termination, tasks for instances that have not yet started changes will no longer be executed and cannot be recovered. If you want to make changes again, you need to re-initiate the batch task.

If the task execution fails, place the cursor on Failure in the Execution result column to view the failure reason.

Last updated: 2026.08.21 16:00:29