Database Backup:Use Database Gateway to back up on-premises databases or private databases in a third-party cloud to Alibaba Cloud

Prerequisites

• A database gateway is created, and the database that you want to back up is added to the database gateway. For more information, see Create a database gateway.

• A backup schedule is purchased, and the logical backup mode is selected for the schedule. For more information, see Create a backup schedule.

Usage notes

• Make sure that the server on which the database gateway is installed can access the Internet. The service port of the server does not need to be open to the Internet. To ensure stable and fast data transmission, make sure that the outbound public bandwidth of the server is at least 10 Mbit/s.

• Make sure that the server on which the database gateway is installed can connect to the database that you want to back up. If the server and the database are deployed in the same internal network, the network latency is minimal.

Billing

Database Gateway is free of charge.

Configure a backup schedule

1. Log on to the DBS console. In the left-side navigation pane, click Backup Schedules. In the top navigation bar, select the region in which you purchase the backup schedule.

2. 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.

3. In the Configure Backup Source and Destination step of the Configure Backup Schedule wizard, configure parameters in the Backup Source Information and Backup Destination Information sections and click Next in the lower-right corner of the page.

   Section	Parameter	Description
   N/A	Schedule 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 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. Select No public network IP: Port's self-built database (accessed through the database gateway). Note If you select No public network IP: Port's self-built database (accessed through the database gateway), cross-region backup is not supported. The region of the source database must be the same as the region of the Object Storage Service (OSS) bucket that you use to store the backup data.
   	Instance Region	The region in which the database that you want to back up resides.
   	Database Type	The type of the database that you want to back up. By default, the database type that you selected when you purchased the backup schedule is used. In this example, this parameter is set to MySQL.
   	Gateway instance ID	The ID of the database gateway.
   	Address	The endpoint that is used to connect to the database. You can obtain the endpoint by performing the following operations: Log on to the Data Management (DMS) console. In the top navigation bar, choose Solution > Database Gateway. On the Gateway List page, find the database gateway that you want to use and click its ID to enter the details page and view the database endpoint and port number. For more information, see Create a database gateway.
   	Port Number	The port number that is used to connect to the database. You can obtain the port number in the DMS console. The default port number of the MySQL database is 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 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 Storage Type	The type of storage that is used to store the backup data. Valid values: DBS Storage (recommended): Backup data is stored in DBS without the need to create an Object Storage Service (OSS) bucket. 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. OSS For User: You must create a bucket in the OSS console in advance. For more information, see Create buckets. Note In this example, DBS Storage (recommended) is selected. If you select OSS For User, you must configure the OSS Bucket Name parameter. Only the Standard storage class is supported. If the volume of data to be backed up is large, we recommend that you purchase subscription storage plans to offset fees. For more information, see Use storage plans. Storage plans are more cost-efficient than the pay-as-you-go billing method.
   	Storage Encryption	The method that is used to encrypt the stored data. Valid values: Encrypted: recommended. DBS uses AES-256 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: DBS does not encrypt the backup data. KMS Encrypted: DBS uses Key Management Service (KMS) to encrypt the backup data. This value is available only if the Backup Storage Type parameter is set to OSS For User.

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

   • If you selected Logical Backup when you purchased a backup schedule, DBS allows you to specify the databases and tables to be backed up during full backups. You can back up a single table, a single database, multiple databases, or an entire database instance for some types of databases during full backups. DBS supports incremental backups only for some types of databases. By default, all the incremental data is backed up during incremental backups.

     • You can click Select All in the lower-left corner of the page to select all databases. The database objects that can be backed up and the backup granularity vary based on the database type. For more information, see Database engines and features.

     • By default, a backup schedule cannot be used to back up a database that is created after the backup schedule is created. To back up the database, you can add the database to the backup schedule on the Edit Backup Objects page of the backup schedule. For more information, see Modify backup objects.

   • If you selected Physical Backup when you purchased a backup schedule, you must back up an entire database instance.

5. In the Configure Backup Time step, configure 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. Valid values: Periodic Backup and Single Backup. Note In scenarios in which incremental data needs to be restored, we recommend that you select Periodic Backup and perform a full backup at least once a week. Otherwise, a large number of binary logs must be replayed during restoration. This process is prone to errors and may result in a prolonged recovery time objective (RTO).
   Full Backup Cycle	The days of the week on which DBS runs the backup schedule. This parameter is required if the Full-scale Backup Frequency parameter is set to Periodic Backup. Select at least one day of the week.
   Full Backup Started At	The point in time at which DBS starts a full backup. This parameter is required if the Full-scale Backup Frequency parameter is set to Periodic Backup. We recommend that you specify a point in time during off-peak hours. Example: 01:00. Note If a previous full data backup is not complete 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 This parameter is displayed only if you set the Full-scale Backup Frequency parameter to Periodic Backup. By default, the binary logging feature is enabled for an ApsaraDB RDS for MySQL instance. If you use a self-managed database, you must manually enable the binary logging feature.
   Maximum Concurrent Threads for Full Data Backup	The maximum number of concurrent threads that are available for a full backup. You can configure this parameter to adjust the backup speed. For example, you can reduce the number of backup threads to minimize impacts 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: MB/s. You can set the limit based on your business requirements. The default value 0 indicates that the network bandwidth is unlimited. Note This parameter is displayed only if 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.

   Note

   If you set the Incremental Backup parameter to Enable in Step 6, you must configure the lifecycle for incremental backup data.

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.

   Note

   • If the state of the backup schedule changes to Running, the backup schedule takes effect.

   • If an exception or error occurs when you start the backup schedule, troubleshoot the exception or error at the earliest opportunity. For more information, see How do I fix errors for an abnormal backup schedule in DBS? If your issue persists after you use the solution that is provided in the preceding topic, contact technical support in the DBS DingTalk group (ID: 35585947).

What to do next

• After a database is backed up, you can view the backup schedule or restore the database. For more information, see View a backup schedule or Restore a database.

• You can also call an API operation to create a backup schedule, or to create, configure, and then start a backup schedule. For more information, see CreateBackupPlan or CreateAndStartBackupPlan.

• For more information about how to modify the backup source, backup objects, or backup policy such as the backup time and backup set retention time of a backup schedule, see Manage a backup plan.

• For more information about fees that may be subsequently incurred by a backup schedule, see Billing FAQ.

• You can pause a backup schedule that you do not need to reduce costs. For more information, see Pause or start a backup schedule.