This topic describes the data restoration methods that are supported by ApsaraDB RDS for SQL Server.
Scenario 1: Restore data in the cloud
Method | Related operation |
Restore data to an existing RDS instance | Note To restore a single database to an existing RDS instance, we recommend that you manually back up the database by following the instructions in Create a manual backup. Then, you can use the manual backup file as the reference point for data restoration. This method helps flexibly roll back data in scenarios such as application version upgrades or releases. |
Restore data to a new RDS instance (previously known as a cloned RDS instance) | |
Restore data from a temporary RDS instance to the original RDS instance (This method is suitable only for RDS instances that run SQL Server 2008 R2 and use Premium Local SSDs.) | |
Restore data across regions | |
Restore data to a self-managed database from backup files | Download backup files by following the instructions in Download data backups and log backups. Then, restore data to the self-managed database from the backup files. |
Scenario 2: Migrate local data to the cloud
For more information, see Overview of data migration methods and SQL Server cloud migration solutions.
| Data source | Incremental migration | Available approaches | Recommended approach |
|---|---|---|---|
| Self-managed SQL Server | Yes | Physical backup via OSS (manual), physical backup via Data Disaster Recovery and DTS, DTS logical migration | Use Data Disaster Recovery and DTS to migrate data based on physical backup files |
| Azure SQL Database | Yes | DTS logical migration, ApsaraDB RDS console end-to-end migration, SQL Server Management Studio (SSMS) migration | ApsaraDB RDS console end-to-end migration or DTS logical migration |
| Azure SQL Managed Instance | — | DTS logical migration, ApsaraDB RDS console end-to-end migration, SSMS migration, physical backup via OSS | — |
| SQL Server on Azure Virtual Machines | — | DTS logical migration, ApsaraDB RDS console end-to-end migration, SSMS migration, physical backup via OSS | — |
| Amazon RDS for SQL Server | Yes | DTS logical migration, ApsaraDB RDS console end-to-end migration, SSMS migration, physical backup via OSS | ApsaraDB RDS console end-to-end migration or DTS logical migration |
| Huawei Cloud RDS for SQL Server | No | Physical backup via OSS (full data only), DTS logical migration (full data only), SSMS migration | Use OSS to manually migrate full backup data |
| TencentDB for SQL Server | Yes | DTS logical migration, physical backup via OSS, SSMS migration | Use DTS for logical migration |
| TencentDB for SQL Server | No | SSMS migration | Use SSMS to perform cloud migration |
| Google Cloud SQL for SQL Server | Yes | DTS logical migration, SSMS migration | Use DTS for logical migration |
For DTS logical migration from Azure SQL Database, Azure SQL Managed Instance, SQL Server on Azure Virtual Machines, Amazon RDS for SQL Server, and Google Cloud SQL for SQL Server, set the SQL Server Incremental Synchronization Mode parameter to Polling and querying CDC instances for incremental synchronization when configuring incremental migration.
When migrating from Huawei Cloud RDS for SQL Server running SQL Server 2008 R2, upgrade the database version before starting the migration. For instructions on how to create and download backup files in Huawei Cloud RDS for SQL Server, refer to the Huawei Cloud documentation.