Skip to main content

Restore a backup

POST 

/v1/restores

mode is volume, instance or bucket to restore as something new, or in_place to write the backup back over the volume or server it came from. A new volume or server whose backup is on an instant tier at this site is cloned from it, as job kind instant_restore: each volume exists within seconds in the target project, nothing is read from the repository, and the clone is copied in full in the background. Every other restore reads the repository copy. Restored as new, a server can take a different flavor, networks, key_name and security_groups, and resource_ids restores only the named disks. mapping_profile applies a saved recovery profile. Anything it cannot resolve here must be confirmed by name in confirm_unresolved. A backup that does not hold every disk of its resource is refused until acknowledge_partial is set. Only an operator can restore into another project, with target_project_id. Every restore acts in its target project through a delegation the caller's token grants, and the identity service delegates only roles the caller holds in that project itself: an admin role on the system or on another project does not count, so an operator account needs a role, such as member, in every project it restores into.

Any member of the project the token is scoped to.

Request​

Responses​

Accepted