Create a backup schedule - Data Management - Alibaba Cloud Documentation Center

You can use the Data Disaster Recovery console or call API operations to create a backup schedule to back up and restore your database. This topic describes how to create a backup schedule in the console.

Usage notes

You cannot create pay-as-you-go backup schedules in Data Disaster Recovery. You can create only subscription backup schedules in Data Disaster Recovery.
Note
If you use the data archiving feature in the Data Management (DMS) console, the system creates a pay-as-you-go backup schedule in Data Disaster Recovery. You are charged for the backup schedule based on the amount of data that is backed up. For more information, see Backup fees.
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.

Procedure

Log on to the DMS console V5.0.
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.
On the Backup Schedules page, click Create Schedule in the upper-right corner to go to the Create Schedule.

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

Parameter	Description
Product Type	The backup schedule that you want to use. Note You cannot create a pay-as-you-go backup schedule in the Dada Management (DMS) console.
Region	The region in which you want to store the backup data. Note Backup in the same region: Select the region in which the database to be backed up resides. Geo-redundancy: Select a region different from that of the database to be backed up. This method provides a better disaster recovery capability but may charge you additional fees. For example, if you want to back up a database from the China (Beijing) region to the China (Shanghai) region, select the China (Shanghai) region.
Data Source Type	The data source type of the database to be backed up. Note If the data source is an ApsaraDB RDS for MySQL instance, a self-managed MySQL database, or a PolarDB for MySQL cluster, select MySQL. For more information about how to select a data source type, see Supported database types and features.
Specification	The backup schedule specifications that you want to use. Higher specifications offer higher backup and restoration performance. Data Disaster Recovery supports the following backup schedule specifications: micro, small, medium, large, and xlarge. The xlarge specification type provides extra large specifications without an upper limit on the amount of backup data. To ensure fast backup and restoration of specific database instances, such as database instances in the production environment, we recommend that you select the xlarge or large specification type. If you do not require high backup and restoration performance, you can select the most cost-effective backup schedule specifications based on your business requirements. For more information, see Select the backup method and backup schedule 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 backup method that you want to use. Valid values: Physical Backup: You can perform a physical backup only on self-managed databases, but not ApsaraDB RDS instances. You can use this method to back up database files in the operating system. In most cases, physical backup and restoration are faster than logical backup and restoration. You can also use a sandbox instance for emergency disaster recovery. Logical Backup: You can perform a logical backup on ApsaraDB RDS instances, self-managed databases in data centers, and self-managed databases hosted on Elastic Compute Service (ECS) instances. You can use this method to back up database objects, including tables, indexes, and stored procedures. Data Disaster Recovery allows you to back up specified databases and tables in a fine-grained way. 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 Size	The storage capacity of the backup schedule that you want to purchase. You do not need to specify the storage capacity when you purchase a backup schedule. You are charged for the amount of your data that is stored in Data Disaster Recovery. Note If you back up a large amount of data, we recommend that you purchase a backup instance storage plan provided by Data Disaster Recovery to offset the storage fees of built-in 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	The resource group that is used by the backup schedule. You can select the default resource group or a custom resource group to facilitate backup schedule management.
Quantity	The number of backup schedules that you want to purchase. Note A backup schedule can be used to back up only one database instance. To back up multiple database instances, you must purchase multiple backup schedules. For example, if you want to back up ApsaraDB RDS for MySQL Instance A and ApsaraDB RDS for MySQL Instance B, you must purchase two backup schedules. A backup schedule can be used to back up only one type of database. To back up multiple types of databases, you must purchase multiple backup schedules. For example, if you want to back up a self-managed SQL Server database and a self-managed MySQL database, you must purchase two backup schedules.
Subscription Duration	The subscription duration for the backup schedule that you want to purchase.

On the Confirm Order page, confirm the order information, read and select the terms of services, and then click Pay.
After you pay for the order, go to the Backup Schedules page to view the new backup schedule.

FAQ

How do I determine whether I need to purchase a storage plan?

You can determine whether to purchase a storage plan based on the following scenarios:

If you store backup data in the built-in storage pool of Data Disaster Recovery, we recommend that you purchase a storage plan to offset the storage fees. By default, you are charged for using the built-in storage pool on a pay-as-you-go basis. Storage plans are more cost-effective than the pay-as-you-go billing method. Storage plans of higher specifications provide larger discounts. For more information, see Use storage plans.
If you configure a backup schedule to back up data to an Object Storage Service (OSS) bucket or a self-managed NAS file system, you do not need to purchase a storage plan because you are not charged storage fees.

How do I determine whether I need to purchase a network plan?

You can determine whether to purchase a storage plan based on the following scenarios:

If you enable geo-redundancy in the ApsaraDB RDS console, we recommend that you purchase a network plan to offset the network traffic fees that are generated for backing up data across regions in the ApsaraDB RDS console. You are charged for the amount of cross-region backup data on a pay-as-you-go basis. Network plans are more cost-effective than the pay-as-you-go billing method. Network plans of higher specifications provide larger discounts. For more information, see Use network plans.
If you back up ApsaraDB RDS instances, self-managed databases hosted on Elastic Compute Service (ECS) instances, self-managed databases in data centers, or databases hosted on third-party cloud services in Data Disaster Recovery, you are not charged network traffic fees. This is because the data is backed up over the Internet or by using Express Connect, VPN Gateway, or Smart Access Gateway that you configure. Therefore, you do not need to purchase a network plan.

Can I create pay-as-you-go backup schedules in Data Disaster Recovery?

You cannot create pay-as-you-go backup schedules in Data Disaster Recovery. You can create only subscription backup schedules in Data Disaster Recovery.

Note

If you use the data archiving feature in the DMS console, the system creates a pay-as-you-go backup schedule in Data Disaster Recovery. You are charged for the backup schedule based on the amount of data that is backed up. For more information, see Backup fees.

Can I change the backup method of a backup schedule from physical backup to logical backup after I purchase the backup schedule?

No, you cannot change the backup method of a backup schedule after you purchase the backup schedule.

Is the performance of a database affected when I use Data Disaster Recovery to back up the database?

When Data Disaster Recovery performs a backup task on a database, the database performance is affected. Therefore, we recommend that you perform backup tasks during off-peak hours. For more information, see What is the impact of backup on databases?

References

For information about whether Data Disaster Recovery supports the backup and restoration of your database and the granularity of database backup and restoration, see Supported database types and features.
For more information about the backup schedule types or how to select a backup schedule type, see Select the backup method and backup schedule type.
For information about the definitions of and differences between logical backup and physical backup, see Logical backup, physical backup, and snapshot.