Hi,
On Sun, Jan 14, 2024 at 3:03, redhat@intheoutback.com<redhat@intheoutback.com> wrote:Hi, I am in the process of moving our oVirt environment from a self hosted engine to a standalone engine on it's own HW. I have Googled and found a procedure for standalone > self hosted, but not the other way around.My current situation is that I have 5 locations running oVirt 4.3 with 3 to 4 hypervisors and iSCSI storage backend, with a self hosted engine. All these locations are operational and short a downtime is acceptable if a must, losing a VM is NOT good.I also have 1 oVirt environment 4.3 with 2 hypervisors and iSCSI backend that is my QA/Test.All my networks are on internal networks with no outside world connections.Most importantly, we are also looking at upgrading from 4.3 to 4.4I have not found any straightforward way to migrate from self hosted to standalone.My current plan is to do the following.1) Create a new 4.4 standalone engine2) Remove one hypervisor from the 4.3 cluster3) Kickstart the hypervisor to RHEL 8.8 and configure ready for oVirt 4.44) Add the new host to the standalone engine.5) Shutdown and export a number of VMs in the oVirt 4.3 and import them in to the new oVirt 4.4.6) Repeat steps 2 > 5 until the everything is moved over.Just wanting to get your expert opinions on this method or is there a much quicker easier method that will not risk the chances of losing the cluster/VMs or an extended outage.Since we need to upgrade anyway from 4.3 to 4.4 I thought this the better method that upgrading the operational clusters.Thanks_______________________________________________Users mailing list -- users@ovirt.orgTo unsubscribe send an email to users-leave@ovirt.orgPrivacy Statement: https://www.ovirt.org/privacy-policy.htmloVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/