Thanks for your answer.
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
That is great news. Just to clear things up completely: - This backup command is sufficient ? No further switches ? "engine-backup --mode=backup --file=[EngineBackupFile] --log=[LogFILE]" - Do I need to place the node to which I want to deploy engine into maintenance before doing the backup? This is referred in the stated documentation as: "If a hosted-engine host is carrying a virtual load at the time of backup [...] then a host [...] cannot be used to deploy a restored self-hosted engine." This is still true? If yes: all other precautions apply from that documentation? - before creating the new engine on the new storage, the old engine need to be un-deployed on all engine-HA hosts. I am unable to find information about this issue. Just un-deploy via web ui? - I want to deploy on a gluster volume that has been automatically created by the Node setup. The file /etc/gluster/glusterd.vol does not carry "option rpc-auth-allow-insecure on" which is mentioned in the documentation. Do I need to follow the instructions for gluster, or are settings already sufficiently set by the automatic gluster deployment done by oVirt Node setup? I already have some VM images running on that gluster storage anyway. Thanks for your help. - Andreas