Database Backup (DBS) provides features such as geo-redundancy, long-term archiving, and distributed backup for PolarDB-X instances.
A PolarDB-X V1.0 instance is created. The data of the PolarDB-X V1.0 instance is stored in an ApsaraDB RDS for MySQL instance whose MySQL version is 5.x.
|SQL file backup||DBS logically backs up data in the JSON format.|
|Backup data query||DBS allows you to query backup data by using SQL statements without the need to restore data. For more information, see Query data in a single backup set.|
|Geo-redundancy||DBS can back up a PolarDB-X instance to an Object Storage Service (OSS) bucket that is deployed in the destination region. DBS allows you to restore the backup data to a PolarDB-X 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.|
|Backup speed limit||DBS allows you to limit the backup speed to reduce the negative impact of backup operations on database performance.|
|Distributed backup||DBS provides the distributed backup feature for backup schedules of the large or xlarge type. This feature allows you to back up and restore multiple nodes at the same time.|
Create a backup schedule
Create a backup schedule. For more information, see Purchase a backup schedule.
Configure the 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. Database 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. By default, the backup method that you select when you purchase the backup schedule is used. In this example, this parameter is set to Logical Backup.
Database Location The location of the database that you want to back up. In this example, this parameter is set to Distributed PolarDB-X Instance. Instance Region
The region where the instance that you want to back up resides.
Database Type The type of the database that you want to back up. In this example, this parameter is set to Polardb-x (original DRDS upgrade). PolarDB-X Instance ID The ID of the PolarDB-X instance where the database that you want to back up is deployed. Database Name
The name of the database that you want to back up.
The username of the account that is used to connect to the database that you want to back up. The account must have specific permissions to back up the database. For more information, see Account permissions.
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 appears. If the Test Failed message appears, 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, set this parameter to DBS Storage (recommended). If you set this parameter to 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: recommended. DBS uses AES-256, one of the advanced encryption standard ciphers,
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: The backup data is not 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, click Next in the lower-right corner of the page. DBS allows you to back up only an entire distributed database instance.
- In the Configure Backup Time step, set 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.
The start time of the backup, such as 01:00. We recommend that you set a time during off-peak hours.Note If a previous full backup is not finished at the start time of the next full backup, DBS skips the next full backup.
Incremental Backup DBS does not support incremental backup for PolarDB-X databases. 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 the impact 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?.
- In the Edit Lifecycle step, configure the lifecycle for a full backup set 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 status of the backup schedule changes to Running, the backup schedule takes effect. You can view the backup task on the Backup Schedules page. For more information, see View backup schedules.