For documentation purposes, there's a more general step of "Any VM you can shut down, do". Live Migration is great for VMs which need to stay up, but it's not free, and not even cheep. You will get done quicker if you can shut down VMs you don't need, migrate fewer things, and then (re)boot everything at the end.

Yes, there's a possible weird combo between XOSTOR and HA in some situations. Let me add @ronan-a or @dthenot in the loop. It's likely that XOA disconnection is just a visible symptom of something else. It's not ultra trivial to reproduce though.

Great job, worked perfectly! Thank you very much for your fast support!

Thank you guys! Problem temporarily fixed by Vates support,

Thanks @olivierlambert , really appreciate quick help. VM migrated successfully.

Not until we can have our own piece of code doing it. Right now, it's a binary that's not Open Source made by Citrix, we cannot legally re-distribute it.

@olivierlambert Thank you. I thought maybe I was losing my mind/eye sight, especially after reading that google search indicating there was a start button in 6.

That worked; thank you!!!

I just learned something new, thats awesome

@florent sorry I said PoC as reference to our XCP-ng pool cluster, not vddk migration process Sure we've got a trial license to challenge the solution so we can open a tunnel on the XOA and eventually give some VMware credentials to make some migrations tests. We've got some non-critical VMs to make warm migrations tests on without impact. Tunnel opened -> 35803

@Danp said in VDI not showing in XO 5 from Source.: xe vdi-param-list uuid= Hi Dan, [18:52 mycsskvdcxcp03 ~]# xe vdi-param-list uuid=5f899e22-f3a7-4f0b-8de6-2b8058c0f575 uuid ( RO) : 5f899e22-f3a7-4f0b-8de6-2b8058c0f575 name-label ( RW): ADSIM-UAT_DISK01 name-description ( RW): is-a-snapshot ( RO): false snapshot-of ( RO): d31f2db0-be21-4794-b858-1bea357869c8 snapshots ( RO): snapshot-time ( RO): 19700101T00:00:00Z allowed-operations (SRO): clone; snapshot current-operations (SRO): sr-uuid ( RO): 5d22cba7-fbf6-a03b-bb73-9ffba3a3ee75 sr-name-label ( RO): SR-HDD-DEV-2 vbd-uuids (SRO): c6f4c7fa-4f6f-7999-d13c-3a29d887d828 crashdump-uuids (SRO): virtual-size ( RO): 171798691840 physical-utilisation ( RO): 50272698880 location ( RO): 5f899e22-f3a7-4f0b-8de6-2b8058c0f575 type ( RO): User sharable ( RO): false read-only ( RO): false storage-lock ( RO): false managed ( RO): true parent ( RO) [DEPRECATED]: <not in database> missing ( RO): false is-tools-iso ( RO): false other-config (MRW): xenstore-data (MRO): sm-config (MRO): host_OpaqueRef:c3426081-ce96-507b-a219-8d2cb124c3ad: RW; read-caching-enabled-on-e1594701-28e9-4127-858e-74d4663669f8: true on-boot ( RW): persist allow-caching ( RW): false metadata-latest ( RO): false metadata-of-pool ( RO): <not in database> tags (SRW): cbt-enabled ( RO): false [18:54 mycsskvdcxcp03 ~]# Best regards, Azren

Restarting tool stack on master host of remote pool cleared the stuck job and backup was able run failed vms. Support ticket still open fyi.

@itservices Thanks Marc

@exetico I have updated my script. Please use your previous install file (if you have it saved) to remove your previous version (remember to save your config before running uninstall), before you proceed to install the new version.

some timeout or race condition between the end of the job and the mail generation ? perhaps putting 10sec delay to send mail ?

Ping @team-xo-backend

not better with production upgraded to 6.0.1 (XOA and XO Proxies) we will open a support ticket ps : if we delog/relog from XOA with another user, we have better chance to get the file restore working... not 100% very unstable is there a link ?!