Recovery

Adopts backups that another cloud wrote into a repository this cloud can also read. An operator reads what a repository holds and binds a resource from the other cloud to a project here. That resource's backups then appear in the project and restore like its own. Recovery profiles translate the other cloud's flavors, networks and volume types into this cloud's. A dry run shows what a recovery would build before anything is created.

📄️ List recovery bindings

Operator only: needs a system-scoped token.

📄️ Bind a resource from another cloud to a project

Declares that a resource another cloud backed up into a shared repository belongs to a project here. Its backups then appear in that project and can be restored there, and new ones are picked up as they arrive. Naming a standby pool also keeps a warm copy of it. A resource can be bound once.

📄️ Delete a recovery binding

Stops picking up new backups of the resource. Backups already brought in stay restorable, and a standby the binding created is left in place.

📄️ Show a recovery binding

Operator only: needs a system-scoped token.

📄️ Check a recovery before running it

Works out how a bound resource's backup would be rebuilt here: the flavor, networks, volume types and other settings it would get, and what cannot be matched. Nothing is created. It uses the newest backup unless `point_id` names one, and a stored recovery profile or one given inline. Items listed in `confirm_unresolved` are accepted as they are.

📄️ List recovery profiles

Operator only: needs a system-scoped token.

📄️ Create a recovery profile

A named, reusable translation from another cloud's flavors, networks, subnets, volume types, availability zones, security groups and key pairs to this cloud's. Restores and dry runs of that cloud's backups use it by name.

📄️ Delete a recovery profile

Operator only: needs a system-scoped token.

📄️ List what a repository holds

Every backup found in the repository, including those another cloud wrote. Each one carries the recovery binding that covers it. Where a project of the same id exists here, that project is proposed as the owner, to confirm. The answer also lists the parts of the repository that cannot be read yet, such as a dedup domain whose key has not been imported. With `view=groups` it lists instead the protection groups the repository describes, each at the newest version of its document read here, with the recovery registered here for it, if any; a domain whose key is missing hides its groups and is listed as unreadable.