The difference is that up to now, you have been using block storage instead of file storage. I would create a separate gluster volume only for the engine and then stop the engine on the iSCSI, Logout out of the iSCSI and restore the engine on the gluster volume. One benefit of Gluster is that you can make snapshots of the VM on gluster level (power off engine, snapshot , power on) before updates. Drawback of Engine on Gluster is that you need to know a little bit about Gluster in case something breaks. Best Regards,Strahil Nikolov On Tue, Jun 22, 2021 at 2:17, Chris Adams&lt;cma(a)cmadams.net&gt; wrote: I've run oVirt on iSCSI storage for years, and I've had to replace the hosted engine a couple of times (upgrade from CentOS 6 to 7, then moving to new storage). I'm looking at oVirt on hyperconverged Gluster storage.  I see pages about how to replace a host, but how do you replace the engine when needed?  Is it possible to connect a new hosted engine to the existing Gluster storage? I'm just trying to understand all the differences of iSCSI vs. Gluster before deploying it for real; if there's info online that I missed, feel free to point me to it. Thanks! -- Chris Adams <cma(a)cmadams.net&gt; _______________________________________________ Users mailing list -- users(a)ovirt.org To unsubscribe send an email to users-leave(a)ovirt.org Privacy Statement: https://www.ovirt.org/privacy-policy.html oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/RKMU5EXUBM4...