This topic describes how to restore data to a new instance from a full or differential backup set. ## **Background Information** SQL Server provides the following restore methods: * Restore from a backup set: This method allows you to restore an entire instance or specific databases to a new or existing instance from a specified backup set. The data in the restored instance is consistent with the data from the backup file. For more information, see [Restore to a new instance from a backup Set](https://docs.volcengine.com/docs/6899/141474) and [Restore to an Existing Instance from a backup set](https://docs.volcengine.com/docs/6899/1130117). * Restore to a point in time: This method allows you to restore an entire instance or specific databases to a new or existing instance as they were at a specified point in time. The data in the restored instance is consistent with the data at the specified point in time. For more information, see [Restore a new instance to a point in time](https://docs.volcengine.com/docs/6899/153379) and [Restore an existing instance to a point in time](https://docs.volcengine.com/docs/6899/1130119). ## **Billing description** Restoring from a backup set restores data to a new instance by specifying a backup file. Charges apply for the new instance. For more information about instance fees, see [Billing overview](https://docs.volcengine.com/docs/6313/77796). ## **Prerequisites** * An instance has been created and the instance state is **Running**. For detailed operations, see [Create an instance](https://docs.volcengine.com/docs/6899/141335). * The original instance must have at least one full or differential backup. ## **Precautions** * When restoring a specified database to a new instance, note the following: * Restoring system databases and the rdsadmin database is currently not supported. * When the **Node specification** is **2\-core**, you can restore up to 50 databases in a single operation. * When selecting a compatible version for the new instance, you can only choose a version that is the same as or higher than the original instance's compatible version. Lower compatible versions are not supported. ## Procedure 1. Log on to the [RDS for SQL Server console](https://console.volcengine.com/db/sql-server). 2. In the upper\-left corner of the top menu bar, select the target project and region. 3. In the left navigation pane, click **Instances**. 4. On the **Instances** page, click the name of the target instance. 5. On the **Summary** page, click **Backups**. 6. On the **Backups** tab, click **Restore to new instance**. 7. On the **Restore to new instance** page, configure the following parameters. |**Category** |**Parameter** |**Description** | |---|---|---| |**Restore configuration** |**Restore method** |Select **By backup set**. This restores the instance from a specified backup set. The selectable backup sets are determined by the Number of days to retain backup. | ||**Backup set** |Select a target **full backup** or **differential backup** from the dropdown list. | ||**Recovery object** |Select a recovery object as needed. You can select **The entire instance** or **Specify database**, as follows:

* **The entire instance**: when you select this option, all data in the backup set is restored to the new instance.

* **Specify database**: when you select this option, you can restore data at the database level.

tip

When using the Specify database option for data recovery with a 2\-core node specification, you can restore up to 50 databases in a single operation.

You can rename restored databases in the Selected database area. The restored database name can be the same as the original database name or follow the naming conventions below:

Start with a letter and end with a letter or digit.

The length must be between 2 and 60 characters. Consists of letters, numbers, and underscores (_).

You can not use reserved words, such as master, msdb, model, tempdb,resource, rdsadmin, and distribution.

| |**Basic information** |**Instance name** |(Optional) Set an instance name. The naming rules are as follows:

* Can not start with digits or hyphen (\-).

* Can only contain Chinese characters, letters, digits, underscores (_) and hyphens(\-).

* The length must be between 1 and 128 characters.

tip

If you do not enter an instance name, it will be the same as the instance ID.

| ||**Compatible versions** |Select a compatible version for the new instance.

tip

When selecting a compatible version for the new instance, you can only choose a compatible version that is the same as or higher than the original instance's compatible version. Lower compatible versions are not supported. The release year version and product edition of the compatible version shall be no lower than those of the original instance.

Year version: 2019 < 2022

Product edition: Web Edition < Standard Edition < Enterprise Edition

For example:

If the original instance's compatible version is 2022 Standard Edition, you can select 2022 Standard Edition, 2022 Enterprise Edition.

If the original instance's compatible version is 2019 Enterprise Edition, you can select 2019 Enterprise Edition, 2022 Enterprise Edition.

| |**Specification configuration** |**Instance type** |Select an instance type as needed. The supported types are as follows: **High availability**, **Single node edition**, and **Cluster edition**.

* **High Availability**: A classic high\-availability architecture with one primary and one secondary node, suitable for production databases in large and medium\-sized enterprises for scenarios like the internet, IoT, retail e\-commerce, logistics, and gaming. You can select **High availability** as the Instance type when the **Compatible version** is **SQL Server 2019 Standard Edition**, **SQL Server 2022 Standard Edition**.

* **Single node edition**: It adopts a single node deployment architecture. Compared to typical primary and secondary instances, it comprises only one node while offering high cost\-performance ratio. It is suitable for personal learning, micro\-websites, and development and testing environments for small and medium\-sized enterprises. You can select **Single node edition** as the instance type when the **Compatible version** is **SQL Server 2019 Standard Edition**, **SQL Server 2019 Enterprise Edition**, **SQL Server 2019 Web Edition**, **SQL Server 2022 Standard Edition**, **SQL Server 2022 Enterprise Edition**, **SQL Server 2022 Web Edition** or .

* **Cluster**: Features a high\-availability architecture with one primary, one standby, and multiple read\-only nodes. This edition is suitable for production databases in large and medium\-sized enterprises, such as those in the internet, hospitality, and online education industries. You can select **Cluster edition** as the **Instance type** when the **Compatible version** is **SQL Server 2019 Enterprise Edition**, **SQL Server 2022 Enterprise Edition** . | ||**Specification series** |(Optional) If you select the **Include previous generation specifications** radio button, you can choose a specification type that **includes previous generations** from the **Specification type** field below.

tip

For more information about specifications, see Primary instance specifications.

| ||**Specification type** |Select the **Specification type** of the instance. If you click the **Include historical specifications** radio button above, the available **Specification types** are as follows:

* If the **Compatible version** is **SQL Server 2019 Standard Edition**, **SQL Server 2022 Standard Edition** or :

* When the **Instance type** is **High availability** or **Single node edition**, the **Specification type** supports **Exclusive Type**, **General Type**, **Exclusive Type II**, and **General Type II**.

* If the **Compatible version** is **SQL Server 2019 Enterprise Edition**, **SQL Server 2022 Enterprise Edition**or :

* When the **Instance type** is **Cluster Edition**, the **Specification type** supports **Exclusive Type** and **Exclusive Type II**.

* When **Instance type** is set to **Single node edition**, **General type** and **General Type II** are available for **Specification type**.

* If the **Compatible version** is **SQL Server 2019 Web Edition** or **SQL Server 2022 Web Edition**:

* When **Instance type** is set to **Single node edition**, General type and General Type II are available for Specification type**General type** and **General Type II** are available for Specification type.

tip

For more information about each specification type, see Product specification family.

| ||**Node specification** |Configure the node specifications and availability zones for the instance's primary and secondary nodes as needed. The details are as follows:

* **Node specification**: Select the node specification for the primary node from the drop\-down list. The secondary node's node specification is automatically the same as the primary node's.

tip

Node specifications for SQL Server Standard Edition, Enterprise Edition, or Web Edition are from the 4il generation by default.

If you select Include previous generation specifications above, you can select node specifications from the 1ie or 3il specification families.

For more details about node specifications, see Primary instance specifications.

* **Availability zones**: Select the availability zone for the node from the drop\-down list. The availability zone is the geographic location of the node. If an instance has primary and secondary nodes, you can deploy them across different availability zones.

tip

Select an availability zone close to your target users to improve access speed.

The availability zone can not be modified after the instance is created successfully.

| ||**Storage Type** |Currently, only **Extremely\-Fast SSD PL1 Cloud Disk** is supported. | ||**Storage space** |Storage space includes data file space and temporary file space. The storage space of the new instance must be greater than or equal to that of the original instance. Enter a storage space between 20 GiB and 4000 GiB in 10 GiB increments. Select a value based on your business needs. | |**Network configuration** |**VPC** |Select the target VPC from the drop\-down list. You can also click Create VPC on the right to create a new VPC. For detailed instructions, see [Create a VPC](https://www.volcengine.com/docs/6401/69467).

tip

A VPC (Virtual Private Cloud) is an isolated network environment that offers higher security and better performance than a traditional classic network.

| ||**Subnet** |The subnets vary depending on the availability zones selected for the primary and secondary nodes, as follows:

* If the primary and secondary nodes are in the same availability zone, the field is displayed as **Subnet**. Select an available **Subnet** in the VPC from the drop\-down list.

* If the primary and secondary nodes are in different availability zones, the fields are displayed as **Primary node subnet** and **secondary node subnet**. From the drop\-down lists, select a subnet in the VPC for the **primary node** and **secondary node**, respectively.

tip

A subnet is a block of IP addresses within a VPC. All cloud resources in the VPC must be deployed in a subnet. The subnet assigns private IP addresses to cloud resources. For more information, see Create a subnet.

| ||**Allowlist** |(Optional) Associate an allowlist with the instance. Click the allowlist text box to go to the **Associate allowlist** page. On this page, select an allowlist and click **Confirm**. You will return to the **Create instance** page, and the selected allowlist will appear in the allowlist text box.

tip

You can also create a new allowlist on the Associate allowlist page. For more information about creating an allowlist, see Create an allowlist.

An instance can bind a maximum of 100 allowlists.

Click × next to the allowlist to remove it.

If a default allowlist is set for the current account, it will appear in the allowlist box.

| |**Account configuration** |**Super account** |The default is **veyun_user**. | ||**Super user password** |Set the administrator account password. The requirements are as follows:

* It must contain at least three of the following character types: uppercase letters, lowercase letters, numbers, and special characters.

* Special characters are `~!@#$%^&*()-_+=?`.

* It must be 8 to 32 characters long.

* It cannot contain the string `veyun_user` (case\-insensitive). | ||**Confirm password** |Enter the password again. | |**Advanced configuration** |**Time zone** |The only supported option is **(UTC+08:00) Beijing, Chongqing, Hong Kong, Urumqi**. | ||**Instance character set** |Select the character set for the instance database. Supported options include **Chinese_PRC_90_CI_AI**, **Chinese_PRC_BIN**, **Chinese_PRC_BIN2**, **Chinese_PRC_CI_AI**, **Chinese_PRC_CI_AS**, **Chinese_PRC_CS_AS**, **Chinese_Taiwan_Stroke_CI_AS**, **Chinese_Taiwan_Stroke_CS_AS**, **Cyrillic_General_CI_AS**, **Japanese_CI_AS**, **Japanese_CS_AS**, **Latin1_General_100_CI_AS_SC_UTF8, Latin1_General_CI_AS**, **Latin1_General_CS_AS**, **SQL_Latin1_General_CP1_CI_AS**, **SQL_Latin1_General_CP1_CS_AS**, and **Thai_CI_AS**. The default is **Chinese_PRC_CI_AS**.

tip

The instance character set can not be modified after the instance is successfully created.

We recommend keeping the instance character set consistent with the original instance.

Even if you select a case\-sensitive instance character set, creating case\-sensitive databases is not supported. For example, databases named A and a will be treated as the same database.

For more information about the instance character set, see References.

| ||**Project** |Select a project for this instance from the dropdown list. The default project is **default**. You can also click **Create a new project** to create a new project. For detailed instructions, see [Create a new project](https://www.volcengine.com/docs/6649/94336).

tip

A project is a virtual concept that includes a set of resources, users, and roles. Projects allow you to centrally view and manage a group of resources and control the permissions of users and roles on these resources within the project. For more information, see Resource Management.

| ||**Tag** |(Optional) Add tags to the backup instance.

tip

Tags help identify and categorize cloud resources. RDS for SQL Server lets you add tags to instances for classification, simplifying instance searches and resource aggregation. For more information, see Tag overview.

| |**Billing information** |**Billing methods** |Select a billing method as needed. The following billing methods are currently supported:

* **Pay\-as\-you\-go**: Select this option for short\-term use of SQL Server instances. Billing is hourly. You can release the instance when it is no longer needed to save costs.

* **Subscription**: If you plan to use a SQL Server instance for a long term, select the subscription method (one\-time payment), and select the subscription duration in the lower\-left corner of the page. Subscription is more cost\-effective than pay\-as\-you\-go, and the longer the subscription duration, the greater the discount.

tip

If you select pay\-as\-you\-go, ensure that your Volcano Engine account balance is at least 100 CNY. For detailed information on billing, see Billing overview.

| ||**Subscription duration** |Select the subscription duration as needed. Monthly (1 to 9 months) and yearly (1 to 3 years) subscriptions are available.

tip

When you select Subscription as the billing method, you can set the subscription duration.

| ||**Automatic renewal.** |Optionally, enable **auto\-renewal upon expiration**. If enabled, the platform will automatically renew your instance monthly before it expires, and no manual renewal is required. You can also modify the renewal configuration. For details, see [Renewal management](https://www.volcengine.com/docs/6899/170008).

tip

When you select the Subscription billing method, you can configure the subscription duration.

| 8. Click **Confirm order**. 9. Complete the following steps based on the selected billing method. * If the instance's billing method is **Pay\-as\-you\-go**: On the **Confirm Order** page, confirm the order details, select the checkbox to agree to **Service Specific Terms**, **Unsubscribe rules**, and , then click **Buy Now**. * If the instance's billing method is **Subscription**: 1. On the **Confirm Order** page, confirm the order details, read and select **Service Specific Terms**,**Unsubscribe rules ** , and click **Submit Order**. 2. On the **Confirm order Information** page, confirm the order information again, and click **Next**. 3. On the **Submit payment information** page, confirm the payment details, select a payment method, click **Go to Pay**, and follow the prompts to complete the payment and create the instance.