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

Tair (Redis OSS-compatible) instances use RDB snapshots for data persistence by capturing in-memory data at a specific point in time, compressing it, and saving it to disk. Backups do not affect read or write performance. By default, instances are backed up once per day. You can modify the automatic backup policy or create manual backups as needed.

Overview

Tair (Redis OSS-compatible) provides two methods to trigger RDB snapshot backups.

• Automatic backup: The system creates backups based on your configured automatic backup policy. By default, backups are created once per day.

  To ensure data security, automatic backup sets cannot be deleted or have their expiration time changed. The system deletes them automatically after they expire.

• Manual backup: You can manually trigger a backup at any time, with a limit of 30 backups per instance per day.

  For cloud-native instances, you can customize the expiration policy for each manual backup, delete manual backup sets, and change their expiration times.

When a cloud-native instance is deleted (either because it expires or is manually released), the status of all its backup sets changes to Not expired. You can then restore or delete them as needed. However, when a classic instance is deleted, its backup sets are also deleted.

Limitations

• If a backup is already in progress, you cannot start a new one. Wait for the current backup to complete before trying again.

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

Procedure

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. In the navigation pane on the left, click Backup and Recovery.

3. Perform one of the following procedures:

   Modify automatic backup policy

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

   2. In the dialog box that appears, configure the backup cycle and backup time window.

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

      • Backup Cycle: Select one or more days of the week for backups. By default, backups are created once per day.

      • Backup Time: Select a time window in hours. We recommend scheduling backups during off-peak hours.

        Note

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

   3. Click OK.

   Create manual backup

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

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

      Custom expiration policies for manual backups are supported only on cloud-native instances, not on classic instances. The available options are:

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

      • Independent: Set a specific retention period for this backup, from 3 to 730 days.

      • Not expired: The backup never expires and is retained indefinitely until manually deleted. For example, you can create a manual backup every Monday or at the beginning of each month and set it to Not expired for long-term data retention.

      Note

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

      • You can extend the expiration time of a manual backup.

FAQ

Related APIs

References

• To restore data, see Restore data from a backup set.

• To download a backup file to your computer, see Download a backup set.