Roll back disk data
Updated at：2025-10-20
This API facilitates rolling back disk data from a specified disk snapshot.
- The disk must be in an Available state to proceed with this operation.
- The provided snapshot ID (snapshotId) must correspond to a snapshot created from the specified disk ID (volumeId).
- When rolling back a system disk, ensure the instance status is either Running or Stopped before initiating this operation.
Note:
When rolling back a system disk snapshot, all data generated on the system disk after the snapshot was created will be completely lost and cannot be recovered.
Request structure
Plain Text
1PUT /v2/volume/{volumeId}?{action} HTTP/1.1
2Host: bcc.bj.baidubce.com
3Authorization: authorization string
4
5{
6 "snapshotId": snapshotId
7} Request headers
There are no special headers required beyond the common headers.
Request parameters
| Parameter name | Types | Whether required | Parameter location | Description |
|---|---|---|---|---|
| version | String | Yes | URL parameter | API version number |
| volumeId | String | Yes | URL parameter | ID of the disk to be rolled back |
| action | String | Yes | Query | Action performed on the disk, current value: rollback |
| snapshotId | String | Yes | Request Body parameters | Snapshot ID used to roll back the specified disk, which must be a snapshot created by the volumeId |
Response headers
No special headers are required beyond the standard ones.
Response parameters
There are no special response parameters
Error codes
| Error code | Error description | HTTP status code | Chinese explanation |
|---|---|---|---|
| BadRequest | Bad request parameters or illegal request. | 400 | Invalid request parameters |
| SnapshotOperationForbidden | snapshot operation forbidden. | 403 | Snapshot operation: deny |
| NoSuchObject | The specified object is not found or resource do not exist. | 404 | Resource does not exist |
| OperationDenied | Operation not available. | 409 | Operation not allowed |
Request example
Plain Text
1PUT /v2/volume/v-3zmCcxbR?rollback HTTP/1.1
2Host: bcc.bj.baidubce.com
3Authorization: bce-auth-v1/f81d3b34e48048fbb2634dc7882d7e21/2015-08-11T04:17:29Z/3600/host/74c506f68c65e26c633bfa104c863fffac5190fdec1ec24b7c03eb5d67d2e1de
4
5{
6 "snapshotId": "s-8CM91d5U"
7}Response example
Plain Text
1HTTP/1.1 200 OK
2x-bce-request-id: 1214cca7-4ad5-451d-9215-71cb844c0a50
3Date: Wed, 03 Dec 2014 06:42:19 GMT
4Content-Type: application/json;charset=UTF-8
5Server: BWS