How do I back up MySQL databases by using logical backup? - Database Backup

Database Backup (DBS) provides features such as geo-redundancy, long-term archiving, and single-table restoration for MySQL databases. This topic describes how to use DBS to automatically back up an ApsaraDB RDS for MySQL instance or a self-managed MySQL database.

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.
Geo-redundancy	DBS supports cross-region backup for MySQL databases. DBS allows you to restore the backup data to an ApsaraDB RDS for MySQL instance or a self-managed MySQL database that is deployed in the source, destination, or another region.
Long-term archiving	DBS can retain your backup data for up to 10 years. After the retention period expires, DBS transfers backup sets to Archive Storage.
Fine-grained backup	DBS allows you to back up multiple databases, a single database, or a single table.
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 database instance. This way, the restoration time is reduced. When you configure a restoration task, you can specify a table as the restoration object. For more information, see Restore a MySQL database from a logical backup.

Create a backup schedule

For more information, see Purchase a backup schedule.

Note

When you purchase a backup schedule, set the Data Source Type parameter to MySQL and the Backup Method parameter to Logical Backup.
For information about the granularity of backup and restoration in DBS, see Database engines and features.
In addition to logical backups, DBS also allows you to back up full data, incremental data, and binary logs of self-managed MySQL databases by using physical backup. For more information, see Back up MySQL databases, Back up binary logs of a MySQL database, and Logical backup, physical backup, and snapshot-based backup.

Configure a backup schedule

Log on to the Database Backup (DBS) console.
In the left-side navigation pane, click Backup Schedules. In the top navigation bar, select a region.
On the Backup Schedules page, find the backup schedule that you want to configure and click Configure Backup Schedule in the Actions column.

In the Configure Backup Source and Destination step, configure the backup source and destination, and click Next in the lower-right corner of the page.

Table 1. Parameters
Section	Parameter	Description
N/A	Schedule Name	The name of the backup schedule. DBS automatically generates a backup schedule name. We recommend that you set 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, Logical Backup is used.
	Database Location	The location of the database instance that you want to back up. Valid values: RDS Instance: backs up an ApsaraDB RDS instance. You must also configure the RDS Instance ID parameter. ECS-Hosted Database: backs up a database that is hosted on an Elastic Compute Service (ECS) instance. You must also configure the ECS Instance ID and Port Number parameters. PolarDB: backs up a PolarDB for MySQL cluster. You must also configure the PolarDB Instance ID parameter. User-Created Database with Public IP Address <IP Address:Port Number>: backs up a self-managed database by using the public IP address of the database. You must also configure the Address and Port Number parameters. Express Connect DB/VPN Gateway/Intelligent Gateway: backs up a self-managed database by using a virtual private cloud (VPC). Before you configure the Peer VPC parameter, you must configure a VPC for the database. For more information, see topics such as Back up a self-managed database in a data center connected to Alibaba Cloud over Express Connect to OSS or DBS and Back up a user-created database in an on-premises data center connected to Alibaba Cloud through VPN Gateway or Smart Access Gateway to OSS or DBS. No public network IP: Port's self-built database (accessed through the database gateway): backs up a self-managed database by using a database gateway. Before you configure the Gateway instance ID parameter, you must configure a database gateway for the database. For more information, see Use Database Gateway to back up on-premises databases or private databases on a third-party cloud to Alibaba Cloud.
	Instance Region	The region in which the source database instance resides. Note This parameter is displayed only if you set the Database Location parameter to RDS Instance, PolarDB, ECS-Hosted Database, or No public network IP: Port's self-built database (accessed through the database gateway).
	Database Type	The type of the database that you want to back up. Default value: MySQL. Note This parameter is displayed only if you set the Database Location parameter to User-Created Database with Public IP Address <IP Address:Port Number>, PolarDB, ECS-Hosted Database, Express Connect DB/VPN Gateway/Intelligent Gateway, or No public network IP: Port's self-built database (accessed through the database gateway).
	Address	The endpoint that is used to connect to the instance that you want to back up. Note If network security settings, such as firewall settings, are specified on the server where the instance is deployed, click Set Whitelist to obtain the CIDR blocks of DBS, and then add the CIDR blocks to the whitelist of the server. This allows DBS to access the server. This parameter is displayed only if you set the Database Location parameter to No public network IP: Port's self-built database (accessed through the database gateway), Express Connect DB/VPN Gateway/Intelligent Gateway, or User-Created Database with Public IP Address <IP Address:Port Number>.
	Port Number	The port number that is used to connect to the database that you want to back up. Default value: 3306. Note This parameter is displayed only if you set the Database Location parameter to No public network IP: Port's self-built database (accessed through the database gateway), Express Connect DB/VPN Gateway/Intelligent Gateway, or User-Created Database with Public IP Address <IP Address:Port Number>.
	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. 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 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.
	SSL Encryption	The connection method that is used to transmit the backup data. Valid values: Non-encrypted SSL-encrypted: 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. Note If you want to select SSL-encrypted, you must enable SSL encryption for the ApsaraDB RDS instance before you configure the backup schedule. For more information, see the Step 1: Enable the SSL encryption feature for an RDS instance section of the "Configure the SSL encryption feature" topic.
	Compliance warranty regarding cross-border data transfers	Read the statement of compliance and select Acknowledge and Agree.
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 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. Note In this example, DBS Storage (recommended) is selected. If you select OSS For User, you must configure the OSS Bucket Name parameter, and only the Standard storage class is supported.
Backup Destination Information	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. AES-256 is one of the advanced encryption standard ciphers. The server-side encryption feature is used in OSS. 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.

In the Edit Backup Objects step, find the database or table that you want to back up in the Available section. Click the rightwards arrow to add the selected database or table to the Selected section. Then, click Next.
Note
- DBS allows you to back up a single table, a single database, or multiple databases. You can click Select All in the lower-left corner of the Available section to select all databases. The supported backup objects vary based on the database types. 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 Configure Task page of the backup schedule. For more information, see Modify backup objects.

In the Configure Backup Time step, configure the parameters that are 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 configure 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. You can select one or more days of a week. Select at least one day of the week.
Started At	The start time of the backup. We recommend that you set a point in time within off-peak hours. Example: 01:00. 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. Note Before you enable incremental backup, make sure that the binary logging feature is enabled for the database that you want to back up. 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 if 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 backup. You can set 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.

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 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?
After the preceding configurations are complete, click Precheck in the lower-right corner of the page.
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 backup is complete, you can view the backup schedule or restore the database. For more information, see View a backup schedule or Restore a MySQL database from a logical backup.
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.