Restore backup data from an RDS SQL Server instance to an existing instance or a new instance. Common use cases include recovering from accidental data changes and querying historical data snapshots.
This topic covers restoring data to an instance in the same region. To restore data across regions or to a self-managed SQL Server database, see Restoration solution overview.
Restore paths
Two restore paths are available. Choose based on your goal:
| Goal | Restore path | Cost impact |
|---|---|---|
| Restore databases to an existing instance quickly, without incurring additional infrastructure costs | Restore to an existing instance | No additional instance fee |
| Restore databases to an isolated copy for analysis, or to an instance with a different configuration | Restore to a new instance | New instance billed separately |
Limitations
| Limitation | Details |
|---|---|
| Data archiving to OSS | Only databases present in the backup set (non-archived) are restored. Databases archived to OSS are excluded from the restored instance. |
| Serverless instances | Backup data from Serverless instances can only be restored to new Serverless instances. Restoring to an existing instance is not supported. |
| RDS SQL Server 2008 R2 (premium performance local disk) | Not supported. Restore data through a temporary instance instead. |
| Transparent Data Encryption (TDE) | After TDE is enabled, backup data can be restored to a new instance, but restoring to an existing instance is not supported. |
Restore to an existing instance
Restore selected databases to any compatible instance in the same region, including the source instance. No new instance is created; billing is unchanged.
Compatibility requirements
| Requirement | Constraint |
|---|---|
| Database version | The target instance version must be greater than or equal to the source instance version. |
| Instance series | Restoring from a higher series to a lower series is not supported. Series from highest to lowest: Cluster Edition > High-availability Edition > Basic Edition. |
| Instance type | Supported combinations: same type to same type, General-purpose to Dedicated, and Dedicated to General-purpose. |
Restore databases to an existing instance
Go to the Instances page. In the top navigation bar, select the region where the instance resides, then click the instance ID.
In the left navigation pane, click Backup and Restoration, then click Restore.
In the dialog box, select Restore to Existing Instance and click OK.
Configure the following parameters and click OK.
ImportantYou cannot overwrite an existing database during a restore. If a database name conflicts with an existing name in the target instance, the restore task fails. Modify the database name to a unique name before retrying. When the restored name differs from all existing databases in the target instance, a new database is created without affecting existing data.
Parameter Description Restore Method By Backup Set: Restores the data in the selected backup set. By Time: Restores to any point in time within the log backup retention period, based on the most recent full backup and incremental backups. Restoring a specific incremental backup is not supported. View or modify the log backup retention period as needed. Restore Time Visible when Restore Method is set to By Time. Select the point in time to restore to. Backup Set Visible when Restore Method is set to By Backup Set. Select the backup set to restore. More Backup Sets Select this option if the target backup set does not appear in the Backup Set list. Destination Instance Name Select the target instance. All instances in the current region under the current Alibaba Cloud account are listed by default, including the source instance. Use the search box to filter if the list is large. NoteSnapshot backups can only be restored to instances that have snapshot backup enabled. Backups from shared instances cannot be restored to General-purpose or Dedicated instances, and vice versa.
Databases to Restore Select the databases to restore (some or all). The original database name is used by default. The restored database name must be unique within the target instance and can only contain letters, numbers, underscores ( _), and hyphens (-).Track progress in Task Center. Click Task Center in the upper-right corner and filter by Task Type = Clone Instance.
Restore to a new instance
Restore selected databases to a newly provisioned instance by backup set or point in time. A separate instance fee applies. Billing starts after the instance is created.
If the original instance is no longer needed after the restore, release or unsubscribe from it to avoid ongoing charges.
Restore databases to a new instance
Go to the Instances page. In the top navigation bar, select the region where the instance resides, then click the instance ID.
In the left navigation pane, click Backup and Restoration, then click Restore.
In the Select Restore Method dialog box, select Restore to New Instance and click OK.
On the Database Restoration page, configure the following parameters.
Parameter Description Billing Method Subscription: Prepaid billing, suitable for long-term use. Longer subscription periods receive higher discounts. Pay-as-you-go: Postpaid billing charged by hour, suitable for short-term use. Restoration Method By Backup Set: Restores the data in the selected backup set. By Point in Time: Restores to any point in time within the log backup retention period, based on the most recent full backup and incremental backups. Restoring a specific incremental backup is not supported. View or modify the log backup retention period as needed. Database All: Restores all databases. Some: Restores specific databases; enter database names separated by commas. NoteIf snapshot backup is enabled on the instance, only All is supported.
Edition Available editions vary by region and database version. See supported editions or refer to the console. Storage Type Select ESSD (Enterprise SSD) or premium performance disk. See Storage type introduction. Zone of Primary Node Select the zone for the primary node. The Basic Edition has only one node and one zone. Deployment Method Multi-zone Deployment (recommended): Primary and secondary nodes are in different zones within the same region, providing cross-zone disaster recovery. Single-zone Deployment: Both nodes are in the same zone. NoteZone performance differences within the same region are minimal. If a zone shows Insufficient, select a different zone. The Basic Edition supports Single-zone Deployment only.
Zone of Secondary Node Available when Deployment Method is set to Multi-zone Deployment. The Basic Edition has no secondary node. Instance Type Available types vary by region and database version. See supported instance types or refer to the console. Storage Capacity Must be greater than or equal to the source instance's storage capacity. Check the source instance's capacity on its Basic Information page. Storage capacity includes data space, system file space, log file space, and transaction file space. Click Next: Instance Configuration and configure the following parameters.
Parameter Description Network Type Only virtual private cloud (VPC) is supported. Create a VPC and vSwitch as needed. Make sure the RDS instance and the ECS instance you want to connect are in the same VPC to enable internal network communication. Resource Group The resource group for the new instance. Create a resource group as needed. Click Next: Confirm Order.
Review the Parameter Configuration, select Quantity and Subscription Duration (for Subscription instances), click Confirm Order, and complete payment. The new instance appears in the instance list. Instance creation takes 1–10 minutes. Refresh the page to check the status.
Connect to the new SQL Server instance and verify the restored databases and tables.
API reference
To restore data programmatically, use the RecoveryDBInstance API.
FAQ
What's next
Restoration solution overview — Cross-region restore and restore to self-managed databases