All Products
Search
Document Center

PolarDB:Use DBS for logical backup

Last Updated:Jan 17, 2026

PolarDB for MySQL supports logical backups with Data Disaster Recovery (DBS). This topic describes how to configure a logical backup using DBS.

Applicability

You must create a backup plan. For more information, see Create a backup plan.

Note

When you purchase the plan, set Database Type to MySQL and Backup Method to Logical Backup.

Pricing

When you use Data Disaster Recovery to back up data, DBS bills you based on the volume of backup data. For more information, see Backup storage costs.

Procedure

Configure the backup plan

  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 2023-01-28_15-57-17.png 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. On the Backup Schedules page, find the backup schedule that you want to configure and click Configure Backup Schedule in the Actions column.

    image.png

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

    image

    Category

    Configuration

    Description

    None

    Backup Plan Name

    The name of the backup schedule. DBS 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 Method

    Defaults to the backup method you selected when you purchased the plan. In this example, it is logical backup.

    Location of Database

    The location of the database instance to be backed up. Select PolarDB.

    Instance Region

    The region in which the source database instance resides.

    Database Type

    The default option is MySQL.

    PolarDB Instance ID

    Select the ID of the PolarDB for MySQL instance that you want to back up.

    Database Account

    Enter the database account. This account must have the required permissions to back up the database. For more information, see Account permissions.

    Password

    The password of the account that is used to connect to the database that you want to back up.

    After you enter the username and password of the database account, click Test Connection next to the password to check whether the information about the database that you want to back up 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 about the database that you want to back up 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 Destination Storage Type

    The storage type for the backup data. The following options are supported:

    • DBS Storage (Recommended): You do not need to create a bucket. Data is automatically stored in DBS Storage. You are charged based on the amount of data stored. For more information about billing, see Billing items (DMS).

    • OSS For User: You need to create a bucket in Object Storage Service (OSS) in advance. For more information, see Create a bucket in the console.

    Note
    • This example uses DBS Storage. If you select User OSS, you must also configure the Object Storage Service (OSS) Bucket Name parameter. Only OSS Standard storage is supported.

    • If you have a large amount of data to store, we recommend that you purchase a DBS storage plan (subscription) to offset the cost of DBS Storage. DBS storage plans are more cost-effective than the pay-as-you-go billing method.

    Storage Method

    Select a storage method. The following options are supported:

    • Encrypted (Recommended): Data is encrypted and stored using the industry-standard Advanced Encryption Standard (AES) 256 algorithm.

      OSS supports server-side encryption. When you upload an object, OSS encrypts the received object and then saves the encrypted object. When you download the object, OSS automatically decrypts it and returns it to you. For more information, see Server-side encryption.

    • Non-encrypted: Encryption is disabled.

  5. On the Edit Backup Objects page, move the databases or tables that you want to back up to the Selected box, and then click Next.

    Note
    • You can back up specific tables, a single database, or multiple databases. You can click Select All in the lower-left corner of the page to select all databases. The backup objects that you can select depend on the database type. For more information, see Supported database types and features.

    • By default, backup jobs do not back up newly created databases. To back up a new database, add it to the backup plan configuration. For more information, see Modify backup objects.

  6. On the Configure Backup Time page, configure the backup time and other settings, and then click Next in the lower-right corner of the page.

    Configuration

    Description

    Full 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 Backup Period

    The days of the week on which DBS runs the backup schedule. You can select one or more days of a week. Select at least one day of the week.

    Full Backup Start Time

    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, DBS skips the next backup.

    Incremental Backup

    Select whether to enable incremental backup. If you enable this parameter, make sure that binary logging is enabled for PolarDB for MySQL. For more information, see Enable binary logging.

    This parameter is displayed only if you set the Full-scale Backup Frequency parameter to Periodic Backup.

    Maximum Number of Parallel Threads for Full 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.

    Backup network speed limit

    The network bandwidth throttling. The default value is 0, which means no speed limit. The value is not limited.

  7. On the Edit Lifecycle page, specify the retention period for full backup data in DBS Storage.

    If you enabled the Incremental Backup feature in the previous step, you must also configure the retention period for the incremental backup data. For more information about the data lifecycle, see How to manage the lifecycle.

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

  9. In the Precheck dialog box, click Start Task after the precheck is successful.

    Note
    • The backup plan is configured when its Status changes to Running.

    • If the backup plan has an abnormal status or reports an error, troubleshoot and fix the issue promptly. For more information, see How to fix an abnormal DBS backup plan. If the issue persists, join the DBS customer consultation DingTalk group (ID: 35585947) for assistance.

FAQ

  • Q: Why can't I find the ID of the backup plan on the Backup Plans page?

    A: The ID of the backup plan appears on the Backup Plans page only after you create it. For more information, see Create a backup plan.

  • Q: Why am I still charged for DBS (pay-as-you-go) after the cluster is released? How do I release a DBS backup plan?

    A: To release a DBS backup plan, see Release or unsubscribe from a backup plan.

  • Q: Why did the "Enable Binlog in Source Database" precheck item fail?

    A: This error occurs because binary logging is not enabled for the PolarDB for MySQL cluster. Log on to the PolarDB console to enable binary logging. For more information, see Enable binary logging.

References

Back up a PolarDB for MySQL database using logical backup