Database Backup (DBS) provides features such as remote backup, 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 data query DBS allows you to use SQL statements to query backup sets without the need to restore backup data. For more information, see Overview.
Remote backup 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 five years. After five 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.

Create a backup schedule

For more information, see Purchase a backup schedule.
Note When you purchase a backup schedule, set Database Type to MySQL and set Backup Method.

Configure a 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.
    Select a region
  3. On the Backup Schedules page, click Configure Backup Schedule in the Actions column corresponding to the backup schedule that you purchased.
    Configure a backup schedule for MySQL data
  4. In the Configure Backup Source and Destination step of the Configure Backup Schedule wizard, set the parameters as described in the following table to configure the backup source and destination.
    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. DBS 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. For more information, see Create a backup schedule.
    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 is deployed.
    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.
    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:
    OSS Bucket Name The name of the OSS bucket that you want to use to store data.
    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.
    Database gateway instance ID The ID of the database gateway.
    Address The public 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 lower-right corner of the page, click Next.
  6. In the Edit Backup Objects step, find the database or table that you want to back up in the Available section. Click the right arrow to add the selected database or table to the Selected section. Then, click Next.
    Note If you back up an entire database, the permission data and stored procedures are also backed up.
  7. In the Configure Backup Time step, set the parameters as described in the following table and click Next.
    Parameter Description
    Full-scale Backup Frequency The frequency of the backup schedule. Valid values: Periodic Backup and Single Backup.
    Note If you select Periodic Backup, you must set the Full Data Backup Recurrence and Full Data Backup Start At parameters.
    Full Data Backup Recurrence The days of the week on which DBS runs the backup schedule.
    Full Data Backup Start At The start time of the backup.
    Note If the time required to complete a full data backup is longer than the backup interval, DBS skips the next backup.
    Real-Time Transaction Log Backup Specifies whether to enable incremental backup.
    Maximum Concurrent Threads for Full Data Backup The maximum number of concurrent threads available for a full data backup.
    Note The maximum number of actual concurrent threads varies based on backup schedule specifications.
  8. 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.
  9. After the configuration is complete, click Precheck in the lower-right corner of the page.
  10. If the Precheck Passed message appears, click Start Task.
    Precheck for 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 MySQL databases.