Create a backup schedule

A backup schedule in Data Disaster Recovery automatically backs up a database instance on a recurring basis. Each schedule covers one database instance and one backup method. You can create a subscription backup schedule in the Data Management (DMS) console or call API operations to create one.

Note

Only subscription backup schedules can be created in the DMS console. Pay-as-you-go backup schedules are not supported. However, the data archiving feature in DMS automatically creates a pay-as-you-go backup schedule and charges based on the amount of data backed up. For details, see Backup fees.

Prerequisites

Before you begin, make sure you have:

An Alibaba Cloud account with access to the DMS console V5.0
A database instance to back up (ApsaraDB RDS, PolarDB, self-managed, or other supported database types)
Sufficient permissions to purchase and configure backup schedules

Choose a backup method

The backup method determines what gets backed up and how. Choose before you start — this setting cannot be changed after purchase.

Dimension	Physical backup	Logical backup
Supported sources	Self-managed databases only (not ApsaraDB RDS)	ApsaraDB RDS instances, self-managed databases in data centers, self-managed databases on Elastic Compute Service (ECS) instances
What it backs up	Database files at the OS level	Database objects: tables, indexes, and stored procedures
Backup granularity	Entire database instance	Fine-grained (specific databases and tables)
Speed	Faster backup and restoration	Slower than physical backup
Disaster recovery	Supports sandbox instances for emergency recovery	Not available

For guidance on selecting the right method, see Select a backup method and Logical backup, physical backup, and snapshot.

Procedure

Log on to the DMS console V5.0.
In the top navigation bar, choose Security and Disaster Recovery (former DBS) > Data Disaster Recovery (DBS) > Backup Plan.

Note
If the DMS console is in simple mode, click the icon in the upper-left corner and choose All Features > Security and Disaster Recovery (former DBS) > Data Disaster Recovery (DBS) > Backup Plan.
On the Backup Schedules page, click Create Schedule in the upper-right corner.

Configure the following parameters, then click Buy Now in the lower-right corner.

Important

If the databases or tables to back up have unreasonable table schemas, large tables, or large fields, a low-specification tier may not have enough resources to complete the backup. Select a higher specification tier to avoid backup failures.

Parameter	Description
Product Type	The type of product to purchase. Select Backup Schedules. Only subscription billing is available in the DMS console.
Region	The region where backup data is stored. To keep backup data in the same region as the source database, select the same region. To enable geo-redundancy for stronger disaster recovery, select a different region — for example, to back up a database in the China (Beijing) region to the China (Shanghai) region, select China (Shanghai). Cross-region storage may incur additional fees.
Data Source Type	The database engine of the source database. For ApsaraDB RDS for MySQL, self-managed MySQL, or PolarDB for MySQL, select MySQL. For a full list of supported engines, see Supported database types and features.
Specification	The performance tier for backup and restoration. Physical backup supports five tiers: micro, small, medium, large, and xlarge. Logical backup supports seven tiers: micro, small, medium, large, xlarge, 2xlarge, and 4xlarge. The xlarge and higher tiers have no upper limit on backup data volume. For production databases, select xlarge or large to ensure fast backup and restoration. For non-critical workloads, a lower tier is sufficient. See Select the backup method and backup schedule specifications.
Backup Method	Physical Backup or Logical Backup. See the comparison table above. This setting cannot be changed after purchase.
Storage Size	No storage capacity needs to be specified at purchase. Storage is billed based on actual usage. For large backup volumes, purchase a storage plan to offset storage fees for built-in storage. For billing details, see Billing FAQ.
Resource Group	The resource group to assign this backup schedule to. Select the default resource group or a custom one.
Quantity	The number of backup schedules to purchase. Each schedule backs up one database instance of one database type. To back up multiple instances or different database types, purchase separate schedules.
Subscription Duration	The subscription period for the backup schedule.

On the Confirm Order page, review the order details, accept the terms of service, and click Pay.

After payment completes, the new backup schedule appears on the Backup Schedules page.

FAQ

Do I need a storage plan?

It depends on where backup data is stored. If the backup uses the built-in storage pool of Data Disaster Recovery, a storage plan is more cost-effective than pay-as-you-go pricing — higher-tier plans offer larger discounts. See Use storage plans.

If the backup writes to an Object Storage Service (OSS) bucket or a self-managed Apsara File Storage NAS file system, no storage plan is needed — built-in storage fees do not apply.

Do I need a network plan?

Only if geo-redundancy is enabled through the ApsaraDB RDS console. Cross-region backup generates network traffic fees billed on a pay-as-you-go basis, and a network plan offsets those fees at a lower rate. Higher-tier plans offer larger discounts. See Use network plans.

If the backup source is an ApsaraDB RDS instance, a self-managed database on ECS, a self-managed database in a data center, or a database on a third-party cloud, Data Disaster Recovery does not charge network traffic fees. Data transfer occurs over the Internet or through Express Connect, VPN Gateway, or Smart Access Gateway (SAG) that you configure. No network plan is needed.

Can I change the backup method after purchase?

No. The backup method (physical or logical) is locked at purchase. To switch methods, purchase a new backup schedule with the desired method.

Does backup affect database performance?

Yes. Running a backup task consumes database resources. Schedule backups during off-peak hours to minimize impact. For more information, see What is the impact of backup on databases?

References

Supported database types and features — check whether your database is supported and what backup granularity is available
Select the backup method and backup schedule type — guidance on choosing the right specification tier
Logical backup, physical backup, and snapshot — detailed definitions and differences between backup methods