Updated on 2022-11-15 GMT+08:00

Restoring a DB Instance to a Point in Time

Scenarios

You can restore from automated backups to a specified point in time.

You can restore one or multiple DB instances at a time.

When you enter the time point that you want to restore the DB instance to, RDS downloads the most recent full backup file from OBS to the DB instance. Then, incremental backups are also restored to the specified point in time on the DB instance. Data is restored at an average speed of 30 MB/s.

Constraints

  • You can restore to new DB instances from backups only when your account balance is greater than or equal to $0 USD. You will pay for the new instance specifications.

    Do not run the reset master command on RDS for MySQL DB instances within their lifecycle. Otherwise, an exception may occur when restoring an RDS for MySQL DB instance to a specified point in time.

  • RDS for MySQL does not support restoration to the original DB instance. If you intend to restore to the original DB instance, restore to a new DB instance first and then change the IP address to that of the original DB instance.

Restoring a DB Instance

  1. Log in to the management console.
  2. Click in the upper left corner and select a region and a project.
  3. Click in the upper left corner of the page and choose Databases > Relational Database Service.

    Figure 1 Relational Database Service

  4. On the Instances page, click the target DB instance.
  5. In the navigation pane on the left, choose Backups & Restorations. On the displayed page, click Restore to Point in Time.
  6. Select the restoration date and time range, enter a time point within the selected time range, and select a restoration method. Then, click OK.

    • Create New Instance

      The Create New Instance page is displayed.

      • The DB engine and version of the new DB instance are the same as those of the original DB instance and cannot be changed.
      • Other settings are the same as those of the original DB instance by default and can be modified. For details, see Buying a DB Instance.

  7. View the restoration result. The result depends on which restoration method was selected:

    • Create New Instance

      A new DB instance is created using the backup data. The status of the DB instance changes from Creating to Available.

      The new DB instance is independent from the original one. If you need read replicas to offload read pressure, create one or more for the new DB instance.

      After the new DB instance is created, a full backup will be automatically triggered.

Restoring Multiple DB Instances at a Time

Only users with the batch restoration permission can restore data to a specified time point in batches. You can contact customer service to apply for the required permission.

  1. Log in to the management console.
  2. Click in the upper left corner and select a region and a project.
  3. Click in the upper left corner of the page and choose Databases > Relational Database Service.

    Figure 2 Relational Database Service

  4. On the Instances page, select target DB instances and choose More > Restore above the DB instance list.

    Only RDS for MySQL DB instances support batch restoration.

  5. In the displayed dialog box, set a single, unified restoration time points, or select different time points for different DB instances.

    Figure 3 Batch restoration

  6. Click Next to confirm the information.
  7. Click OK to submit the batch restoration task.
  8. If you have enabled operation protection, click Send Code in the displayed Identity Verification dialog box and enter the obtained verification code. Then, click OK.

    Two-factor authentication improves the security of your account and cloud product. For details about how to enable operation protection, see the Identity and Access Management User Guide.

Follow-up Operations

After the restoration is successful, you can log in to the DB instance for verification.