Database Backup (DBS) provides the geo-redundancy feature to support geo-disaster recovery for self-managed databases. This topic describes how to use DBS to configure a geo-redundancy policy for a self-managed database.

In this example, a self-managed MySQL database that resides in the China (Hangzhou) region is backed up to the China (Beijing) region. This topic also provides a reference for you to back up other types of self-managed databases, such as Oracle and SQL Server databases. For more information about the parameter settings for other database types, see Backup and restore scenarios.

Create a backup schedule

When you purchase a backup schedule for geo-redundancy, set the parameters based on the following requirements:
  • Region for Backup Instance: the region in which you want to store the backup data. In this example, select China (Beijing).
  • Data Source Type: the engine of the database to be backed up. In this example, select MySQL.
  • Backup Method: the method that is used to back up data. In this example, select Logical Backup.

For more information, see Purchase a backup schedule.

Configure the backup schedule

  1. Log on to the DBS console. In the left-side navigation pane, click Backup Schedules. In the upper-left corner of the Backup Schedules page, select the region where you purchase the backup schedule. In this example, select the China (Beijing) region.
  2. 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
  3. 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 backup schedule for geo-redundancy over the Internet
    Table 1. 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.
    Database Location The location of the database that you want to back up. In this example, select User-Created Database with Public IP Address <IP Address:Port Number>.
    Database Type The engine of the database that you want to back up. In this example, this parameter is set to MySQL.
    Address The endpoint that is used to connect to the instance that you want to back up.
    Port Number

    The port number that is used to connect to the instance that you want to back up. Default value:3306.

    Database Account

    The username of the account that is 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.

    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 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) encrypts network connections at the transport layer to improve the security and integrity of data in transit. However, SSL increases the network connection response time.

      If you want to select SSL-encrypted, you must enable SSL encryption for the original instance before you configure the backup schedule. In addition, you must upload the root certificate. For more information, see What is SSL Certificates Service?.

    This parameter is displayed only when you set the Database Type parameter to MySQL.
    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.
  4. 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.
    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.
  5. In the Configure Backup Time step, set the parameters that are described in the following table 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 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. For example, you must enable the binary logging feature if MySQL and MariaDB databases are used.

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

    This parameter is displayed only when you set the Database Type parameter to MySQL and MariaDB.
    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. Unit: Mbit/s. You can set the limit based on your needs. Default value: 0, which indicates that the network bandwidth is unlimited.

    The limit on the network bandwidth. You can set the limit based on your needs. This can minimize the impact on the network caused by backup. For example, if you set this parameter to 1, the backup speed does not exceed 1 Mbit/s.

    This parameter is displayed only when you set the Database Type parameter to MySQL.

  6. In the Edit Lifecycle step, configure the lifecycle for full backup data in the Configure Full Data Backup Lifecycle section.
    If you set the Incremental real-time backup parameter to Enable in Step 6, you must configure the lifecycle for incremental backup data. For more information about the lifecycle rules of backup data, see How do I manage the lifecycle rules of backup sets?.
  7. After the configurations are complete, click Precheck in the lower-right corner of the page.
  8. 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 a MySQL database from a logical backup.