Updated on 2024-10-14 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.

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. A new DB instance is billed based on the instance specifications.
  • RDS for PostgreSQL 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.
  • Constraints on restoring data to an existing DB instance:
    • If you want to restore to an existing DB instance, submit a service ticket to the customer service to apply for the required permissions.
    • Restoring to an existing DB instance will overwrite data on it and cause the existing DB instance to be unavailable.
    • To restore backup data to an existing DB instance, the selected DB instance must be in the same VPC as the original DB instance and must have the same DB engine and the same or later version than the original DB instance.
    • Ensure that the storage space of the selected DB instance is no less than that of the original DB instance. Otherwise, data will not be restored.

Procedure

  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.

    • 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.
      • Storage space of the new DB instance is the same as that of the original DB instance by default and the new instance must be at least as large as the original DB instance.
      • 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 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." and click Next.
      2. Confirm the information and click OK.
      3. 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.
      4. Two-factor authentication improves the security of your account and cloud product. For details about how to enable operation protection, see Identity and Access Management User Guide.
      Figure 1 Restoring data to a point in time

  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 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.

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

Follow-up Operations

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