ApsaraDB RDS:Restore SQL Server data

Restoration rules

Procedure

1. Go to the Instances page. In the top navigation bar, select the region in which the RDS instance resides. Then, find the RDS instance and click the ID of the instance.

2. In the navigation pane on the left, click Backup and Restoration, and click Database Restoration.

3. In the dialog box that appears, select Restore To Existing Instance and click OK.

4. Set the following parameters and click OK.

   Parameter	Description
   Restoration Method	By Backup Set: You can restore the data in the selected backup set. By Time: You can set any point in time within the log backup retention period. The system will restore data to the specified point in time based on the most recent full backup and incremental backups (restoration of a specific incremental backup is not supported). You can view or modify the log backup retention period as needed.
   Restoration Time	This parameter is visible when Restoration Method is set to By Time. Select the point in time for the data you want to copy.
   Backup Set	This parameter is visible when Restoration Method is set to By Backup Set. Select the backup set you want to restore.
   More Backup Sets	If you cannot find the target backup set in Backup Set, you can select this option to continue searching.
   Target Instance Name	Select the instance to which you want to restore data. You can restore data to an instance with a higher version. The system displays all instances in the current region under the current Alibaba Cloud account by default, including the current instance. Note Snapshot 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 backups from General-purpose or Dedicated instances cannot be restored to shared instances. If there are too many target instances displayed, you can use the search box to filter them.
   Databases To Restore	Select the databases you want to restore. You can restore some or all databases. The system displays all databases in the instance by default. Set the database name after restoration. The system uses the original database name by default. Note the following: The database name after restoration cannot be the same as an existing database name in the target instance. Otherwise, the restoration task will report an error. Please modify it to a unique database name. When the database name after restoration is different from an existing database name in the target instance, the system will create a new database without overwriting or affecting the existing data in the target instance. The database name after restoration can only contain uppercase and lowercase letters, numbers, underscores (_), and hyphens (-).

5. View the progress of the restoration task.

   The system will generate a restoration task. You can click the button in the upper-right corner and filter Task List page by Task Type as Clone Instance to view the restoration progress.

   

Billing information

Because the data is restored to a new instance, fees for the new instance will be charged. You can view the fee details when creating the instance.

Procedure

1. Go to the Instances page. In the top navigation bar, select the region in which the RDS instance resides. Then, find the RDS instance and click the ID of the instance.

2. In the navigation pane on the left, click Backup and Restoration, and click Database Restoration.

3. In the Select Restoration Method dialog box, select Restore To New Instance and click OK.

4. On the Database Restoration page, set the following parameters.

   Category	Description
   Billing method	Subscription: This is a prepaid billing method that requires payment when you create an instance. It is suitable for long-term requirements and is more cost-effective than the pay-as-you-go billing method. The longer the subscription period, the higher the discount. Pay-as-you-go: This is a postpaid billing method that charges you by hour. It is suitable for short-term requirements. You can release the instance immediately after use to reduce costs.
   Restoration Method	By Backup Set: You can restore the data in the selected backup set. By Time: You can set any point in time within the log backup retention period. The system will restore data to the specified point in time based on the most recent full backup and incremental backups (restoration of a specific incremental backup is not supported). You can view or modify the log backup retention period as needed.
   Database	You can restore all or some databases. If you select Partial, you need to manually enter the database names, separated by commas (,). Note If the instance has enabled snapshot backup, only All databases can be restored, and Partial database restoration is not supported.
   Edition	Different regions and database versions support different editions. Please refer to the actual interface.
   Storage Type	Select enterprise SSD (ESSD) or premium performance disk. For more information, see Storage type introduction.
   Primary Node Zone	Select the zone where the primary node of the instance is located. Note The Basic Edition includes only one node, so there is only one zone.
   Deployment Method	Multi-zone Deployment (recommended): The primary node and secondary node are located in different zones within the same region, providing cross-zone disaster recovery. Single-zone Deployment: The primary node and secondary node are located in the same zone. Note There is no substantial difference between different zones in the same region. The performance of ECS accessing RDS in the same zone is better than accessing RDS in other zones of the same region, but the difference is small. When you select Basic Edition, only Single-zone Deployment is supported. If the upper-right corner of the target zone displays Sold Out, please change to another zone. This parameter is not supported for the Basic Edition.
   Secondary Node Zone	If Deployment Method is set to Multi-zone Deployment, you need to select the zone where the secondary node of the instance is located. Note The Basic Edition includes only one node, so there is no secondary node zone.
   Instance Type	Different regions and database versions support different instance types. Please refer to the actual interface.
   Storage Capacity	The storage capacity of the new instance must be greater than or equal to that of the original instance. You can view the storage capacity of the original instance on the Basic Information page of the RDS instance details page. The storage capacity includes data space, system file space, log file space, and transaction file space.

5. Click Next: Instance Configuration and set the following parameters.

   Category	Description
   Network Type	Currently, only virtual private cloud (VPC) is supported. You can create a VPC and vSwitch as needed. Note Make sure that the RDS instance and the ECS instance you want to connect are in the same VPC. Otherwise, the RDS instance and the ECS instance cannot communicate through the internal network.
   Resource Group	The resource group to which the instance belongs. You can create a resource group as needed.

6. Click Next: Confirm Order.

7. Confirm the Parameter Configuration, select Quantity and Duration (for subscription instances only), click Confirm Order, and complete the payment.

   You can go to the instance list and find the newly created instance based on the creation time. Creating an instance takes about 1 to 10 minutes. Please refresh the page to check.

8. You can connect to the new SQL Server instance and check the restored databases and tables.