Re: Migrate HE between ISCSI storages

I don't think you can do it from the UI. The problems is that there are several tar files that contain the location of the disks and that is being read by ovirt-ha-agent on all hosts. I think that someone with deeper experience can get involved. From System Administrator perspective I would just swap the target names (old gets new target name, new one gets old target name), but this is only if the iSCSI target is not used for anything else. Best Regards, Strahil NikolovOn Mar 11, 2019 11:25, kiv@intercom.pro wrote:
Yes.
Open Storage->Disks>Move_disk_HostedEngine:
Error.
The migrate of the disk of any other VM is successful. _______________________________________________ Users mailing list -- users@ovirt.org To unsubscribe send an email to users-leave@ovirt.org Privacy Statement: https://www.ovirt.org/site/privacy-policy/ oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/M5QRRBKBGEIEVX...

On Mon, Mar 11, 2019 at 11:44 AM Strahil <hunter86_bg@yahoo.com> wrote:
I don't think you can do it from the UI.
The problems is that there are several tar files that contain the location of the disks and that is being read by ovirt-ha-agent on all hosts.
I think that someone with deeper experience can get involved.
From System Administrator perspective I would just swap the target names (old gets new target name, new one gets old target name), but this is only if the iSCSI target is not used for anything else.
If you are moving (cloning) the hosted-engine storage domain to a different LUN exposed on the same iSCSI target basically it will be transparent since the iSCSI connection will be per target and not per single LUN. If you are instead moving to a different iSCSI target the recommended way is with backup/restore.
Best Regards, Strahil NikolovOn Mar 11, 2019 11:25, kiv@intercom.pro wrote:
Yes.
Open Storage->Disks>Move_disk_HostedEngine:
Error.
The migrate of the disk of any other VM is successful. _______________________________________________ Users mailing list -- users@ovirt.org To unsubscribe send an email to users-leave@ovirt.org Privacy Statement: https://www.ovirt.org/site/privacy-policy/ oVirt Code of Conduct:
https://www.ovirt.org/community/about/community-guidelines/
List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/M5QRRBKBGEIEVX...
Users mailing list -- users@ovirt.org To unsubscribe send an email to users-leave@ovirt.org Privacy Statement: https://www.ovirt.org/site/privacy-policy/ oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/XB2U5DEYTN3ABK...

I went the other way. Created another HE one on a new host. On a separate server, make the export domain, connected it to both HE and migrated all vm through export / import between HE. Everything went quickly and without problems.
participants (3)
-
kiv@intercom.pro
-
Simone Tiraboschi
-
Strahil