Resume a halted disaster recovery run
POST/v1/protection-groups/:id/runs/:run_id/resume
Picks a halted run up again as the same run, with the same journal and ledger: steps already done are skipped, and the one that failed is looked at again before it is retried. A resumed recover first re-plans what has not run yet from the registration's mapping profile and accepted gaps, the target project and the probe configuration as they are now, so a cause fixed since the halt is honoured; boot, promote and health waits start their bound again, a member's server that failed to build is replaced, and a health gate boots a fresh probe host. The group must still be incomplete with no other run acting on it. Refused with dr_not_enabled when disaster recovery is not enabled on this service.
Any member of the project the token is scoped to.
Request
Responses
- 202
- 401
- 403
- 404
- 409
- 503
- default
Accepted
Unauthorized.
unauthenticated: The token is missing, expired or not valid.
Forbidden.
forbidden: The token may not resume runs of this group.
Not Found.
not_found: No group with this id exists in the token's project. Or the group has no run with this id.
Conflict.
run_not_resumable: The run is not halted.
group_busy: Another run is acting on the group, or the group is no longer incomplete.
Service Unavailable.
dr_not_enabled: Disaster recovery is not enabled on this service.
An error, as an RFC 7807 problem document.