How do I back up a PolarDB for MySQL database? - Database Backup

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

Usage notes

Before you back up incremental data of a PolarDB for MySQL database, make sure that the binary logging feature is enabled for the database. By default, the binary logging feature is disabled. For more information about, see Enable binary logging.

Create a backup schedule

For more information, see Create 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 based on which DBS backs up and restores PolarDB for MySQL databases, see Database engines and features.

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 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, Logical Backup is selected.
	Database Location	The location of the database that you want to back up. Select PolarDB from the drop-down list.
	Instance Region	The region in which the source database instance resides.
	Database Type	The type of the database that you want to back up. Default value: MySQL.
	PolarDB Instance ID	The ID of the PolarDB for MySQL database that you want to back up.
	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.
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 data. 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.
Start 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. If you enable incremental backup, make sure that the binary logging feature is enabled for the PolarDB for MySQL database that you want to back up. For more information, see Enable binary logging. 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. You can specify the limit based on your business requirements. Default value: `0`, which indicates that the network bandwidth is not limited.

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

Related operations

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 MySQL database from a logical backup.
You can call the CreateBackupPlan operation to create a backup schedule. You can also call the CreateAndStartBackupPlan operation to create, configure, and start a backup schedule. For more information, see CreateBackupPlan or CreateAndStartBackupPlan.
You can modify the backup source and backup objects of a backup schedule. You can also modify the backup strategies of a backup schedule such as the backup time and backup retention policy. For more information, see Manage a backup plan.
You can check the fees that may be charged for a backup schedule. For more information, see Billing FAQ.
To reduce costs, you can pause a backup schedule that you do not need. For more information, see Pause or start a backup schedule.

FAQ

Q: What do I do if a backup schedule for a PolarDB for MySQL database fails the precheck on the binary logging feature?
A: The precheck fails because the binary logging feature is disabled for the PolarDB for MySQL database. You can enable the binary logging feature for your database in the PolarDB console. For more information, see Enable binary logging.