On Mon, Apr 1, 2019 at 5:26 PM <andreas.elvers+ovirtforum@solutions.work> wrote:

Hi friends of oVirt,

Roughly 3 years ago a user asked about the options he had to move the hosted engine to some other storage.

The answer by Simone Tiraboschi was that it would largely not be possible, because of references in the database to the node the engine was hosted. This information would prevent a successful move of the engine even with backup/restore.

The situation seem to have improved, but I'm not sure. So I ask.

We have to move our engine away from our older Cluster with NFS Storage backends (engine, volumes, iso-images).

The engine should be restored on our new cluster that has a gluster volume available for the engine. Additionally this 3-node cluster is running Guests from a Cinder/Ceph storage Domain.

I want to restore the engine on a different cluster to a different storage domain.

Reading the documentation at https://www.ovirt.org/documentation/self-hosted/chap-Backing_up_and_Restoring_an_EL-Based_Self-Hosted_Environment.html I am wondering whether oVirt Nodes (formerly Node-NG) are capable of restoring an engine at all. Do I need EL-based Nodes? We are currently running on oVirt Nodes.

Yes, now you can do it via backup and restore:

take a backup of the engine with engine-backup and restore it on a new hosted-engine VM on a new storage domain with:

hosted-engine --deploy --restore-from-file=mybackup.tar.gz

- Andreas
_______________________________________________
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/Y7EPAGSARSUFGYRABDX7M7BNAVBRAFHS/