Restoring from Backup Files to RDS for SQL Server Instances

Scenarios

This section describes how to use an automated or manual backup to restore a DB instance to the status when the backup was created.

Constraints

• Constraints on restoring data to a new DB instance:
  • The time zone of the new DB instance must be the same as that of the original DB instance. Otherwise, data inconsistency may occur.
• Constraints on restoring data to an existing DB instance (other than the original 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 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.
  • The storage space of the selected DB instance must be no less than that of the original DB instance. Otherwise, data will not be restored.
  • The time zone of the selected DB instance must be the same as that of the original DB instance. Otherwise, data inconsistency may occur.
  • DB instances with the TDE function enabled cannot be restored from backups to existing DB instances.

Procedure

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.
4. On the Backups page, locate the target backup and click Restore in the Operation column.

   Alternatively, click the target DB instance on the Instances page. In the navigation pane, choose Backups & Restorations. On the displayed page, locate the backup to be restored and click Restore in the Operation column.

5. In the displayed dialog box, specify required information and click OK.
   1. Select a restoration method.
      • Restore to Existing

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

   2. Select the databases to be restored. You can rename these databases as required. If you do not enter a new name, the original database name will be used.
      

      • The new database names must be different from each other and must be different from the original database names.
      • The new database names cannot contain the following fields (case-insensitive): rdsadmin, master, msdb, tempdb, model, and resource.
      • Each database name consists of 1 to 64 characters. Only letters, digits, hyphens (-), underscores (_), and periods (.) are allowed.

6. View the restoration result. The result depends on which restoration method was selected:
   • Restore to Existing

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

Follow-up Operations

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

Backup data cannot be restored to original RDS for SQL Server DB instances. If you need to restore data to your original DB instance, restore backup data to a new or an existing DB instance and then migrate the backup data to the original instance using DRS or change the floating IP address of the new DB instance to that of the original instance.

FAQs

How Can I Restore Data If No Backup Is Available?