Restore the data of an ApsaraDB RDS for SQL Server instance

Restore the data to an existing RDS instance

You can restore the data of your RDS instance to the original RDS instance or to another existing RDS instance. During this process, you can specify to restore some or all of the databases that are created on your RDS instance. In addition, you can specify to restore the data from a backup set or to a specific point in time.

1. Go to the Backup and Restoration page.
   1. Log on to the ApsaraDB for RDS console. In the left-side navigation pane, click Instances. In the top navigation bar, select the region where your RDS instance resides.
      
   2. Find your RDS instance and click its ID. In the left-side navigation pane, click Backup and Restoration.
2. Click Restore.
3. Select Restore to Existing Instance and click OK.
   
4. Configure the following parameters and click OK.
   

   Parameter	Description
   Restore Method	By Time: allows you to restore the data to a specific point in time. The specified point in time must be within the log backup retention period. For more information about how to view or change the log backup retention period, see Back up an ApsaraDB RDS for SQL Server instance. By Backup Set: allows you to restore the data from a full or incremental backup set.
   Restore Time	Select the point in time to which you want to restore the data. This parameter appears only when you set the Restore Method parameter to By Time.
   Backup Set	Select the backup set from which you want to restore the data. This parameter appears only when you set the Restore Method parameter to By Backup Set.
   Instance	Select the destination RDS instance to which you want to restore the data. By default, ApsaraDB RDS displays all the RDS instances that are created within your Alibaba Cloud account and reside in the selected region. These displayed RDS instances include the original RDS instance whose data you want to restore. Note The destination RDS instance can run a higher SQL Server version than the original RDS instance. If the original RDS instance belongs to the shared instance family, you cannot restore the data of the instance to a general-purpose or dedicated RDS instance. Similarly, if the original RDS instance belongs to the general-purpose or dedicated instance family, you cannot restore the data of the instance to a shared RDS instance. If ApsaraDB RDS displays a large number of RDS instances, you can enter a keyword in the Instance field to search for the required destination RDS instance.
   Databases to Restore	Select the databases that you want to restore. By default, ApsaraDB RDS displays and selects all the databases that are created on the original RDS instance. If you want to restore all the data of the original RDS instance, select all the databases. If you want to restore one or more databases, select only the required databases. Specify the names that you want to use for the selected databases on the destination RDS instance. By default, the original names of the selected databases are retained. Note The names of the selected databases on the original RDS instance cannot be the same as those of the existing databases on the destination RDS instance.

   Note

   • If a selected database on the original RDS instance has the same name as an existing database on the destination RDS instance, you must specify a New Database Name for the selected database.
   • The value of the New Database Name parameter can contain only lowercase letters, digits, underscores (_), and hyphens (-).

Restore the data to a new RDS instance

You can restore the data of your RDS instance to a new RDS instance. This process was previously known as instance cloning. During this process, you can specify to restore the data from a backup set or to a specific point in time. If you restore the data from a backup set, you can restore some or all of the databases whose data is included in the backup set.

You must pay for the new RDS instance. The required fee is the same as the amount that you must pay for a new RDS instance. If you no longer require the original RDS instance after the restoration, we recommend that you immediately release or unsubscribe from the instance. For more information, see Release or unsubscribe from an ApsaraDB RDS for SQL Server instance.

1. Go to the Backup and Restoration page.
   1. Log on to the ApsaraDB for RDS console. In the left-side navigation pane, click Instances. In the top navigation bar, select the region where your RDS instance resides.
      
   2. Find your RDS instance and click its ID. In the left-side navigation pane, click Backup and Restoration.
2. Click Restore.
3. In the dialog box that appears, select Restore to New Instance and click OK.
4. On the Restore Database (Previously Clone Instance) page, configure the following parameters.

   Parameter	Description
   Billing Method	Subscription: A subscription instance is an instance that you can subscribe to for a specified period of time and pay for up front. For long-term use, the subscription billing method is more cost-effective than the pay-as-you-go billing method. You can receive larger discounts for longer subscription periods. Pay-As-You-Go: A pay-as-you-go instance is charged per hour based on your actual resource usage. The pay-as-you-go billing method is suitable for short-term use. If you no longer require your pay-as-you-go instance, you can release the instance to reduce costs.
   Restore Mode	By Time: allows you to restore the data to a specific point in time. The specified point in time must be within the log backup retention period. For more information about how to view or change the log backup retention period, see Back up an ApsaraDB RDS for SQL Server instance. By Backup Set: allows you to restore the data from a backup set. Note The By Time option appears only when the log backup feature is enabled. You can restore some or all of the databases that are created on the original RDS instance.
   Database	Specify whether you want to restore some or all of the databases that are created on the original RDS instance. If you select Part, you must manually enter the names of the databases that you want to restore. In addition, you must separate the database names with commas (,).
   Edition	Basic: The database system consists of only one RDS instance. Computing is separated from storage to increase cost-effectiveness. High-availability: The database system consists of one primary RDS instance and one secondary RDS instance. These RDS instances work in the high availability architecture. Cluster: The database system consists of one primary RDS instance, one secondary RDS instance, and up to seven read-only RDS instances. You can create read-only RDS instances to scale up the read capability of the database system. Note The available RDS editions vary based on the selected region and database engine version. For more information, see Overview of ApsaraDB RDS editions.
   Zone	A zone is an independent physical location within a region. The Zone of Primary Node parameter specifies the zone to which the primary RDS instance belongs. The Zone of Secondary Node parameter specifies the zone to which the secondary RDS instance belongs. You can select the Single-zone Deployment or Multi-zone Development method. Single-zone Deployment: If you select this deployment method, the Zone of Primary Node and the Zone of Secondary Node are the same. Multi-zone Development: This is the recommended deployment method. If you select this deployment method, the Zone of Primary Node and the Zone of Secondary Node are different. This allows you to provide zone-level disaster recovery. You need only to specify the Zone of Primary Node, ApsaraDB RDS automatically allocates the Zone of Secondary Node. Note After the RDS instance is created, you can view information about the RDS instance and its secondary RDS instance on the Service Availability page. If you select the RDS Basic Edition, the database system consists of only one primary RDS instance and supports only the single-zone deployment method.
   Instance Type	General-purpose (Entry-level): belongs to the general-purpose instance family. A general-purpose instance exclusively occupies the allocated memory and I/O resources. However, it shares CPU and storage resources with the other general-purpose instances that are deployed on the same server. Dedicated Instance (Enterprise-level): belongs to the dedicated instance family. A dedicated instance exclusively occupies the allocated CPU, memory, storage, and I/O resources. The dedicated host instance family is the top configuration of the dedicated instance family. A dedicated host instance exclusively occupies all the CPU, memory, storage, and I/O resources of the server where it is deployed. Dedicated: A dedicated cluster exclusively occupies all the resources on a VM or physical host. The permissions to manage hosts in a dedicated cluster can be authorized to you. This allows you to create multiple database instances on a host. For more information, see Add a host. Note Each instance type supports a specific number of CPU cores, memory capacity, maximum number of connections, and maximum IOPS. For more information, see Primary instance types.
   Capacity	The storage capacity that the RDS instance has available to store data files, system files, binary log files, and transaction files. The storage capacity increases in increments of 5 GB. Note The dedicated instance family supports exclusive allocations of resources. Therefore, the storage capacity of each instance type with local SSDs in this family is fixed. For more information, see Primary instance types.

5. Click Next: Instance Configuration.
6. Configure the following parameters.

   Parameter	Description
   Network Type	Classic Network: the traditional type of network. VPC: the recommended type of network. A virtual private cloud (VPC) is an isolated virtual network that provides higher security and better performance than the classic network. If you select the VPC network type, you must also specify the VPC parameter and the vSwitch of Primary Node parameter. Note The RDS instance must have the same network type as the ECS instance that you want to connect. If the RDS and ECS instances both have the VPC network type, these instances must also reside in the same VPC. Otherwise, these instances cannot communicate over an internal network.
   Resource Group	The resource group to which the new RDS instance belongs.

7. Click Next: Confirm Order.
8. Confirm the settings in the Parameters section, specify the Purchase Plan and Duration parameters, read and select Terms of Service, click Pay Now, and then complete the payment. You must specify the Duration parameter only when the new RDS instance uses the subscription billing method.

Restore the data to the original RDS instance by using a temporary RDS instance

For more information, see Restore the data of an ApsaraDB RDS for SQL Server instance by using a temporary RDS instance.

Related operations