Data Management:Create a backup from the backup plan list

• To check whether Data Disaster Recovery supports backup and restore for your database and learn about the granularity of backup and restore for different databases, see Supported database types and features.

• To learn about backup plan specifications or get recommendations on choosing a specification, see How to choose a backup method.

• To understand the differences between logical backup and physical backup, see Logical backup, physical backup, and snapshots.

1. Log on to Data Management DMS 5.0.

2. In the top navigation bar, choose Security and disaster recovery (DBS) > Data Disaster Recovery (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 disaster recovery (DBS) > Data Disaster Recovery (DBS) > Backup Plan.

3. Click the Create Schedule button in the upper-right corner to go to the purchase page.

4. Configure the following parameters and click Buy and Start in the lower-right corner.

   Configuration	Description
   Product Type	Select Backup Plan. Note The DMS console does not support creating pay-as-you-go backup plans.
   Backup Plan Region	Select the region where you want to store backup data. Note Single-region backup: Select the same region as your database. Cross-region backup (geo-redundancy): Select a different region from your database for stronger disaster recovery, but additional fees may apply. For example, to back up a database in China (Beijing) to China (Shanghai), purchase a backup plan in the China (Shanghai) region.
   Data Source Type	Select the type of the database you want to back up. Note If your data source is RDS MySQL, a self-managed MySQL database, or PolarDB for MySQL, select MySQL. For guidance on selecting a data source type, see Supported database types and features.
   Specification	A higher specification provides better backup and restore performance. Available specifications include the following: micro (entry-level), small (low-end), medium (mid-range), large (high-end), and xlarge (high-end with no traffic limit). If your database instance (for example, a production database) requires high-performance backup and restore, we recommend purchasing an xlarge or large specification for faster operations. If backup and restore speed is not critical, calculate and choose the most cost-effective specification. For more information, see Guidelines for selecting backup methods and backup plan specifications. If the databases and tables that you want to back up involve issues such as unreasonable table schemas, large tables, or large fields, and you select a low-specification backup schedule type, the resources of the backup schedule may be insufficient to back up the databases or tables. In this case, backup exceptions occur. To prevent backup exceptions, we recommend that you select a high-specification backup schedule type.
   Backup Method	The following backup methods are supported: Physical backup: Supports only self-managed databases, not RDS instances. This method backs up database files at the operating system level. Physical backup and restore are typically faster than logical backup and restore and support rapid recovery. Logical backup: Supports RDS instances, on-premises databases, and ECS self-managed databases. This method backs up database objects such as tables, indexes, and stored procedures, enabling fine-grained backup and restore at the database or table level. Note For information about the definitions of and differences between logical backup and physical backup, see Logical backup, physical backup, and snapshot and Select a backup method.
   Storage Space	You do not need to select a capacity during purchase. The system charges based on the actual amount of data stored. Note If you back up a large amount of data, we recommend that you purchase a backup instance storage plan provided by DBS to offset the storage fees of built-in DBS storage for the backup schedule. For more information about how to purchase a storage plan, see the FAQ section of this topic. For information about fees that may be incurred for a backup schedule, see Billing FAQ.
   Resource Group	Configure a resource group. Select the default or a custom resource group to simplify backup plan management.
   Quantity	Select the quantity as needed. Note One backup plan can back up only one database instance. To back up multiple instances, create multiple backup plans. For example, to back up RDS MySQL instance A and RDS MySQL instance B, purchase two backup plans. One backup plan supports only one database type. To back up both a self-managed SQL Server database and a self-managed MySQL database, purchase two backup plans.
   Subscription Duration	Select the subscription duration for the backup plan.

5. On the Confirm Order page, verify the order details, read and select the Service Agreement, and click Pay.

   After successful payment, go to the Backup Plans page to view your new backup plan.

Procedure

This example uses an RDS MySQL logical backup plan to illustrate the configuration process. Steps may vary slightly for other database types.

1. Find the target backup plan ID and click Configure Backup Schedule in the Actions column.

2. On the Configure Backup Source and Destination page, configure the backup source and destination, then click Next in the lower-right corner.

   In the Backup Source Information section, set Backup Method to Logical Backup, select RDS Instance for Database Location, choose the Instance Region and RDS Instance ID, enter the Database Account and Password, select Non-encrypted Connection or SSL Secure Connection for Connection Method, click Test Connection to verify connectivity, and check I understand and agree to the compliance commitment above. In the Backup Destination Information section, select DBS Storage (Recommended) for Backup Destination Storage Type and Built-in Encryption for Storage Method.

3. On the Edit Backup Objects page, move the desired databases and tables from the source to the Selected box, then click Next.

   Note

   • Logical backup: You can select specific databases or tables for full backup. Some databases support multi-database, single-database, or single-table selection. Incremental backup, if supported, includes all incremental data by default and does not allow per-table selection.

   • Physical backup: Only entire database instances can be backed up.

4. On the Configure Backup Time page, set the backup schedule and other options, then click Next in the lower-right corner.

5. On the Edit Lifecycle page, enter the retention period for full backup data.

   Note

   If you enabled Incremental Backup in the previous step, you must also configure the retention period for incremental backup data.

6. After completing the configuration, click Precheck in the lower-right corner.

7. After the Precheck dialog box shows that precheck passed, click Start Task.

   Note

   • When the backup plan Status changes to Running, the backup plan is configured successfully.

   • If the backup plan fails or reports an error, contact support in the customer service DingTalk group (ID: 35585947).

Notes

• When restoring a database to an RDS instance in a different region, the target RDS instance must have a public endpoint.

  For example, if your backup plan is in China (Hangzhou) and you want to restore data to an RDS instance in China (Beijing), the RDS instance in China (Beijing) must have a public endpoint.

• Restore time depends on the backup plan specification and the size of the database to restore. Higher specifications yield faster restores, and larger databases take longer to restore.

Procedure

1. Find the target backup plan ID and click Manage in the Actions column.

2. On the Configure Task page, click Restore Database in the upper-right corner.

3. On the Set Time Restored To page, set the Set Time Restored To and Restore Target Database, then click Next.

   Note

   • Restore configuration varies slightly by database engine.

   • Data Disaster Recovery supports restoring MySQL and SQL Server databases directly to a new RDS instance without requiring you to create the instance in advance.

4. On the Configure Objects to Restore page, configure the following settings and click Precheck in the lower-right corner.

   Configuration	Description
   Conflict Handling	By default, Conflict Handling is set to Rename on Object Name Conflict. For example, if a table named job_info already exists during restore, the system renames the new table to job_info_dbs_<restore job ID>_<timestamp>.
   Restore Objects	Select the databases or tables to restore from the Source Database Objects list and move them to the Selected Database Objects list. Note Some databases support single-table or single-database restore granularity, which reduces the amount of data restored and shortens RTO (Recovery Time Objective). For details on supported restore granularity, see Supported database types and features.

5. After the Precheck dialog box shows Precheck Passed, click Start Task.

   You can view the restore progress on the Restore Tasks tab on the left.

   The restore job list shows the job status and detailed progress, including Full Schema Pre-Restore Progress, Full Data Restore Progress, Incremental Log Restore Progress, and Full Schema Post-Restore Progress. When all progress indicators reach 100%, the job status changes to Completed.

   Note

   • Restore time depends on the backup plan specification and database size. Higher specifications yield faster restores.

   • If you choose to restore to a new instance, the system takes about 5–10 minutes to create the new RDS instance. After a successful restore, you can find the new RDS instance in the RDS console. Alternatively, click the restore job ID and then click the RDS instance name in the Basic Information section to be redirected to the RDS console automatically.