Updated on 2023-06-02 GMT+08:00

Creating a Backup Policy

A backup policy allows CBR to automatically back up vaults at specified times or intervals. Periodic backups can be used to restore data quickly against data corruption or loss.

To implement periodic backups, you need a backup policy first. You can use the default backup policy or create one as needed.

You can apply backup policies to server backup vaults, SFS Turbo backup vaults, and disk backup vaults. CBR will then periodically perform backup at the time given in the backup policy and delete expired backups.


  • A backup policy must be enabled before it can be used for periodic backups.
  • A maximum of 32 backup policies can be created in each account.
  • When a backup time and a replication time are both configured, ensure that replication starts after backup is complete. Or, replication may fail.
  • When expired backups are deleted, automatic backups will be deleted, but manual backups will not.
  • Only servers in the Running or Stopped state and disks in the Available or In-use state can be backed up.


  1. Log in to CBR Console.

    1. Log in to the management console.
    2. Click in the upper left corner and select your region and project.
    3. Click and choose Storage > Cloud Backup and Recovery. Select a backup type from the left navigation pane.

  2. Choose Policies and click the Backup Policies tab. In the upper right corner, click Create Policy. See Figure 1.

    Figure 1 Creating a backup policy

  3. Set the backup policy parameters. Table 1 describes the parameters.

    Table 1 Backup policy parameters



    Example Value


    Select a policy type. In this section, we select the backup policy.

    Backup policy


    Backup policy name

    A name must contain 1 to 64 characters including digits, letters, underscores (_), or hyphens (-).



    Whether to enable the backup policy.

    Only after a backup policy is enabled and applied will CBR automatically backs up the vault resources and deletes expired backups.

    Backup Frequency

    Select a backup frequency.

    • Weekly

      Specifies on which days of each week the backup task will be executed. You can select multiple days.

    • Day based

      Specifies the interval (every 1 to 30 days) for executing the backup task.

    Every day

    If you select day-based backup, the first backup is supposed to be executed on the day when the backup policy is created. If the execution time on the day you create the backup policy has passed, the first backup will be executed in the next backup cycle.

    It is recommended that backups be performed during off-peak hours or when no services are running.

    Execution Time

    Execution time

    Backups can be scheduled at the beginning of each hour, and you can select multiple hours.

    • There may be a time difference between the scheduled backup time and the actual backup time.
    • If a large amount of data needs to be backed up, you are advised to make backup less frequent to prevent the system from skipping any execution time.

      For example, a disk is scheduled to be backed up at 00:00, 01:00, and 02:00. A backup task starts at 00:00. Because a large amount of incremental data needs to be backed up or a heap of backup tasks are executed at the same time, this backup task takes 90 minutes and completes at 01:30. The system performs the next backup at 02:00. In this case, only two backups are generated in total, one at 00:00, and the other at 02:00.

    00:00, 02:00

    It is recommended that backups be performed during off-peak hours or when no services are running.

    Full Backup

    Whether to perform periodic full backups.

    • Enable

      Enabling full backup improves your data reliability, but full backups will use more storage space.

      Configure a full backup frequency. The value ranges from 0 to 100. Value 0 indicates that a full backup will be performed in every backup task.

    • Do not enable

      Periodic full backup will not be performed. Instead, the system will always perform incremental backups after the first backup.

      • A full backup usually takes a long period of time. If a full backup of a resource is in progress, other backups of this resource will not be performed. For example, any policy-based backups planned to be executed during a full backup will be skipped.
      • If you configure to retain backups by quantity, full backups will be performed only when the full backup frequency is less than the number of backups to be retained.


    Retention Rule

    Rule that specifies how backups will be retained

    • Time period

      You can choose to retain backups for one month, three months, six months, one year, or for any desired number (2 to 99999) of days.

    • Backup quantity

      You can set the maximum number of backups to retain for each resource. The value ranges from 2 to 99999.

    • Advanced Options

      You can also set long-term retention rules with advanced options. Long-term retention rules and quantity-based retention rules will be both applied.

      • Day-based: 0–100
      • Weekly: 0–100
      • Monthly: 0–100
      • Yearly: 0–100

      A resource may be backed up multiple times in a day. If day-based backup is configured, only the most recent backup of that day is retained. If you set Day-based to 5, the most recent backup of each of the last five days that have backups generated will be retained and the earliest backups will be deleted automatically. If day-based, weekly, monthly, and yearly retention rules are all configured, all the rules will apply and the union set of backups will be retained. For example, if Day-based is set to 5 and Weekly to 1, five backups will be retained. The long-term retention rule and the quantity-based retention rule both apply.

    • Permanent
      • The system automatically deletes the earliest and expired backups every other day to avoid exceeding the maximum number of backups to retain or retaining any backup longer than the maximum retention period.
      • Expired backups are not deleted right after they are expired. They will be deleted from 12:00 to 00:00 in batches.
      • The retention rules apply only to auto-generated backups, but not manual backups. Manual backups need to be deleted manually.
      • After a backup is used to create an image, the backup will not be deleted by the retention rule.
      • A maximum of 10 backups are retained for failed periodic backup tasks. They are retained for one month and can be deleted manually.

    6 months

    More frequent backups create more backups or retain backups for a longer time, protecting data to a greater extent but occupying more storage space. Set an appropriate backup frequency as needed.

  4. Click OK.
  5. Locate the desired vault and choose More > Apply Backup Policy to apply the policy to the vault. You can view the applied policy on the vault details page.

    After the policy is applied, data will be periodically backed up to the vault based on the policy.


At 10:00 a.m. on Monday, a user sets a backup policy for their vault to instruct CBR to execute a backup task at 02:00 a.m. every day and retain a maximum of three backups. As of 11:00 a.m. on Saturday, three backups will be retained, which are generated on Wednesday, Thursday, and Friday. The backup generated at 02:00 a.m. on Tuesday has been automatically deleted.