Help Center/ Relational Database Service/ User Guide/ Working with RDS for MySQL/ Data Restorations/ Restoring Data to RDS for MySQL/ Restoring a DB Instance to a Point in Time
Updated on 2024-10-14 GMT+08:00
View PDF
Share

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.

Function Description

Table 1 Function description

Item

Description

Restoration scope

The entire instance

Instance data after restoration

The instance data after restoration is consistent with that in the full backup file plus the incremental backup file used for the restoration.

  • Restoring data to a new instance creates an instance with the same data as that generated by that time point.
  • Restoring data to the original or an existing instance will overwrite the instance data.

Restorable time point

Any time point within the retention period after the earliest full backup is generated

Scenario
  • Restoration to a new instance
  • Restoration to the original instance
  • Restoration to an existing instance other than the original one

Configurations for restoring to a new instance
  • The DB engine and engine version of the new instance are the same as those of the original instance.
  • Other parameters need to be reconfigured.

Time required

The time required depends on how much data there is in the instance. The average restoration speed is 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.
  • When you restore data to a new DB instance, large transactions in the original DB instance backup may cause a restoration failure. If the restoration fails, contact customer service.
  • Constraints on restoring data to the original DB instance:
    • Restoring to the original DB instance will overwrite data on it and cause the DB instance to be unavailable during the restoration.
  • Constraints on restoring data to an existing DB instance:
    • Restoring to an existing DB instance will overwrite data on it and cause the existing DB instance to be unavailable during the restoration.
    • To restore backup data to an existing DB instance, the selected DB instance must use the same DB engine and the same or a later version than the original DB instance.
    • Ensure that the storage space of the selected DB instance is greater than or equal to the storage space of the original DB instance. Otherwise, data will not be restored.

Restoring a DB Instance

  1. Log in to the management console.
  2. Click in the upper left corner and select a region.
  3. Click in the upper left corner of the page and choose Databases > 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.

    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. For details about how to enable operation protection, see Identity and Access Management User Guide.

    • 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.
    • Restore to Original
      1. Select "I acknowledge that after I select Restore to Original, data on the original databases will be overwritten and the original DB instance will be unavailable during the restoration." and click Next.
      2. Confirm the information and click OK.
    • Restore to Existing
      1. Select "I acknowledge that restoring to an existing DB instance will overwrite data on the instance and will cause the existing DB instance to be unavailable during the restoration. Only DB instances that can be used as target instances for the restoration are displayed here. Eligible instances must have the same DB engine type, version, and at least as much storage as the instance being restored.
      2. Select an existing instance and click Next.
      3. Confirm the information and click OK.

  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.

    • Restore to Original

      On the Instances page, the status of the DB instance changes from Restoring to Available.

      A new restoration time range is available. There will be a difference between the new and original time ranges. This difference reflects the duration of the restoration.

      After the restoration is complete, a full backup will be automatically triggered.

    • Restore to Existing

      On the Instances page, the status of the DB instance changes from Restoring to Available.

      You can view the detailed progress and result of the task on the Task Center page. For details, see Task Center.

      After the restoration is complete, 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.
  3. Click in the upper left corner of the page and choose Databases > 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 1 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. For details about how to enable operation protection, see Identity and Access Management User Guide.

Follow-up Operations

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

FAQs

How Can I Restore Data If No Backup Is Available?

Parent Topic: Restoring Data to RDS for MySQL