Data Management:Logically back up and restore an ApsaraDB RDS for SQL Server database

Usage notes

You cannot configure two or more backup schedules for an ApsaraDB RDS for SQL Server database. Otherwise, restoration exceptions occur.

Create a backup schedule

For more information, see Create a backup schedule.

Configure a backup schedule

The following section describes how to configure a backup schedule to logically back up an ApsaraDB RDS for SQL Server database.

1. Log on to the Data Management (DMS) console V5.0.

2. In the top navigation bar, choose Security and Specifications (DBS) > Disaster Recovery for Data (DBS) > Backup Plan.

   Note

   If you use the DMS console in simple mode, move the pointer over the icon in the upper-left corner of the DMS console and choose All Features > Security and Specifications (DBS) > Disaster Recovery for Data (DBS) > Backup Plan.

3. On the Backup Schedules page, find the backup schedule that you want to configure and click Configure Backup Schedule in the Actions column.

4. In the Configure Backup Source and Destination step, configure the backup source and destination, and click Next in the lower-right corner of the page.

   

   Section	Parameter	Description
   N/A	Schedule Name	The name of the backup schedule. Data Disaster Recovery automatically generates a backup schedule name. We recommend that you enter a descriptive name that is easy to identify. Backup schedule names do not need to be unique.
   Backup Source Information	Backup Mode	The method that is used to back up data. By default, the backup method that you select when you purchase the backup schedule is used. In this example, Logical Backup is used.
   	Database Location	The ApsaraDB RDS instance on which the source database is deployed. Select RDS Instance.
   	Instance Region	The region in which the source database resides.
   	RDS Instance ID	The ID of the ApsaraDB RDS instance on which the source database is deployed.
   	Database Account	The username of the account that is used to connect to the source database. The account must have permissions to back up the database. For more information, see Required permissions for different types of database accounts. Note For ApsaraDB RDS databases, read-only permissions are required for backup, and read/write permissions are required for backup and restoration.
   	Password	The password of the account that is used to connect to the source database. Note After you enter the username and password of the database account, click Test Connection next to the password to check whether the information of the source database is valid. If the specified parameters are valid, the "Test Passed" message is displayed. If the "Test Failed" message is displayed, click Check next to Test Failed. Modify the information of the source database based on the check results.
   	Compliance warranty regarding cross-border data transfers	Read and agree to the compliance commitment by selecting the check box.
   Backup Destination Information	Backup Storage Type	The storage type of the backup data. Valid values: DBS Storage (recommended): Backup data is stored in Data Disaster Recovery without the need to create an Object Storage Service (OSS) bucket. You are charged based on the volume of your data that is stored in Data Disaster Recovery. For more information about the billing method, see Pricing. OSS For User: You must create a bucket in the OSS console in advance. For more information, see Create buckets. Note In this example, DBS Storage (recommended) is selected. If you select OSS For User, you must configure the OSS Bucket Name parameter. Only the Standard storage class is supported. If you want to store a large amount of data, we recommend that you purchase a subscription storage plan to offset Data Disaster Recovery built-in storage fees. Data Disaster Recovery storage plans are more cost-efficient than the pay-as-you-go billing method.
   	Storage Encryption	The method that is used to encrypt the stored data. Valid values: Encrypted (recommended): AES-256 is used to encrypt the stored data. The server-side encryption feature is used in OSS. When you upload an object to a bucket for which server-side encryption is enabled, OSS encrypts and stores the object. When you download the encrypted object from OSS, OSS decrypts the object and returns the decrypted object to you. Non-encrypted: Backups are not encrypted.

5. In the Edit Backup Objects step, find the database or table that you want to back up in the Available section. Click the rightwards arrow to add the selected database or table to the Selected section. Then, click Next.

   Note

   • Data Disaster Recovery allows you to back up a single table, a single database, or multiple databases. You can click Select All in the lower-left corner of the Available section to select all databases. The supported backup objects vary based on the database types. For more information, see Supported database types and features.

   • By default, a backup schedule cannot be used to back up a database that is created after the backup schedule is created. To back up the database, you can add the database to the backup schedule on the Configure Task page of the backup schedule. For more information, see Modify backup objects.

6. In the Configure Backup Time step, set the parameters that are described in the following table and click Next.

   Parameter	Description
   Full-scale Backup Frequency	The frequency of the backup schedule. Valid values: Periodic Backup and Single Backup. Note If you select Periodic Backup, you must configure the Full Data Backup Recurrence and Start At parameters.
   Full Data Backup Recurrence	The days of the week on which Data Disaster Recovery runs the backup schedule. You can select one or more days of a week. Select at least one day of the week.
   Start At	The start time of the backup. We recommend that you set a point in time within off-peak hours. Example: 01:00. Note If a previous full data backup is not finished at the start time of the next backup, Data Disaster Recovery skips the next backup.
   Incremental Backup	Data Disaster Recovery does not support incremental backup for SQL Server databases.
   Maximum Concurrent Threads for Full Data Backup	The maximum number of concurrent threads available for a full backup. You can set this parameter to adjust the backup speed. For example, you can reduce the number of backup threads to minimize impacts on the database.

7. In the Edit Lifecycle step, configure the lifecycle for full backup data in the Configure Full Data Backup Lifecycle section.

   Note

   The backup set can be retained for a minimum of seven days and a maximum of 3,650 days. After the retention period expires, the backup set is automatically deleted.

8. After the preceding configurations are complete, click Precheck in the lower-right corner of the page.

9. If the Precheck Passed message appears, click Start Task.

   Note

   • If the state of the backup schedule changes to Running, the backup schedule takes effect.

   • If an exception or error occurs when you start the backup schedule, troubleshoot the exception or error at the earliest opportunity. For more information, see How do I fix errors for an abnormal backup schedule? If your issue persists after you use the solution that is provided in the preceding topic, contact technical support in the DingTalk group (ID: 35585947).

Restore an ApsaraDB RDS for SQL Server database

Related operations

• You can call the CreateBackupPlan operation to create a backup schedule. You can also call the CreateAndStartBackupPlan operation to create, configure, and start a backup schedule. For more information, see CreateBackupPlan or CreateAndStartBackupPlan.

• You can modify the backup source and backup objects of a backup schedule. You can also modify the backup strategies of a backup schedule such as the backup time and backup retention policy. For more information, see Manage a backup schedule.

• You can check the fees that may be charged for a backup schedule. For more information, see Billing FAQ.

• To reduce costs, you can pause a backup schedule that you do not need. For more information, see Pause or start a backup schedule.