Restore of a backup in a new controller does not work

[Guillermo]

The instructions for backup & restore in Juju provides feedback on how to restore a Juju Controller in case of a complete failure in a cluster (https://juju.is/docs/controller-backups). Following those instructions you are requested to create a new controller, and to use the "juju-restore" tool to get the data back.

The thing is that the "juju-restore" needs to be used in the same controller, and it does not support disaster recovery scenario (https://github.com/juju/juju-restore).

[Ian Booth (wallyworld)]

Yeah, the disaster recovery feature needs to be implemented.

[John A Meinel (jameinel)]

Note that as a workaround we have documented manual steps for restoring a
backup
https://discourse.charmhub.io/t/manual-steps-to-restore-a-backup/1330

They were done before the refactoring to make juju-restore a separate
process, but they likely still have the important steps.

On Wed, Apr 7, 2021, 20:05 Ian Booth <email address hidden> wrote:

> Yeah, the disaster recovery feature needs to be implemented.
>
> ** Changed in: juju
> Status: New => Triaged
>
> ** Changed in: juju
> Importance: Undecided => High
>
> ** Changed in: juju
> Milestone: None => 2.9.1
>
> --
> You received this bug notification because you are subscribed to juju.
> Matching subscriptions: juju bugs
> https://bugs.launchpad.net/bugs/1922897
>
> Title:
> Restore of a backup in a new controller does not work
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/juju/+bug/1922897/+subscriptions
>