Type Alias: TakeRuntimeBackupAsClusterAdminErrors
type TakeRuntimeBackupAsClusterAdminErrors = object;
Properties
400
400: ProblemDetail;
The request names a backupId while at least one targeted physical tenant generates its own ids, or omits it while at least one does not, or the id is not a positive number. No tenant was triggered. A targeted tenant that rejects the request as invalid during the fan-out answers with the same status but the cluster body, listing the tenants that were triggered.
401
401: ProblemDetail;
The request lacks valid authentication credentials.
404
404: ProblemDetail;
The requested physicalTenantId does not exist in this cluster, so no tenant was triggered.
409
409: ClusterTakeRuntimeBackupResponse;
At least one targeted physical tenant already holds a backup with this id or a higher one. Backups are triggered without a preceding check, so the tenants that accepted the id are listed in the body and keep running; delete them before retrying.
500
500: ClusterTakeRuntimeBackupResponse;
At least one targeted physical tenant could not be triggered, and the failures do not agree on a single status. The body lists the tenants that were triggered and keep running.
502
502: ClusterTakeRuntimeBackupResponse;
The connection to the broker was cut mid-flight on at least one targeted physical tenant, which may or may not have accepted the request. Those tenants are reported as UNKNOWN with the id to check them under, and the tenants that were triggered keep running.
503
503: ClusterTakeRuntimeBackupResponse;
At least one targeted physical tenant could not be reached. The body lists the tenants that were triggered and keep running.
504
504: ClusterTakeRuntimeBackupResponse;
The request from gateway to broker timed out on at least one targeted physical tenant, which may or may not have accepted it. Those tenants are reported as UNKNOWN with the id to check them under, and the tenants that were triggered keep running.