Tair (Redis® OSS-Compatible):Automatic or manual backup

Tair (Redis OSS-Compatible) uses RDB snapshots for data persistence. In-memory data is captured at specific points in time, compressed, and persisted to disk. The backup process does not affect data retrieval performance.

By default, each instance is configured to back up data automatically once a day. You can modify the automatic backup policy to suit your requirements, or create manual backups at any time. Backups are retained for 7 days by default. To keep backup data beyond this period, you can download backup files to your local machine.

Background information

Tair (Redis OSS-compatible) instances use RDB snapshots for data persistence. In-memory data captured at specific points in time is persisted to files on disks. The backup process does not affect data retrieval performance.

Automatic vs. manual backups

The following table compares the two backup methods available for Tair (Redis OSS-Compatible) instances.

Limits

• Only one backup task can run at a time per instance. Wait for the current backup to complete before starting another.

• By default, backups are created from the replica. If the data flashback feature is enabled, backups are created from the primary instead.

• Automatic backups are retained for 7 days and cannot be deleted manually. They are automatically removed when they expire.

• You can create up to 30 manual backups per day per instance. If you exceed this limit, the error Exceeding the daily backup times of this DB instance. is returned. The limit resets after 24 hours and does not affect automatic backups.

• When an instance expires or is released, all backup data is deleted. To preserve your backups, download backup files in advance.

Access the Backup and Recovery page

1. Log on to the console and go to the Instances page. In the top navigation bar, select the region in which the instance that you want to manage resides. Then, find the instance and click the instance ID.

2. Click the instance ID to open the instance details page, and then click Backup and Recovery in the left-side navigation pane.

Configure the automatic backup policy

1. In the upper-right corner, click Backup Settings.

2. In the panel that appears, configure the following parameters:

   • Retention Days: Backup files are retained for 7 days.

   • Backup Cycle: Select one or more days of the week on which to run backups. By default, one backup is created per day.

   • Backup Time: Select a time window (in hours) during which the backup runs. We recommend that you schedule backups during off-peak hours to minimize any potential impact.

     Note

     The time displayed in the console is in the same time zone as your computer.

3. Click OK.

Create a manual backup

1. In the upper-right corner, click Create Backup.

2. In the dialog box that appears, configure Backup Expiration Policy and click OK.

   Only cloud-native instances support custom expiration policies for manual backups. Classic instances do not support this feature. The available options are:

   • Standard (default): The backup follows the same retention rules as the current automatic backup policy.

   • Independent: You set a specific retention period for the backup, ranging from 3 to 730 days.

   • Not expired: The backup never expires and is retained for the lifetime of the instance. This is useful for periodic archival backups -- for example, backing up every Monday or at the start of each month.

   Note

   The expiration time of manual backup data can be extended after creation. You can call the ModifyBackupExpireTime API operation, or update the setting in the console.

Delete a manual backup

For cloud-native instances, you can click the Delete button next to a manual backup to remove it. Automatic backups cannot be deleted manually -- they are automatically removed when they expire.

FAQ

Related API operations

References

• Restore data from a backup to a new instance

• Download backup files

• Data flashback (point-in-time recovery)