Attach a backup to a server
POST/v1/attachments
Presents one disk of a backup to a running server as a read-only volume, so files can be copied out with the server's own tools. resource_id picks the disk; the root disk otherwise. expires_in is how long it stays attached, as a duration such as 4h. 24 hours when left out.
Any member of the project the token is scoped to.
Request
Responses
- 202
- 400
- 401
- 403
- 404
- 409
- 413
- 415
- 422
- default
Accepted
Bad Request.
invalid_request: The body is not a single JSON object, names a field this operation does not take, or gives a value of the wrong type.
Unauthorized.
unauthenticated: The token is missing, expired or not valid.
Forbidden.
forbidden: The token may not attach backups in the backup's project.
Not Found.
not_found: The backup does not exist or is not visible to this token.
Conflict.
point_not_restorable: The backup's state is not committed or verified.
tier_unavailable: tier is rbd: attachments read the repository copy. Or the repository copy cannot be read now.
Request Entity Too Large.
body_too_large: The body is larger than the service accepts.
Unsupported Media Type.
unsupported_media_type: The body is not sent as application/json.
Unprocessable Entity.
validation_failed: point_id is not a UUID. target_instance_id is missing. expires_in is not a duration. resource_id names no disk of the backup. tier is not chunk or rbd. Or the backup is of a bucket, which cannot be attached.
An error, as an RFC 7807 problem document.