Bind the recovered servers' backups back home
POST/v1/protection-groups/:id/failback-bindings
At a group's home after a failover, proposes and then creates the recovery bindings that let this region adopt the backups of the servers the other region recovered, so a failback can write them back into the originals. The proposal is exactly the set the other region's newest record of recovering the group names: one binding per member, from the repository the record was read from, into the group's project. A member already bound into the project keeps its binding; one bound into another project is refused with binding_conflict. With dry_run=true the request answers the proposal and creates nothing. Operator only.
Operator only: needs a system-scoped token.
Request
Responses
- 200
- 201
- 400
- 401
- 403
- 404
- 409
- 413
- 415
- 503
- default
OK.
With dry_run=true, or when every binding already existed, the proposal. Nothing was created.
Created
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 is not an operator token.
Not Found.
not_found: No group with this id exists.
Conflict.
conflict: The group is a recovery registration; failback bindings are confirmed where the workload comes back.
no_newer_custody_elsewhere: No record of another region recovering the group has been read here.
binding_conflict: A recovered server is already bound into another project; fields names each member.
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.
Service Unavailable.
dr_not_enabled: Disaster recovery is not enabled here.
An error, as an RFC 7807 problem document.