PITR: Restoring a DB Instance to a Point in Time

Scenarios

You can restore an instance 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 80 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 plus the incremental backup 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 80 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.
To restore DB instances to a point in time in batches, you must contact customer service to request required permissions.
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, submit a service ticket.
Constraints on restoring data to the original DB instance:
- Restoring to the original DB instance will overwrite all existing data and passwords, and the DB instance will be unavailable during the restoration.
Constraints on restoring data to an existing DB instance:
- Restoring to an existing DB instance will overwrite data and passwords on it and cause the existing DB instance to be unavailable.
- The selected DB instance must use the same DB engine and same major version as the original DB instance, and its minor version cannot be earlier than that of 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, the task cannot be delivered.
If SQL throttling is enabled for the DB instance, different constraints apply to different restoration scenarios:
- Restoration to a new instance: In RDS for MySQL 5.7, the original SQL throttling rules become invalid. In RDS for MySQL 5.6 and 8.0, the SQL throttling rules of the original instance are retained.
- Restoration to the original instance: The SQL throttling rules of the original instance are restored to the state when the backup was created.
- Restoration to an existing instance: In RDS for MySQL 5.7, all SQL throttling rules of the target instance become invalid. In RDS for MySQL 5.6 and 8.0, the rules of the original instance will overwrite those of the target instance.

Supported Storage Types

If you restore data to your original instance, the storage type of the instance does not change. If you restore data to a new instance or an existing instance other than the original one, the storage types supported are listed in Table 2.

**Table 2** Supported storage types
Original Storage Type	Restore To	New Storage Type
Cloud SSD	New instance and existing instance other than the original instance	Cloud SSD Extreme SSD
Extreme SSD	New instance and existing instance other than the original instance	Cloud SSD Extreme SSD

Restoring a DB Instance to a Point in Time

Click in the upper left corner and select a region.
Click in the upper left corner of the page and choose Databases > Relational Database Service.
On the Instances page, click the target instance name.
In the navigation pane on the left, choose Backups & Restorations.
In the upper right corner of the page, choose Restore to Point in Time > Restore Instance.
Select the restoration date and time range, enter a time point within the selected time range, and set Restoration Method to Create New Instance. 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.
On the displayed page, set required parameters and click Buy.
- 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 an RDS for MySQL DB Instance.
View the restoration result.

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.

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

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

Click in the upper left corner and select a region.
Click in the upper left corner of the page and choose Databases > Relational Database Service.
On the Instances page, click the target instance name.
In the navigation pane on the left, choose Backups & Restorations.
In the upper right corner of the page, choose Restore to Point in Time > Restore Instance.
Select the restoration date and time range, enter a time point within the selected time range, set Restoration Method to Restore to Original, select the confirmation check box, and click Next.

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 the Identity and Access Management User Guide.
Confirm the information and click OK.
View the restoration result.

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.

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

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

Click in the upper left corner and select a region.
Click in the upper left corner of the page and choose Databases > Relational Database Service.
On the Instances page, click the target instance name.
In the navigation pane on the left, choose Backups & Restorations.
In the upper right corner of the page, choose Restore to Point in Time > Restore Instance.
Select the restoration date and time range, and enter a time point within the selected time range.
Set Restoration Method to Restore to Existing, select the confirmation check box, select an existing instance, and click Next.

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 the Identity and Access Management User Guide.
Confirm the information and click OK.
View the restoration result.

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 Viewing a Task.

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

Restoring Multiple DB Instances at a Time

Click in the upper left corner and select a region.
Click in the upper left corner of the page and choose Databases > Relational Database Service.
On the Instances page, select target DB instances and choose More > Restore above the DB instance list.
In the displayed dialog box, set a unified restoration time point, or select different time points for different DB instances.

Figure 1 Batch restoration
Click Next to confirm the information.
Click OK to submit the batch restoration task.
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.