Organizational Policy Name |
Organizational policy name
A name must contain 1 to 64 characters including digits, letters, underscores (_), or hyphens (-). |
org_policy |
Organizational Policy Description |
Description that can help the organization members to understand the usage of the policy. |
/ |
Organizational Policy Type |
Select a policy type. In this section, we select the backup policy. |
Backup policy |
Policy Name |
Backup policy name
A name must contain 1 to 64 characters including digits, letters, underscores (_), or hyphens (-). |
backup_policy |
Status |
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.
|
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 service off-peak hours or when no services are running. |
Execution Time |
Execution times of the backup policy in a day
Backups can be scheduled at the beginning of each hour, and you can select multiple hours.
NOTICE:
- 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. CBR 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.
- The execution times refer to the local times of clients, not the time zone and times of the region.
|
00:00, 02:00
- It is recommended that backups be performed during service off-peak hours or when no services are running.
- Peak hours of the backup service are from 00:00 to 06:00, during which there may be scheduling delays. So you are advised to evaluate your service types and schedule backups outside of the backup peak hours.
|
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 means that a full backup will be performed in every backup task.
- Do not enable
Periodic full backup will not be performed. Instead, CBR will always perform incremental backups after the first backup.
NOTICE:
- 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.
- When backups are kept by quantity, full backups can be performed only when the full backup frequency configured is less than the number of retained backups.
|
7 |
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
NOTE:
- 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.
- If 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 |