We give an HTTP status code with every HTTP response we send for the Backup management APIs. These status codes are intended to comply with the IETF specification which mentions what the status code means and things like whether the clients can cache this result, or whether they should try the same request again. Here’s a non-exhaustive list of the frequently used status codes in our REST APIs and what we mean by them.

Status code	Status	Meaning
`200 OK`	Success	Everything was fine and worked.
`201 CREATED`	Success	Indicates that the request has succeeded and a new resource has been created as a result.
`202 ACCEPTED`	Success	Indicates that the request has been received but not completed yet. We have already added your request to our batch and will process it.
`400 BAD REQUEST`	Bad Request	The request does not have the required fields, or the fields the request has, are invalid in some way.
`401 UNAUTHORIZED`	Unauthorized	The current user is not authorized to execute this request. Please refer Authorization for more details.
`403 FORBIDDEN`	Forbidden	An action cannot be performed on the requested resource because the user does not have the access to that particular resource.
`404 NOT FOUND`	Not Found	The request has parameters that do not exist in the system. Please verify the data that you are sending in your request.
`409 CONFLICT`	Conflict	The request could not be completed due to a conflict with the current state of the resource. A similar request/resource already exists in the system, and hence this prevents the user to create duplicate requests.
`422 UNPROCESSABLE ENTITY`	Unprocessable Entity	The server understands the content type and syntax of the request entity, but still server is unable to process the request because of some invalid data passed in the request.
`429 TOO MANY REQUESTS`	Too Many Requests	There is a violation of the rate Limit Values that we have set for our APIs. To understand the Rate Limit values for different apis, please check Rate Limiting.
`500 INTERNAL SERVER ERRORT`	Internal Server Error	Something went wrong and we don't know what. If the issue persists kindly reach out to the support team with the relevant details.
`503 UNAVAILABLE`	Service Unavailable	Something is down that should be up. Our load balancers might return this if we're down. And we return it if something we're relying on to handle the request successfully isn't answering.
`504 GATEWAY TIMEOUT`	Gateway Timeout	We couldn't handle the GET request within our time limit. This might be due to some intermittent issue in the backend. Please reach out to the support if issue persists even after retries.

Error codes

Apart from the above Http Status codes, we also throw some custom error codes with messages which helps the customer to understand the exact issue in the request sent and hence the cause of failure too

Create backup policy

Http status code - 409 CONFLICT

1
2
"errorCode": "127",
"errorMessage": "Backup Policy already exists with orgId: {} cloudId: {} product: {PRODUCT}"

Http status code - 422 UNPROCESSABLE ENTITY

1
2
"errorCode": "103",
"errorMessage": "{PRODUCT} is not present in cloud site {}"

Create backup

Http status code - 404 NOT FOUND

1
2
"errorCode": "126",
"errorMessage": "Backup policy not found, orgId = {}, policyId = {}"

Http status code - 409 CONFLICT

1
2
"errorCode": "136",
"errorMessage": "A backup request for this product already exists"

Http status code - 422 UNPROCESSABLE ENTITY

1
2
"errorCode": "139",
"errorMessage": "The site is either not licensed or does not exist"

Get status of backup

Http status code - 400 BAD REQUEST

1
2
"errorCode": "108",
"errorMessage": "The backupId : {} is invalid or does not belong to operation Backup"

Create restore

Http status code - 409 CONFLICT

1
2
"errorCode": "137",
"errorMessage": "A restore request for this product already exists"

Get restore status

Http status code - 400 BAD REQUEST

1
2
"errorCode": "120",
"errorMessage": "The restoreId : {} is invalid or does not belong to operation Restore"

Create storage

Http status code - 409 CONFLICT

1
2
"errorCode": "128",
"errorMessage": "Conflicting Storage name = {}"

Http status code - 400 BAD REQUEST

1
2
"errorCode": "130",
"errorMessage": "Incorrect principalTag = {} or roleIdentifier = {}"

Http status code - 400 BAD REQUEST

1
2
"errorCode": "133",
"errorMessage": "Storage region = {} is not eligible for the org:{} and cloud: {}"

Http status code - 400 BAD REQUEST

1
2
"errorCode": "142",
"errorMessage": "Validation failed for storage creation for bucketName = {} and basePath = {} and region = {}"

Get storage details

Http status code - 404 NOT FOUND

1
2
"errorCode": "129",
"errorMessage": "Storage Details not found for storageId = {}"

Create export

Http status code - 404 NOT FOUND

1
2
"errorCode": "131",
"errorMessage": "No COMPLETED export found for backup = {}"

Http status code - 400 BAD REQUEST

1
2
"errorCode": "140",
"errorMessage": "Export Already in Progress"

Get export details

Http status code - 404 NOT FOUND

1
2
"errorCode": "113",
"errorMessage": "BackupId not found for exportId = {}"

Http status code - 404 NOT FOUND

1
2
"errorCode": "110",
"errorMessage": "Brie job=EXPORT with externalId={exportId} is not present"

Http status code - 404 NOT FOUND

1
2
"errorCode": "112",
"errorMessage": "Invalid cloudId={} for job=EXPORT with externalId={exportId}"

Get import details

Http status code - 404 NOT FOUND

1
2
"errorCode": "113",
"errorMessage": "BackupId not found for importId = {}"

Http status code - 404 NOT FOUND

1
2
"errorCode": "110",
"errorMessage": "Brie job=IMPORT with externalId={importId} is not present"

Http status code - 404 NOT FOUND

1
2
"errorCode": "112",
"errorMessage": "Invalid cloudId={} for job=IMPORT with externalId={importId}"

Get post operation report

Http status code - 404 NOT FOUND

1
2
"errorCode": "143",
"errorMessage": "Post operation report not available for migration = {}"