Creating a Microservice Backup Policy

Function

This API is used to create a microservice backup policy.

Authorization Information

Each account has all of the permissions required to call all APIs, but IAM users must have the required permissions specifically assigned.

If you are using role/policy-based authorization, see the required permissions in Permissions and Supported Actions.
If you are using identity policy-based authorization, the permission listed below is required.
Action
Access Level
Resource Type (*: required)
Condition Key
Alias
Dependency
cse:engine:create
write
-
g:ResourceTag/<tag-key>
g:EnterpriseProjectId
g:TagKeys
-
-

Action	Access Level	Resource Type (*: required)	Condition Key	Alias	Dependency
cse:engine:create	write	-	g:ResourceTag/<tag-key> g:EnterpriseProjectId g:TagKeys	-	-

URI

POST /cseengine/v1/engines/{engineId}/backup-strategies

**Table 1** Path parameter
Parameter	Mandatory	Type	Description
engine_id	Yes	String	Microservice engine ID.

Request

**Table 2** Request header parameters
Parameter	Mandatory	Type	Description
X-Auth-Token	Yes	String	User token.
X-Enterprise-Project-ID	No	String	If this parameter is not set, the default enterprise project is default and the ID is 0. Default Value: 0
Content-Type	Yes	String	Set it to application/json;charset=UTF-8.
Accept	Yes	String	Set it to application/json.

**Table 3** Request body parameters
Parameter	Mandatory	Type	Description
schedule	Yes	String	Scheduling cron expression for describing the backup time.
reserve	No	int	Backup file retention days.
maxFiles	No	int	Maximum number of files.

Response

Status code: 200

**Table 4** Response body parameters
Parameter	Type	Description
id	String	Backup policy ID.
engineId	String	Engine ID.
schedule	String	Scheduling cron expression for describing the backup time.
reserve	String	Backup file retention days.
maxFiles	int	Maximum number of files.
createAt	long	Creation timestamp.
nextAt	long	Next backup timestamp.

Status code: 400

**Table 5** Response body parameters
Parameter	Type	Description
error_code	String	Error code.
error_msg	String	Error message.
detail	String	Location details.

Status code: 500

**Table 6** Response body parameters
Parameter	Type	Description
error_code	String	Error code.
error_msg	String	Error message.
detail	String	Location details.

Example Request

POST https://{endpoint}/cseengine/v1/engines/{engineId}/backup-strategies

{
  "schedule" : "string",
  "reserve" : "10",
  "maxFiles": "10"
}

Example Response

Status code: 200

success

{
  "id": "string",
  "engineId": "string",
  "schedule": "string",
  "reserve": "10",
  "maxFiles": "10",
  "createAt": "10000",
  "nextAt": "100000"
}

Status Codes

Status Code	Description
200	success
400	Bad Request
500	Internal Server Error

Error Code

See Error Codes.

Parent topic:Engine Management

Previous topic: Backing Up and Restoring a Microservice Engine

Next topic: Creating a Microservice Engine Tag

Feedback

Was this page helpful?

Helpful Not helpful

Provide feedback

Thank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.

The system is busy. Please try again later.

For any further questions, feel free to contact us through the chatbot.

Chatbot