Hi all, I've a 2 hosts setup with ovirt 4, with a bunch of machines on it. I started with an old iSCSI unit, then added a new NFS storage server and started moving all VMs. All VMs have been migrated over NFS (live storage migration works great!), but now I need to move also the hosted engine, in order to dismiss the iSCSI storage. So, what're the best guidelines to migrate ? I suspect that simply doing live storage migration will not work :) All backups of the hosted engine are available.

Thanks! Matteo _______________________________________________ Users mailing list Users(a)ovirt.org http://lists.ovirt.org/mailman/listinfo/users

Once upon a time, Simone Tiraboschi <stirabos(a)redhat.com&gt; said: > unfortunately moving an existing hosted-engine env from one storage kind to > another (without manually touching the engine DB) is currently not > supported. Please see: > http://lists.ovirt.org/pipermail/users/2016-July/041526.html I'm digging through this now, as I need to move my oVirt 3.5 setup from one storage array to another (both iSCSI), including the hosted engine. Reading this: https://bugzilla.redhat.com/show_bug.cgi?id=1240466#c21 it sounds like that's not currently possible (at least with 3.5). Is that correct? I was planning to follow this process: https://www.ovirt.org/documentation/admin-guide/hosted-engine-backup-and- restore/ which says "point to the new shared storage" - will that not work?

-- Chris Adams <cma(a)cmadams.net&gt;

Once upon a time, Simone Tiraboschi <stirabos(a)redhat.com&gt; said: > The issue is that the engine DB backup you are going to restore already > contains a reference to the previous hosted-engine storage domain and to > the previous hosted-engine VM and so on and so the auto-import procedure to > have the engine VM looking up for its own infrastructure will not trigger. > You have to manually remove them form the DB you restored. Okay, that makes sense. I see this from you: https://gerrit.ovirt.org/#/c/64966/ Should that work okay with a 3.5 database? I'm familiar with SQL, so if it needs some tweaks, I can handle that (just looking really to see if that's the right general idea).

If so, could I connect the new iSCSI storage to a host, shutdown the engine, "dd" the engine over, start up the new location in single-user mode, and make the DB change? Basically, just wondering if I could skip the full install and jump right to an installed system.

Thanks for your help. -- Chris Adams <cma(a)cmadams.net&gt;