Database Backup (DBS) provides features such as geo-redundancy, long-term archiving, and single-table restoration for MySQL instances.

Features

Feature Description
Incremental backup

DBS uses incremental log streaming to retrieve binary log files in real time for incremental backup.

Full backup

Logical backups are stored in the Parquet format. Physical backups are stored in the gzip format.

Backup set download

DBS allows you to download backup sets. For more information, see Overview.

Backup data query

DBS allows you to use SQL statements to query data in backup sets without the need to restore backup data. For more information, see Backup set query overview.

Geo-redundancy DBS can back up a MySQL instance to an Object Storage Service (OSS) bucket that is created in the destination region. DBS allows you to restore the backup data to a MySQL instance in the source, the destination, or a different region.
Long-term archiving

DBS can retain your backup data for up to ten years. After ten years, DBS transfers backup sets to Archive Storage.

Fine-grained backup

DBS allows you to back up a single table, a single database, multiple databases, or an entire MySQL instance.

Backup speed limit

DBS allows you to limit the backup speed to reduce the negative impact of backup operations on database performance. For more information, see How do I change the maximum backup speed?.

Single-table restoration

DBS allows you to restore a single table without the need to restore the entire MySQL instance. This way, the restoration time is reduced.

When you configure the objects to restore, select the table that you want to restore. For more information, see Restore the logical backup of a MySQL database.

Create a backup schedule

For more information, see Purchase a backup schedule.

Note When you purchase a backup schedule, set the Database Type parameter to MySQL and set the Backup Method parameter to Logical Backup.

Configure the backup schedule

  1. Log on to the DBS console.
  2. In the left-side navigation pane, click Backup Schedules. On the Backup Schedules page, select a region in the upper-left corner.
  3. Find the ID of the backup schedule that you want to configure and click Configure Backup Schedule in the Actions column.
    Configure a backup schedule for MySQL data
  4. In the Configure Backup Source and Destination step of the Configure Backup Schedule wizard, configure the backup source and destination, and click Next in the lower-right corner of the page.
    Configure a logical backup schedule for MySQL data
    Table 1. Database parameters
    Section Parameter Description
    N/A Schedule Name

    The name of the backup schedule. Database Backup generates a backup schedule name. We recommend that you set a descriptive name that makes the backup schedule easy to identify. Backup schedule names do not have to be unique.

    Backup Source Information Backup Mode

    The method used to back up data. By default, the backup method that you selected when you purchased the backup schedule is used. In this example, this parameter is set to Logical Backup by default.

    Database Location The location of the database that you want to back up. Valid values:
    • RDS Instance
    • User-Created Database with Public IP Address <IP Address:Port Number>
    • ECS-Hosted Database
    • Express Connect DB/VPN Gateway/Intelligent Gateway
    • POLARDB Instance
    • No public network IP: Port's self-built database (accessed through the database gateway)
    Note In this example, select RDS Instance. If you select other location types, you must set more parameters. For more information, see Table 2.
    Instance Region

    The region where the instance that you want to back up resides.

    RDS Instance ID The ID of the ApsaraDB RDS instance that you want to back up.
    Database Account

    The username of the account used to connect to the database that you want to back up. The account must have specific permissions to back up the database. For more information, see Account permissions.

    Note For ApsaraDB RDS databases, read-only permissions are required for backup, and read and write permissions are required for backup and restoration.
    Password

    The password of the account 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 of the database that you want to back up is correct. If the specified parameters are valid, the Test Passed message appears. If the Test Failed message appears, click Check next to Test Failed. Modify the information about the instance that you want to back up based on the check results.

    SSL Encryption The method used to encrypt the backup data. Valid values:
    • Non-encrypted
    • SSL-encrypted
    Backup Destination Information Backup Storage Type The type of storage used to back up data. Valid values:
    • DBS built-in storage (recommended)
    • OSS For User
    Note In this example, select DBS built-in storage (recommended). If you select OSS for user, you must set the OSS Bucket Name parameter.
    Storage Encryption The method used to encrypt the stored data. Valid values:
    • Encrypted (recommended): The backup data is encrypted.

      The server-side encryption feature of Object Storage Service (OSS) is used. When you upload an object to OSS, 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. For more information, see Server-side encryption.

    • Non-encrypted: The backup data is not encrypted.
    OSS Bucket Name

    The name of the OSS bucket that you want to use to store data.

    This parameter is valid only when you set the Backup Storage Type parameter to OSS for user.

    Table 2. Other parameters
    Section Parameter Description
    Backup Source Information Database Type The engine of the database that you want to back up. Default value: MySQL.
    Gateway instance ID

    The ID of the database gateway.

    Address

    The endpoint used to connect to the database that you want to back up.

    Port Number

    The port used to connect to the database that you want to back up.

    ECS Instance ID

    The ID of the Elastic Compute Service (ECS) instance where the database that you want to back up is deployed.

    Peer VPC

    The virtual private cloud (VPC) where the database that you want to back up is deployed.

    POLARDB Instance ID The ID of the PolarDB for MySQL instance that you want to back up.
  5. In the Edit Backup Objects step, find the database or table that you want to back up and add them to the Selected section. Then, click Next.
    Note DBS allows you to back up a single table, a single database, multiple databases, or an entire MySQL instance. If you back up an entire database, the permission data and stored procedures are also backed up.
  6. In the Configure Backup Time step, configure the backup time and click Next in the lower-right corner of the page.
    Parameter Description
    Full-scale Backup Frequency

    The frequency of the backup schedule. Select Periodic Backup or Single Backup as needed.

    Note If you select Periodic Backup, you must set the Full Data Backup Recurrence and Start At parameters.
    Full Data Backup Recurrence

    The days of the week on which DBS runs the backup schedule. Select at least one day of the week.

    Start At

    The start time of the backup, such as 01:00. We recommend that you set a time during off-peak hours.

    Note If a previous full data backup is not finished at the start time of the next backup, DBS skips the next backup.
    Real-Time Transaction Log Backup

    Specifies whether to enable incremental backup. If you enable incremental backup, make sure that the binary logging feature is enabled for the database that you want to back up.

    Note By default, the binary logging feature is enabled for an ApsaraDB RDS for MySQL database. If you use a self-managed database, you must manually enable the binary logging feature.

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

    Maximum Concurrent Threads for Full Data Backup

    The maximum number of concurrent threads available for a full data backup. You can set this parameter to adjust the backup speed. For example, reduce the number of backup threads to minimize the impact on the database.

    The maximum number of actual concurrent threads varies based on backup schedule specifications. For more information, see How do I change the maximum backup speed?.

  7. In the Edit Lifecycle step, configure the lifecycle for a full data backup in the Configure Full Data Backup Lifecycle section.
    Note If you select Enable for the Real-Time Transaction Log Backup parameter, you must configure the backup time for incremental backup data.
  8. After the configuration is complete, click Precheck in the lower-right corner of the page.
  9. If the Precheck Passed message appears, click Start Task.
    Precheck for the logical backup of MySQL data
    Note When the status of the backup schedule changes to Running, the backup schedule takes effect.
    After data is backed up, you can view the backup schedule or restore the backup data. For more information, see View backup schedules and Restore the logical backup of a MySQL database.