This topic describes how to use Database Backup (DBS) to back up a read-only ApsaraDB RDS instance.
Backup of read-only ApsaraDB RDS instances
|DBS-based data backup||Description|
|Incremental backup||Not supported. Read-only ApsaraDB RDS instances do not provide binary logs. Therefore, DBS cannot perform incremental backup on these instances.|
- A read-only ApsaraDB RDS instance is created. For more information, see Create a read-only ApsaraDB RDS for MySQL instance.
- The instance is deployed in a virtual private cloud (VPC). For more information, see the Network types section of the "Change the network type of an ApsaraDB RDS for MySQL instance" topic.
- A backup schedule is purchased. For more information, see Purchase a backup schedule.
- An account is created for the database that you want to back up, and the required permissions are granted to the database account. For more information, see Account permissions.
DBS supports only logical backup of ApsaraDB RDS instances, and does not support physical backup of ApsaraDB RDS instances.
The following section describes how to configure a backup schedule to back up a read-only ApsaraDB RDS instance. A read-only ApsaraDB RDS for MySQL instance is used as an example.
- 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.
- 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.
- In the Configure Backup Source and Destination step of the Configure Backup Schedule wizard, configure the backup source and destination.
Then, click Next in the lower-right corner of the page. The following table describes the 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. 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 source database. In this example, Express Connect DB/VPN Gateway/Intelligent Gateway is selected. Database Type The type of the source database. In this example, MySQL is selected. Peer VPC The VPC in which the source read-only instance is deployed. Address The endpoint used to connect to the source database.Note In this example, you can only enter an IP address. You can view the internal endpoint of the read-only ApsaraDB RDS instance in the ApsaraDB RDS console, and then ping the internal endpoint on your on-premises machine to obtain the IP address. Port Number
The port used to connect to the source database.
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.
The password of the database account.
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.
Backup Destination Information Backup Storage Type The type of storage that is used to store the backup data. Valid values:
Note In this example, select DBS Storage (recommended). If you select OSS For user, you must set the OSS Bucket Name parameter.
- 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.
Storage Encryption The method that is used to encrypt the stored data. Valid values:
- Encrypted: DBS uses AES-256, one of the advanced encryption standard ciphers, to encrypt the
stored data. This is the recommended encryption method.
The server-side encryption feature is used in Object Storage Service (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.
- KMS Encrypted
- 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.
- 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 use logical backup, 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 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, set 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. 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.
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.
Specifies whether to enable incremental backup. In this example, Disable is selected. Incremental backup cannot be enabled for read-only instances.
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: Mbit/s. You can set the limit based on your business requirements. Default value: 0, which indicates that the network bandwidth is not limited.
This parameter is displayed only if you set the Database Type parameter to MySQL.
- In the Edit Lifecycle step, configure the lifecycle for full backup data in the Configure Full Data Backup Lifecycle section.
- After the 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.