Immutable backup

Updated at:

Immutable backup is intended for scenarios such as insurance and financial services where critical business data must be protected. After immutable backup is enabled, backup data is locked in a read-only state within the configured retention period. The backup data cannot be modified or deleted by any means, including the console and API operations. When a cluster is released, at least one immutable backup set is retained permanently.

Note

Immutable backup is currently in a grayscale rollout. If you want to try it, submit a ticket and we will assist you.

Overview

Immutable backup is enabled at the cluster level. After it is enabled, all backup sets that are automatically generated for the cluster, including data backups and log backups, become immutable backup sets and expire when the configured retention period ends. Within the retention period, the backup data cannot be modified or deleted through the console or by calling API operations. Immutable backup cannot be disabled after it is enabled.

Limits

  • The backup cycle must include at least 2 days per week.

  • After immutable backup is enabled:

    • The retention period of level-1 backups must be at least 7 days. If the original retention period is shorter than 7 days, the system automatically adjusts it to 7 days when immutable backup is enabled.

    • When you adjust the backup policy, you can only increase the backup frequency or extend the backup retention period. You cannot decrease the frequency or shorten the retention period.

    • If level-2 backup is enabled, you cannot disable level-2 backup or cancel the same-region or cross-region level-2 backup retention that is already enabled.

    • When the cluster is released, at least one backup set is retained permanently. After the cluster is released, the backup policy cannot be modified.

Enable immutable backup

Warning

This operation is irreversible. Immutable backup cannot be disabled after it is enabled. Before you proceed, verify the backup frequency, retention period, and level-2 backup settings.

  1. Log on to the PolarDB console and go to the details page of the target cluster.

  2. In the left-side navigation pane, choose Backup and Restoration.

  3. In the Backup Policy Settings section, make sure that backups are scheduled on at least 2 days per week and that the level-1 backup retention period is at least 7 days.

  4. In the Immutable Backup section, turn on the switch.

  5. In the confirmation dialog box that appears, read the message carefully and click OK.

After immutable backup is enabled, the status of Immutable Backup changes to Enabled, and the switch is dimmed and cannot be turned off.

Backup handling after cluster release

After immutable backup is enabled, the backup retention policy that is applied when the cluster is released is locked and cannot be changed. By default, the last backup set is retained permanently. You can also change the setting to permanently retain all backup sets. You are not allowed to delete all backup sets when you release the cluster.

Immutable backup sets are not deleted when the cluster is released. They are retained until their retention periods end.