To implement periodic automatic backup on EVS disks, you need to create a backup policy first. Then the system will periodically perform backups according to the execution time specified in the backup policy. You can choose to use the default backup policy provided by the system or create one as needed.
The system automatically creates EVS disk data backups and deletes expired data backups only when a backup policy is created and enabled.
You can create a backup policy to associate all those EVS disks whose data needs to be periodically backed up.
The Policies tab page displays existing backup policies. Expand the desired backup policy to view EVS disks associated with it.
Parameter |
Description |
Remarks |
---|---|---|
Name |
The name is a string of 1 to 64 characters consisting of letters, digits, underscores (_), and hyphens (-), and cannot start with default. |
Example value: autobk_78ba |
Execution Time |
Detailed time for backing up data of the EVS disks associated with the backup policy. Backup can be scheduled on integral hours and multiple selections are supported. |
Example value: 02:00 |
Backup Period |
Weekly: specifies on which days of each week the backup job will be executed. You can select all. Daily: specifies the interval (every 1 to 14 days) for executing the backup job (on the hour). |
Example value: Every 3 days If you select Daily, the first backup time is irrelevant to the time when the backup policy is created. A backup policy takes effect from the month when it is created. Policies with the same Backup Period execute backup jobs at the same times. For example, if a backup policy with "Every 3 days" is created on the second date of a month, the first backup will be created on the fourth date of the month. "Every 3 days" indicates that backups will be created on the first date, fourth date, seventh date, and so on. To ensure stable service running, back up EVS disks during off-peak hours. |
Retention Rule |
Time Period: You can choose to retain backups for one month, three months, six months, or one year, or for any desired number (2 to 99999) of days. Backup Quantity: specifies the maximum allowed number of backups for a single EVS disk. NOTE:
Set this parameter based on the applied quota. For example, if 10 EVS disks are associated with the backup policy and this parameter is set to 10, then at least a quota of 100 backups is required. If the applied quota is smaller than 100, the backup job will fail due to the insufficient quota. To view the quota, read the related tip above the VBS backup list. |
Example value: 6 A more frequent backup of EVS disks creates more backups and delivers a higher level of data protection but occupies more storage space. Determine the backup frequency based on the data importance and service volume. Perform relatively frequent backup operations for important data. When the number of backups to be retained has exceeded the value of Backup Quantity, the system automatically deletes the earliest backups. After a backup is deleted, the other backups can still be used for restoration. |
Retain the first backup in this month |
If you select this option, the initial data backup in the current month will be retained. |
The first backup in the current month will not be deleted. For example, if the current month is February, the first backup generated in February will not be deleted during February. The first backup generated in January, together with other backups generated in January, will be deleted in sequence. |
Enable |
You can turn on the switch ( |
If you have disabled the backup policy or have turned off the switch ( |
A tag is represented in the form of a key-value pair. Tags are used to identify, classify, and search for cloud resources.
Tags added in a backup policy apply to all backups generated using the backup policy. Tags are used to filter and manage backup resources only. A backup policy can have a maximum of 10 tags.
Parameter |
Description |
Example Value |
---|---|---|
Key |
Each tag of a backup has a unique key. The key of a tag is user-definable or is selected from those of existing tags in TMS. The naming rules for a tag key are as follows:
|
Key_0001 |
Value |
The values of tags can be repetitive and can be blank. The naming rules for a tag value are as follows:
|
Value_0001 |