On Tue, Apr 2, 2019 at 12:40 PM Andreas Elvers <andreas.elvers+ovirtforum@solutions.work> wrote:

> No need for that; but you will required to redeploy them from the new
> engine to update their configuration.

so I keep the old engine running while deploying the new engine on a different
storage? Curious.


No, you will need to shut it down: having two distinct engines running at the same time can be really destructive.
Please carefully follow the documentation.

Other hosts and other virtual machines can be up at restore time.
 
I don't understand what "redeploy them [the old engine hosts] from
the new engine to update their configuration" means.

In fact the current engine incarnation is running on an old cluster, that
has no access to the new storage (the cluster is to go away).
The engine is also managing the new cluster to which we want to move the engine.
The engine is the only piece that keeps us from shutting down the old cluster.
That's the motivation for restoring the engine on the new cluster.

You will have only the new cluster:
then choose the remaining hosted-engine hosts one by one, set them into maintenance mode, and click reinstall from the engine to update their hosted-engine configuration.
 
_______________________________________________
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-leave@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/
List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/WVOFX4ZXDF4PKR5JHW4BKR45ZQRC56CS/