This topic describes how to configure a backup schedule in Database Backup (DBS). When you configure a backup schedule, you can specify the database or table to be backed up, backup frequency, storage method, and backup cycle.

Prerequisites

  • A backup schedule is purchased. For more information, see Purchase a backup schedule.
  • An account of the database to be backed up is prepared, and the required permissions on the database account are obtained. For more information, see Account permissions.
  • A backup gateway is installed on the server of the database to be backed up if you want to perform a physical backup. For more information, see Add a backup gateway.
    Note To check whether a backup gateway is installed, go to the Backup Gateways page in the DBS console.

Procedure

This topic describes only a general procedure for configuring backup schedules for MySQL data. The specific configuration procedure varies based on database types. For more information about configuration examples for different database types, see Backup and restore scenarios.

  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. On the Backup Schedules page, 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. Then, 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. DBS generates a backup schedule name. We recommend that you set a descriptive name that is easy to identify. Backup schedule names do not have to be unique.

    Backup Source Information Backup Mode

    The method that is 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 Other parameters.
    Instance Region

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

    If you set the Database Location parameter to POLARDB Instance or ECS-Hosted Database, select 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 that is used to encrypt the backup data. Valid values:
    • Non-encrypted
    • SSL-encrypted: Secure Sockets Layer (SSL) is used at the transport layer to encrypt network connections and enhance the security and integrity of communication data. However, SSL increases the response time.

      Before you set this parameter to SSL-encrypted, make sure that SSL is enabled for the ApsaraDB RDS for MySQL instance. For more information, see Enable SSL encryption.

    This parameter is displayed only when you back up a MySQL database.
    Backup Destination Information Backup Storage Type The type of storage that is used to back up data. Valid values:
    • DBS Storage (recommended): Backup data is stored in DBS without requiring you to create storage space. You are charged based on the volume of your data that is stored in DBS. For more information about the billing method, see Storage fees.

      To reduce storage costs, we recommend that you use subscription storage plans. For more information, see Use storage plans.

    • OSS For User: You must create a bucket in the Object Storage Service (OSS) console in advance. For more information, see Create buckets.
    Note In this example, set this parameter to DBS Storage (recommended). If you set this parameter to OSS For User, you must set the OSS Bucket Name parameter.
    Storage Encryption The method that is used to encrypt the stored data. Valid values:
    • Encrypted (recommended): DBS uses AES-256, one of the advanced encryption standard ciphers, to encrypt the stored data.

      The server-side encryption feature is used in OSS. When you upload an object to a bucket for which server-side encryption is enabled, 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 displayed 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 type 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 it to the Selected section. Then, click Next.
    Move databases or tables
    Note
    • If you selected Logical Backup when you purchased a backup schedule, DBS allows you to back up a single table, a single database, multiple databases, or an entire database instance.
    • If you selected Physical Backup when you purchased a backup schedule, you must back up an entire database instance.
    If you back up an entire database instance, the permission data and stored procedures are also backed up.
  6. In the Configure Backup Time step, set the parameters that are described in the following table. Then, 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 set this parameter to 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.
    Incremental 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?.

    Backup network speed limit

    The limit on the network bandwidth. You can set the limit based on your needs. Default value: 0, which indicates that the network bandwidth is unlimited.

    This parameter is displayed only when you back up a MySQL database.

  7. In the Edit Lifecycle step, configure the lifecycle for full backup data in the Configure Full Data Backup Lifecycle section.
    Note If you set the Incremental Backup parameter to Enable in Step 6, you must configure the lifecycle for incremental backup data.
  8. After the configurations are 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 plans and Restore a database.

References of API operations