Database Backup (DBS) provides features such as geo-redundancy, long-term archiving, and single-table restoration for MySQL instances. This topic describes how to use DBS to back up an ApsaraDB RDS for MySQL or self-managed MySQL instance.
| 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. |
| Backup data query | DBS allows you to use SQL statements to query data in backup sets without the need to restore backup data. For more information, see Overview. |
| Geo-redundancy | DBS can back up a MySQL instance to an Object Storage Service (OSS) bucket across regions. DBS allows you to restore the backup data to a MySQL instance in the source, the destination, or a different region. |
| Long-term archiving | DBS can retain your backup data for up to ten years. After ten years, 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 MySQL instance. This way, the restoration time is reduced. When you configure the objects to restore, select the table that you want to restore. For more information, see Restore a MySQL database from a logical backup. |
Create a backup schedule
For more information, see Purchase a backup schedule.
Configure a backup schedule
- Log on to the DBS console.
- In the left-side navigation pane, click Backup Schedules. On the Backup Schedules page, select a region in the upper-left corner.
- Find the ID of 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 of the Configure Backup Schedule wizard, 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. The default value of this parameter is the backup method that you selected when you purchased the backup schedule. In this example, Logical Backup is selected.
Database Location The location of the instance that you want to back up. Valid values: - RDS Instance: backs up an ApsaraDB RDS instance. You must also set the RDS Instance ID parameter.
- ECS-Hosted Database: backs up a database hosted on an Elastic Compute Service (ECS) instance. You must also set the ECS Instance ID and Port Number parameters.
- POLARDB Instance: backs up a PolarDB for MySQL instance. You must also set the POLARDB Instance ID parameter.
- User-Created Database with Public IP Address <IP Address:Port Number>: backs up a self-managed database by using its public IP address. You must also set 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 set the Peer VPC parameter, you must configure a VPC for the database instance. For more information about the configurations, see 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 set the Gateway instance ID parameter, you must configure a database gateway for the database instance. For more information about the configurations, 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 resides.
This parameter is displayed only if you set the Database Location parameter to RDS Instance, POLARDB Instance, 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.
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 Instance, 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.Database Account The username of the account that is used to connect to the source database. 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 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 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 instance 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: 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 RDS instance before you configure the backup schedule. For more information, see Enable SSL encryption.
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. 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, and only the Standard storage class is supported.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 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 back up a single table, a single database, multiple databases, or an entire database instance. 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 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 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. 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.
Note If 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 ApsaraDB RDS for MySQL databases. 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, 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 needs. Default value: 0, which 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 When the state of the backup schedule changes to Running, the backup schedule takes effect.