On Thu, Sep 29, 2016 at 5:26 PM, Chris Adams <cma@cmadams.net> wrote:
Once upon a time, Simone Tiraboschi <stirabos@redhat.com> 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?
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.
-- Chris Adams <cma@cmadams.net>