Database Backup (DBS) provides features such as single-table restoration, geo-redundancy, full backup, incremental backup, and long-term archiving for Redis instances.
|SQL file backup||DBS logically backs up data in the JSON format.|
|Geo-redundancy||DBS can back up a Redis 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 Redis 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 a single table, a single database, multiple databases, or an entire Redis instance.|
|Backup speed limit||DBS allows you to limit the backup speed to reduce the negative impact of backup operations on database performance.|
|Single-table restoration||DBS allows you to restore a single table without the need to restore the entire Redis instance. This way, the restoration time is reduced.|
An instance of Redis 4.0 Standard Edition that uses the master-replica architecture is created. DBS cannot back up Redis instances of earlier versions such as Redis 2.8 Standard Edition or the Redis cluster edition. For more information, see Database engines and features.
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. Valid values:
- ApsaraDB for Redis: backs up an ApsaraDB for Redis instance. You must also set the Redis 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.
- 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 user-created database in an on-premises data center connected to Alibaba Cloud through 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.
The region where the instance that you want to back up resides.This parameter is displayed only when you set the Database Location parameter to ECS-Hosted Database, ApsaraDB for Redis, or No public network IP: Port's self-built database (accessed through the database gateway).
The type of the database that you want to back up. Default value: Redis.
AddressThe 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 when 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>.
The port number that is used to connect to the instance that you want to back up.Default value: 6369.
PasswordThe password of the database account. The password format varies based on the selected account.
- If you use the default account, enter only the password.
The username of the default account is default. If no account has a username of default, the username of the default account is the instance ID, such as r-bp10noxlhcoim2****.
- If you use a custom account, the format of the password is
<Username>:<Password>. The default account can also use the password in this format to connect to the database. For example, if the username of the custom account is
testaccountand the password is
Rp829dlwa, you must enter
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.
- 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 back up an entire database, the permission data and stored procedures are also backed up.
- 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.
Specifies whether to enable incremental backup.
This parameter is displayed only when 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 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. If you set the Incremental Backup parameter to Enable in the previous step, you must also configure the lifecycle for an incremental backup set. For more information about the lifecycle of backup sets, see How do I manage the lifecycle rules of backup sets?
- 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.
What to do nextRestore a Redis database
- Q: What can I do if no Redis instance is available when I configure a backup schedule?
A: DBS allows you to back up Redis instances only of Redis 4.0 Standard Edition that uses the master-replica architecture. DBS cannot back up Redis instances of earlier versions such as Redis 2.8 Standard Edition or the Redis cluster edition. Check the version and specifications of your Redis instance.