Error Codes
Status Code |
Error Code |
Error Message |
Description |
Solution |
---|---|---|---|---|
404 |
common.0011 |
query job fail |
Failed to query the task. |
Check whether the parameters are correct. |
400 |
VolumeBackup.0014 |
submit job exception |
Failed to submit the task. |
Try again. If the fault persists, contact the technical support. |
401 |
VolumeBackup.0041 |
api roles is null or empty |
Failed to check user rights. |
Add the required permissions for the user. |
403 |
VolumeBackup.0042 |
user role is not allowed for this action |
The user does not have the rights to perform operations. |
Add the required permissions for the user. |
401 |
VolumeBackup.0044 |
invalid token roles |
User rights are invalid. |
Obtain a valid token. |
400 |
VolumeBackup.0002 |
api request parameter instance null |
The request format is incorrect. |
Use a valid format. |
400 |
VolumeBackup.0003 |
api request parameter name over length |
Parameter name in the request is too long. |
Use a valid name. |
400 |
VolumeBackup.0004 |
api request parameter name invalid character |
Parameter name in the request contains invalid characters. |
Use a valid name. |
400 |
VolumeBackup.0005 |
api request parameter name invalid prefix |
Parameter name in the request starts with auto. |
Use a valid name. |
400 |
VolumeBackup.0006 |
api request parameter description is invalid |
Parameter description in the request is too long or contains invalid characters. |
Use valid parameter description. |
400 |
VolumeBackup.0007 |
api request parameter name is null |
Parameter name in the request is empty. |
Use a valid name. |
400 |
VolumeBackup.0008 |
get assume role token fail |
Failed to obtain the permission. |
Use a valid token. |
400 |
VolumeBackup.0009 |
call IAM api to get shadow domain ak and sk fail. |
Failed to obtain the key. |
For details, contact the technical support. |
400 |
VolumeBackup.0010 |
api request parameter volume_id null |
Parameter volume_id in the request is empty. |
Use a valid disk ID. |
400 |
VolumeBackup.0011 |
api request parameter volume_id invalid UUID pattern |
The format of parameter volume_id in the request is incorrect. |
Use a valid disk ID. |
400 |
VolumeBackup.0012 |
volume status is not available or in-use |
The disk status is not available or in_use. |
Try again in an allowed state of disk. |
400 |
VolumeBackup.0013 |
volume's last backup progress is not finished |
The previous backup creation task is not complete. |
Back up data again after the previous backup task is complete. |
400 |
VolumeBackup.0017 |
fsp cinder create snapshot exception |
Failed to create the snapshot. |
Try again. If the fault persists, contact the technical support. |
400 |
VolumeBackup.0018 |
fsp cinder return null snapshot |
The snapshot creation result is empty. |
Try again. If the fault persists, contact the technical support. |
400 |
VolumeBackup.0019 |
fsp cinder get snapshot detail exception |
Failed to query the snapshot during backup creation. |
Try again. If the fault persists, contact the technical support. |
400 |
VolumeBackup.0020 |
got snapshot detail is null |
The snapshot query result is empty. |
Try again. If the fault persists, contact the technical support. |
404 |
VolumeBackup.0021 |
volume not exists |
The EVS disk does not exist or has been deleted. |
Try again. If the fault persists, contact the technical support. |
400 |
VolumeBackup.0022 |
fsp cinder create volume exception |
Failed to create the temporary disk. |
Try again. If the fault persists, contact the technical support. |
400 |
VolumeBackup.0023 |
fsp cinder return null volume |
The result of creating the temporary disk is empty. |
Try again. If the fault persists, contact the technical support. |
400 |
VolumeBackup.0024 |
fsp cinder get volume detail exception |
Failed to query the temporary disk. |
Try again. If the fault persists, contact the technical support. |
400 |
VolumeBackup.0025 |
got volume detail is null |
The result of querying the temporary disk is empty. |
Try again. If the fault persists, contact the technical support. |
400 |
VolumeBackup.0026 |
api request parameter name length is too short |
Parameter name in the request is too short. |
Use a valid name. |
400 |
VolumeBackup.0027 |
fsp cinder or ebackup create backup exception |
Failed to create the backup. |
Try again. If the fault persists, contact the technical support. |
400 |
VolumeBackup.0028 |
fsp cinder or ebackup return null backup |
The backup creation result is empty. |
Try again. If the fault persists, contact the technical support. |
400 |
VolumeBackup.0029 |
fsp cinder get backup detail exception |
Failed to query the backup result. |
Try again. If the fault persists, contact the technical support. |
400 |
VolumeBackup.0030 |
got backup detail is null |
The backup query result is empty. |
Try again. If the fault persists, contact the technical support. |
400 |
VolumeBackup.0035 |
fsp cinder get volume details exception |
Failed to query all disks of a user. |
Try again. If the fault persists, contact the technical support. |
400 |
VolumeBackup.0036 |
fsp cinder get backup details exception |
Failed to query all backups of a user. |
Try again. If the fault persists, contact the technical support. |
400 |
VolumeBackup.0037 |
created snapshot status is not available or query snapshot exception |
Failed to query the snapshot status. |
Try again. If the fault persists, contact the technical support. |
400 |
VolumeBackup.0038 |
created volume status is not available or query volume exception |
Failed to query the status of a temporary disk. |
Try again. If the fault persists, contact the technical support. |
400 |
VolumeBackup.0039 |
created backup status is not available or query backup exception |
Failed to query the backup status. |
Try again. If the fault persists, contact the technical support. |
400 |
VolumeBackup.0040 |
volume's backup number is over limit |
The number of existing VBS backups has reached the upper limit. |
Contact the administrator to increase quota. |
400 |
VolumeBackup.0043 |
fsp cinder get volume or backup detail exception |
Failed to query the disk or backup. |
Use a correct disk or backup. |
400 |
VolumeBackup.0049 |
api request tag parameter is invalid |
The tag parameter is invalid. |
Use a valid tag parameter. |
400 |
VolumeBackup.0050 |
The number of tags exceeded |
The number of tags has reached the upper limit. |
Use the tag function as required. |
400 |
VolumeBackup.0051 |
volume of this pod does not support backup |
The disk does not support backup. |
Backup is not supported currently. Contact the technical support. |
400 |
VolumeBackup.0053 |
DESS volume type is not support backup |
DESS disks do not support backup. |
Backup is not supported currently. Contact the technical support. |
400 |
VolumeBackup.0062 |
fsp cinder return snapshot status is error |
The snapshot status is error. |
Try again in an allowed state of disk. |
400 |
VolumeBackup.0063 |
fsp cinder return temp volume status is error |
The status of the temporary disk is error. |
Try again in an allowed state of disk. |
400 |
VolumeBackup.0064 |
fsp cinder return backup status is error |
The backup status is error. |
Try again in an allowed state of disk. |
400 |
VolumeBackup.0070 |
query quota usage exception |
Failed to query the quota information. |
For details, contact the technical support. |
400 |
VolumeBackup.0071 |
no enough sas volume quota num |
The quota for the number of SAS disks has been used up. |
Contact the administrator to increase quota. |
400 |
VolumeBackup.0072 |
no enough sas volume quota bytes |
The quota for the capacity of SAS disks has been used up. |
Contact the administrator to increase quota. |
400 |
VolumeBackup.0073 |
no enough sata volume quota num |
The quota for the number of SATA disks has been used up. |
Contact the administrator to increase quota. |
400 |
VolumeBackup.0074 |
no enough sata volume quota bytes |
The quota for the capacity of SATA disks has been used up. |
Contact the administrator to increase quota. |
400 |
VolumeBackup.0075 |
no enough ssd volume quota num |
The quota for the number of SSD disks has been used up. |
Contact the administrator to increase quota. |
400 |
VolumeBackup.0076 |
no enough ssd volume quota bytes |
The quota for the capacity of SSD disks has been used up. |
Contact the administrator to increase quota. |
400 |
VolumeBackup.0077 |
no enough sas snapshot quota num |
The quota for the number of SAS disk snapshots has been used up. |
Contact the administrator to increase quota. |
400 |
VolumeBackup.0078 |
no enough sata snapshot quota num |
The quota for the number of SATA disk snapshots has been used up. |
Contact the administrator to increase quota. |
400 |
VolumeBackup.0079 |
no enough ssd snapshot quota num |
The quota for the number of SSD disk snapshots has been used up. |
Contact the administrator to increase quota. |
400 |
VolumeBackup.0080 |
no enough backup quota num |
The quota for the number of backups has been used up. |
Contact the administrator to increase quota. |
400 |
VolumeBackup.0081 |
no enough backup quota bytes |
The quota for the capacity of backups has been used up. |
Contact the administrator to increase quota. |
400 |
VolumeBackup.0082 |
no enough volume quota num |
The quota for the number of disks has been used up. |
Contact the administrator to increase quota. |
400 |
VolumeBackup.0083 |
no enough volume quota bytes |
The quota for the capacity of disks has been used up. |
Contact the administrator to increase quota. |
400 |
VolumeBackup.0084 |
no enough snapshot quota num |
The quota for the number of snapshots has been used up. |
Contact the administrator to increase quota. |
400 |
VolumeBackup.0100 |
submit subjod exception in delete backup status |
Failed to submit the subtask. |
Try again. If the fault persists, contact the technical support. |
400 |
VolumeBackup.0101 |
delete snapshot exception in delete backup status |
Failed to delete the snapshot. |
Try again. If the fault persists, contact the technical support. |
400 |
VolumeBackup.0102 |
delete backup exception when call openstack api |
Failed to delete the backup. |
Try again. If the fault persists, contact the technical support. |
400 |
VolumeBackup.0103 |
query backup detail exception in delete backup status |
Failed to query the backup details. |
Try again. If the fault persists, contact the technical support. |
400 |
VolumeBackup.0104 |
get glance msg from fsp failed. |
Failed to obtain the image information. |
Try again. If the fault persists, contact the technical support. |
400 |
VolumeBackup.0105 |
the url is invalid |
The format of the backup deletion request is incorrect. |
Use valid request parameters. |
400 |
VolumeBackup.0109 |
query snapshot from fsp failed |
Failed to query the snapshot during backup deletion. |
Try again. If the fault persists, contact the technical support. |
400 |
VolumeBackup.0110 |
the backup details msg is null |
Failed to query the backup. |
Try again. If the fault persists, contact the technical support. |
400 |
VolumeBackup.0113 |
The backup has been made as an image, cannot delete it |
The backup has already been used to create an image and cannot be deleted. |
Delete the created image first and then the backup. |
400 |
VolumeBackup.0123 |
query the backup details is null from FSP |
Failed to query all backups. |
Try again. If the fault persists, contact the technical support. |
400 |
VolumeBackup.0125 |
failed to delete the backup. |
Failed to perform the backup deletion operation. |
Try again. If the fault persists, contact the technical support. |
400 |
VolumeBackup.0129 |
Deleting this type of backups is not allowed |
Deleting this type of backups is not allowed. |
For details, contact the technical support. |
400 |
VolumeBackup.0900 |
error with ClientException |
The service is unavailable. |
For details, contact the technical support. |
404 |
VolumeBackup.0111 |
the volume info or backup detail is not exist |
The disk to be restored or the backup used to restore the disk does not exist. |
Use valid disk and backup. |
400 |
VolumeBackup.0200 |
restore backup exception |
Failed to restore data. |
For details, contact the technical support. |
400 |
VolumeBackup.0201 |
restore backup null response |
The data restoration result is empty. |
For details, contact the technical support. |
400 |
VolumeBackup.0202 |
restore backup volume error |
The disk status is error. |
For details, contact the technical support. |
400 |
VolumeBackup.0203 |
api request parameter backup_id null |
Parameter backup_id in the request is empty. |
Use a valid backup ID. |
400 |
VolumeBackup.0204 |
api request parameter backup_id invalid UUID pattern |
The format of parameter backup_id in the request is incorrect. |
Use a valid backup ID. |
400 |
VolumeBackup.0205 |
volume for restore state is not available |
The disk status is unavailable. |
Use a disk in a valid state. |
400 |
VolumeBackup.0206 |
volume for restore is creating backup |
A backup is being created for the disk. |
Wait until the backup is complete and try again. |
404 |
VolumeBackup.0207 |
query the volume backup details msg is null |
The disk does not exist. |
Use a valid disk. |
400 |
VolumeBackup.0208 |
volumeID in body is null or empty |
Parameter volume_id in the request is incorrect. |
Use a valid disk ID. |
400 |
VolumeBackup.0209 |
volume size is less than backup size |
The capacity of the disk must be greater than or equal to that of the backup. |
Expand the capacity of the disk. |
400 |
VolumeBackup.0210 |
body in request is empty |
The format of the disk restoration request is incorrect. |
Use valid restoration parameters. |
400 |
VolumeBackup.0211 |
Cloud disks at the disaster recovery site cannot be restored. |
Cloud disks at the disaster recovery site cannot be restored. |
Use valid restoration parameters. |
400 |
VolumeBackup.0089 |
backup status is not available |
The disk backup status is unavailable. |
Use a backup in an allowed state. |
400 |
AutoBackup.0000 |
request body is empty |
The request is empty. |
Use a valid request body. |
400 |
AutoBackup.0001 |
request body exist empty structure |
The object contained in the request is empty. |
Use a valid request body. |
401 |
AutoBackup.0002 |
request token is empty |
The token contained in the request header is empty. |
Use a valid token. |
401 |
AutoBackup.0003 |
request token is expired |
The token contained in the request header has expired. |
Use a valid token. |
401 |
AutoBackup.0005 |
request domain id is empty |
Failed to obtain the domain ID from the token contained in the request header. |
Use a valid token. |
400 |
AutoBackup.0006 |
request policy id is empty |
The policy ID contained in the request is empty. |
Use valid request parameters. |
400 |
AutoBackup.0008 |
convert request to JSON object failed |
Failed to convert the request into a JSON object. |
Use valid request parameters. |
500 |
AutoBackup.0009 |
internal error |
An exception occurred in internal system processing. |
Try again. If the fault persists, contact the technical support. |
400 |
AutoBackup.0100 |
normal tenant has no right to operator default policy |
The tenant cannot modify the default backup policy. |
For details, contact the technical support. |
400 |
AutoBackup.0101 |
backup policy name length is illegal |
The length of the backup policy name is invalid. |
Use a valid policy length. |
400 |
AutoBackup.0102 |
backup policy name is invalid |
The parameter of the backup policy name is invalid. |
Use a valid policy name. |
400 |
AutoBackup.0103 |
schedule policy start time format error |
The parameter of the backup job start time is invalid. |
Use a valid backup job start time. |
400 |
AutoBackup.0104 |
schedule policy status is illegal |
The parameter of the backup policy status is invalid. |
Use a valid policy state. |
400 |
AutoBackup.0105 |
schedule policy remain firstbackup of cur month is illegal |
The parameter of whether to retain the first backup in the current month is invalid. |
Use a valid parameter. |
400 |
AutoBackup.0106 |
schedule policy frequency is out of range |
The parameter of the backup job interval is invalid. |
Use a valid parameter. |
400 |
AutoBackup.0107 |
schedule policy rentention num is out of range |
The parameter of the number of retained backups is invalid. |
Use a valid parameter. |
400 |
AutoBackup.0108 |
schedule policy rentention day is out of range |
The parameter of the retention days is invalid. |
Use a valid parameter. |
400 |
AutoBackup.0109 |
schedule policy week frequency is illegal, must in (SUN, MON, TUE, WED, THU, FRI, SAT) |
The parameter of the backup job interval is invalid. |
Use a valid parameter. |
400 |
AutoBackup.0203 |
backup policy num over limit |
The number of existing backup policies has reached the upper limit. |
Use the policy function as required. |
400 |
AutoBackup.0204 |
number of volumes reaches limit |
The number of associated volumes has reached the upper limit. |
Associated the exceeded disk with a new policy. |
404 |
AutoBackup.0205 |
policyId is not exist |
The policy does not exist. |
Use a valid policy. |
400 |
AutoBackup.1100 |
query policy with null input or null tenantId |
The queried policy does not exist. |
Use a valid policy. |
400 |
AutoBackup.1300 |
delete policy: delete policy by policyId failed |
Failed to delete the policy. |
Try again. If the fault persists, contact the technical support. |
400 |
AutoBackup.1400 |
policy bind resources: resources illegal |
The resource to be associated is invalid. |
Use valid resource parameters. |
400 |
AutoBackup.1700 |
execute policy: input param invalid |
Failed to execute the backup policy. |
Try again. If the fault persists, contact the technical support. |
400 |
AutoBackup.0206 |
volume to bind is in bad status |
The status of the disk to be associated is invalid. |
Try again in an allowed state of disk. |
400 |
AutoBackup.0207 |
resource to bind is empty |
The resource to be associated is empty. |
Use valid association parameters. |
404 |
AutoBackup.0208 |
unable to get specified resource detail, may be incorrect resource id |
Operation failed because the disk you want to associate to or disassociate from a backup policy does not exist. |
Specify the operation restrictions. |
400 |
AutoBackup.0209 |
resource id or resource name is empty |
The resource ID or type is empty. |
Use valid resource parameters. |
400 |
AutoBackup.0210 |
HANA volume cannot bind to backup policy |
HANA disks cannot be associated with the backup policy. |
Backup is not supported currently. Contact the technical support. |
400 |
AutoBackup.0211 |
bad resource type |
The resource type is invalid. |
Use valid resource parameters. |
400 |
AutoBackup.0213 |
Unauthorized request |
The request is not authorized. |
Add the required permissions for the user. |
400 |
AutoBackup.0217 |
Snapshot quota is not enough |
The snapshot quota is insufficient. |
Contact the administrator to increase quota. |
400 |
AutoBackup.0218 |
Backup number quota is not enough |
The backup quota is insufficient. |
Contact the administrator to increase quota. |
400 |
AutoBackup.0220 |
DESS volume cannot bind to backup policy |
DESS disks cannot be associated with the backup policy. |
Backup is not supported currently. Contact the technical support. |
400 |
AutoBackup.0221 |
The request contains invalid parametersThe request contains invalid parameters |
The request cannot contain less-than signs (<) or greater-than signs (>). |
Use valid parameters. |
400 |
AutoBackup.0222 |
Only specified action is supported |
Only specified actions are supported. |
For details, contact the technical support. |
400 |
AutoBackup.0225 |
the backup policy is being executed, failed to execute the backup task |
Failed to perform the backup job because the backup policy is being executed. |
Perform the job after the backup is complete. |
401 |
AutoBackup.9002 |
authorization Filter fail |
An internal exception occurred in system authentication. |
Try again. If the fault persists, contact the technical support. |
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