Modifying the Backup Policy Bound to Vault
Function
This API is used to modify the backup policy associated with the vault.
Calling Method
For details, see Calling APIs.
URI
PUT /v5/{project_id}/backup/policy
Parameter |
Mandatory |
Type |
Description |
---|---|---|---|
project_id |
Yes |
String |
User project ID Minimum: 1 Maximum: 256 |
Parameter |
Mandatory |
Type |
Description |
---|---|---|---|
enterprise_project_id |
No |
String |
Enterprise project ID. To query all enterprise projects, set this parameter to all_granted_eps. Default: 0 Minimum: 1 Maximum: 256 |
Request Parameters
Parameter |
Mandatory |
Type |
Description |
---|---|---|---|
x-auth-token |
Yes |
String |
User token. It can be obtained by calling the IAM API used to obtain a user token. The value of X-Subject-Token in the response header is a token. Minimum: 1 Maximum: 32768 |
region |
Yes |
String |
region id Minimum: 0 Maximum: 128 |
Parameter |
Mandatory |
Type |
Description |
---|---|---|---|
enabled |
No |
Boolean |
Whether the policy is enabled. The default value is true. |
policy_id |
Yes |
String |
Policy ID Minimum: 1 Maximum: 256 |
operation_definition |
No |
Scheduling parameter. |
|
trigger |
No |
BackupTriggerRequestInfo object |
Time scheduling rule for the policy |
Parameter |
Mandatory |
Type |
Description |
---|---|---|---|
day_backups |
No |
Integer |
Maximum number of retained daily backups. The latest backup of each day is saved in the long term. This parameter is not affected by the maximum number of retained backup. The value ranges from 0 to 100. If this parameter is specified, timezone must be configured. Minimum value: 0. Maximum value: 100 Minimum: 0 Maximum: 100 |
max_backups |
No |
Integer |
Maximum number of automated backups that can be retained for an object. The value can be -1 or ranges from 0 to 99999. If the value is set to -1, the backups will not be cleared even though the configured retained backup quantity limit is exceeded. If this parameter and retention_duration_days are left blank at the same time, the backups will be retained permanently. Minimum value: 1. Maximum value: 99999. Default value: -1 Minimum: -1 Maximum: 99999 |
month_backups |
No |
Integer |
Maximum number of retained monthly backups. The latest backup of each month is saved in the long term. This parameter is not affected by the maximum number of retained backup. The value ranges from 0 to 100. If this parameter is specified, timezone must be configured. Minimum value: 0. Maximum value: 100 Minimum: 0 Maximum: 100 |
retention_duration_days |
No |
Integer |
Duration of retaining a backup, in days. The maximum value is 99999. If the value is set to -1, backups will not be cleared even though the configured retention duration is exceeded. If this parameter and max_backups are left blank at the same time, the backups will be retained permanently. Minimum value: 1. Maximum value: 99999. Default value: -1 Minimum: -1 Maximum: 99999 |
timezone |
No |
String |
Time zone where the user is located, for example, UTC+08:00. Set this parameter only after you have configured any of the parameters day_backups, week_backups, month_backups, and year_backups. Minimum: 0 Maximum: 256 |
week_backups |
No |
Integer |
Maximum number of retained weekly backups. The latest backup of each week is saved in the long term. This parameter can be effective together with the maximum number of retained backups specified by max_backups. The value ranges from 0 to 100. If this parameter is specified, timezone must be configured. Minimum: 0 Maximum: 100 |
year_backups |
No |
Integer |
Maximum number of retained yearly backups. The latest backup of each year is saved in the long term. This parameter can be effective together with the maximum number of retained backups specified by max_backups. The value ranges from 0 to 100. If this parameter is specified, timezone must be configured. Minimum value: 0. Maximum value: 100 Minimum: 0 Maximum: 100 |
Parameter |
Mandatory |
Type |
Description |
---|---|---|---|
properties |
Yes |
Time rule for the policy execution. |
Parameter |
Mandatory |
Type |
Description |
---|---|---|---|
pattern |
Yes |
Array of strings |
Scheduling rule A maximum of 24 rules can be configured. The scheduling rule complies with iCalendar RFC 2445, but it supports only parameters FREQ, BYDAY, BYHOUR, BYMINUTE, and INTERVAL. FREQ can be set only to WEEKLY or DAILY. BYDAY can be set to MO, TU, WE, TH, FR, SA, or SU (seven days of a week). BYHOUR ranges from 0 to 23 hours. BYMINUTE ranges from 0 minutes to 59 minutes. The scheduling interval must not be less than 1 hour. A maximum of 24 time points are allowed in a day. For example, if the scheduling time is 14:00 from Monday to Sunday, set the scheduling rule as follows: FREQ=WEEKLY;BYDAY=MO,TU,WE,TH,FR,SA,SU;BYHOUR=14;BYMINUTE=00. To start scheduling at 14:00 every day, the rule is as follows: FREQ=DAILY;INTERVAL=1;BYHOUR=14;BYMINUTE=00'. Minimum: 1 Maximum: 256 Array Length: 0 - 24 |
Response Parameters
Status code: 200
Parameter |
Type |
Description |
---|---|---|
error_code |
Integer |
Error code. If the operation is successful, 0 is returned. Minimum: 0 Maximum: 100 |
error_description |
String |
Error description. If the operation is successful, success is returned. Minimum: 1 Maximum: 256 |
Example Requests
Modify the backup policy. The target backup policy ID is af4d08ad-2b60-4916-a5cf-8d6a23956dda.
PUT https://{endpoint}/v5/{project_id}/backup/policy { "enabled" : true, "policy_id" : "af4d08ad-2b60-4916-a5cf-8d6a23956dda", "operation_definition" : { "day_backups" : 0, "max_backups" : -1, "month_backups" : 0, "retention_duration_days" : 5, "timezone" : "UTC+08:00", "week_backups" : 0, "year_backups" : 0 }, "trigger" : { "properties" : { "pattern" : [ "FREQ=DAILY;INTERVAL=2;BYHOUR=14;BYMINUTE=00" ] } } }
Example Responses
Status code: 200
Modify a backup policy.
{ "error_code" : 0, "error_description" : "success" }
Status Codes
Status Code |
Description |
---|---|
200 |
Modify a backup policy. |
Error Codes
See Error Codes.
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.