- Service Overview
- Getting Started
- User Guide
-
API Reference
- Before You Start
- API Overview
- Calling APIs
- Getting Started
-
API Description
-
VBS Backups
- Creating a VBS Backup
- Deleting a VBS Backup (Deprecated)
- Restoring a Disk Using a VBS Backup
- Creating a VBS Backup (Native OpenStack API) (Deprecated)
- Querying Summary Information About VBS Backups (Native OpenStack API) (Deprecated)
- Querying Details About VBS Backups (Native OpenStack API) (Deprecated)
- Querying Details About a VBS Backup (Native OpenStack API) (Deprecated)
- Querying the Job Status
- Deleting a VBS Backup (Native OpenStack API) (Deprecated)
- Restoring a Disk Using a VBS Backup (Native OpenStack API) (Deprecated)
- Sharing a Backup
- Canceling Sharing of a Backup
- Querying Backup Sharings
- Counting Backup Sharings
- Querying Details About a Backup Sharing
-
Backup Policies
- Creating a Backup Policy
- Querying Backup Policies
- Modifying a Backup Policy
- Deleting a Backup Policy
- Associating Resources with a Backup Policy
- Disassociating Resources from a Backup Policy
- Executing a Backup Policy At Once
- Enabling or Disabling a Backup Policy
- Querying Backup Jobs Triggered by a Backup Policy
- Adding a Tag to a Backup Policy
- Removing a Tag from a Backup Policy
- Querying All Backup Policy Tags
- Querying Tags of a Backup Policy
- Batch Updating or Removing Tags of a Backup Policy
- Querying Backup Policies by Tag
-
VBS Backups
- Permissions Policies and Supported Actions
- Appendix
-
FAQs
- What Is Volume Backup Service?
- What Is a Backup Policy?
- What Are the Differences Between Backup and Disaster Recovery?
- How Do I Purchase and Renew VBS?
- What Are the Differences Between CSBS and VBS?
- Does VBS Support Simultaneous Backup of All EVS Disks on a Server?
- Do I Need to Stop the Server Before Backing Up EVS Disks on a Server Using VBS?
- How Long Does VBS Take to Back Up an EVS Disk?
- Does VBS Support Cross-Region Backup and Restoration?
- Do I Need to Stop the Server Before Restoring EVS Disk Data with a VBS Backup?
- What Is the Charging Mode of EVS Disks Created with a VBS Backup?
- Why Are CSBS Backups Displayed on the VBS Backup Page?
- Can a VBS Backup of a System Disk Be Used to Restore the System Disk of an ECS?
- Can I Use a VBS Backup to Restore an EVS Disk Whose Capacity Has Been Expanded?
- Is There a Quota Limit on the Number of Backups?
- What Can I Do In Case of Exceptions in VBS?
- Why Add Tags to a VBS Backup or Backup Policy?
- Does Backup Can Be Performed Several Times a Day?
- Can a Disk Only Be Associated With One Policy?
- What Are Full Backup and Incremental Backup?
- What Are the Differences Between Backups and Snapshots?
- Why Is the Remaining Space Not Changed After a Backup Is Deleted?
- Why Is the Disk Space Usage Displayed in the File System Different from the Backup Size?
- Why Does the Retention Rule Not Take Effect After Being Modified?
- How Do I Disable Automatic Backup?
- Videos
- Glossary
-
More Documents
-
User Guide (Paris)
- Service Overview
- Getting Started
- Operation Guide
-
FAQs
- Does VBS Support Simultaneous Backup of All EVS Disks on a Server?
- Do I Need to Stop the Server Before Backing Up EVS Disks on a Server Using VBS?
- Does VBS Support Cross-Region Backup and Restoration?
- Do I Need to Stop the Server Before Restoring EVS Disk Data with a VBS Backup?
- What Is the Charging Mode of EVS Disks Created with a VBS Backup?
- Why Are CSBS Backups Displayed on the VBS Backup Page?
- Can a VBS Backup of a System Disk Be Used to Restore the System Disk of an ECS?
- Can I Use a VBS Backup to Restore an EVS Disk Whose Capacity Has Been Expanded?
- Is There a Quota Limit on the Number of Backups?
- What Can I Do In Case of Exceptions in VBS?
- Can a Disk Only Be Associated With One Policy?
- What Are Full Backup and Incremental Backup?
- What Are the Differences Between Backups and Snapshots?
- Why Is the Remaining Space Not Changed After a Backup Is Deleted?
- Troubleshooting Cases
- Change History
-
API Reference (Paris)
- Before You Start
- API Overview
- Calling APIs
- Getting Started
-
API Description
-
VBS Backups
- Creating a VBS Backup
- Deleting a VBS Backup (Deprecated)
- Restoring a Disk Using a VBS Backup
- Creating a VBS Backup (Native OpenStack API)
- Querying Summary Information About VBS Backups (Native OpenStack API)
- Querying Details About VBS Backups (Native OpenStack API)
- Querying Details About a VBS Backup (Native OpenStack API)
- Querying the Job Status
- Deleting a VBS Backup (Native OpenStack API)
- Restoring a Disk Using a VBS Backup (Native OpenStack API)
-
Backup Policies
- Creating a Backup Policy
- Querying Backup Policies
- Modifying a Backup Policy
- Deleting a Backup Policy
- Associating Resources with a Backup Policy
- Disassociating Resources from a Backup Policy
- Executing a Backup Policy At Once
- Enabling or Disabling a Backup Policy
- Querying Backup Jobs Triggered by a Backup Policy
-
VBS Backups
- Appendix
- Change History
-
User Guide (Paris)
- General Reference
Copied.
Response
Status Code
After sending a request, you will receive a response, including a status code, response header, and response body.
A status code is a group of digits, ranging from 1xx to 5xx. It indicates the status of a request. For more information, see Status Codes.
For example, if status code 201 is returned for calling the API used to create an IAM user, the request is successful.
Response Header
Similar to a request, a response also has a header, for example, Content-Type.
Figure 1 shows the response header fields for the API used to create an IAM user. The X-Subject-Token header field is the desired user token. This token can then be used to authenticate the calling of other APIs.
For security purposes, you are advised to set the token in ciphertext in configuration files or environment variables and decrypt it when using it.
(Optional) Response Body
The body of a response is often returned in a structured format (for example, JSON or XML) as specified in the Content-Type header field. The response body transfers content except the response header.
The following is part of the response body for the API used to create an IAM user.
{ "user": { "id": "c131886aec...", "name": "IAMUser", "description": "IAM User Description", "areacode": "", "phone": "", "email": "***@***.com", "status": null, "enabled": true, "pwd_status": false, "access_mode": "default", "is_domain_owner": false, "xuser_id": "", "xuser_type": "", "password_expires_at": null, "create_time": "2024-05-21T09:03:41.000000", "domain_id": "d78cbac1..........", "xdomain_id": "30086000........", "xdomain_type": "", "default_project_id": null } }
If an error occurs during API calling, an error code and a message will be displayed. The following shows an error response body.
1 2 3 4 |
{ "error_msg": "The request message format is invalid.", "error_code": "IMG.0001" } |
In the response body, error_code is an error code, and error_msg provides information about the error.
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.
For any further questions, feel free to contact us through the chatbot.
Chatbot