Move 3.0

  • 15 March 2019
  • 9 replies
  • 2172 views

Userlevel 3
Badge +16
Derek Seaman blogged about the now renamed Move 3.0 on his site.

https://www.derekseaman.com/2019/03/nutanix-move-3-0-formerly-xtract-for-vms-now-ga.html

Here is the crux...New to Move 3.0:
  • Move services are now Dockerised and all Move and Move Agent Services now run as Docker Containers. Architecturally, this is an important milestone as we “servicify” move and provide the ability to add/update features without much service disruption as well as providing flexibility to run Move anywhere.
  • GA release of Hyper-V as a source, adding to source list of ESXi and AWS
  • 1-click upgrade of Move. (Support for dark sites ​is coming)
  • Further enhancements to User Experience for Large VM migration with enhanced status updates on the UI
  • Support for a Mixed mode of Source VM setup by allowing for a mix of automatically prepared source VMs and manually prepared source VMs in a migration plan.
  • Support for PEM based authentication for Linux source VMs running on ESXi source
What guest OSes are you migrating to your Nutanix system?

Cc: @aluciani @christievaughan

9 replies

Userlevel 2
Badge +13
I try to migrate as many as possible OSes to Nutanix... Unfortunately, not all are supported with Xtract / Move. I migrated several XP / 2003 systems manually.

Are you planning to MOVE bare metal servers to AHV with the product as well?

Regards,
Bart
Userlevel 1
Badge +3
Was waiting for this for a long time.
Was scheduling our migration manually, with move it made my life much easier.
Userlevel 2
Badge +1
Move needs to add AHV to AHV migration. This would add a method of Storage vMotion, a basic missing Hypervisor function.
Move needs to add AHV to AHV migration. This would add a method of Storage vMotion, a basic missing Hypervisor function.

Here is the process to move vms:
https://portal.nutanix.com/#/page/kbs/details?targetId=kA032000000TTqoCAG

or even easier, if you know your local Nutanix SE, ask them about "Nutanix SWAP"
Morning All. Im busy with a POC for a client. I've setup move 3.0 and added hyperv as my source environment. when I start a migration, the snapshot is done on the hyperv side and the syncing of the MoveSnap starts but after about 5-10min the process fails with the below error. Can anyone perhaps point me in the right direction on where to find the issue please?

Writer operation open on file /opt/xtract-vm/datamover/vdisk/0_0_0_867a0fe0-62e2-46e0-8953-ef4f3f5fd83f/
2bc5de66-2cf4-404a-92ad-64b0fdceff67/867a0fe0-62e2-46e0-8953-ef4f3f5fd83f/
0_0_0_867a0fe0-62e2-46e0-8953-ef4f3f5fd83f_0_0_0_867a0fe0-62e2-46e0-8953-ef4f3f5fd83f failed with 'open /opt/xtract-vm/datamover/vdisk/0_0_0_867a0fe0-62e2-46e0-8953-ef4f3f5fd83f/2bc5de66-2cf4-404a-92ad-64b0fdceff67/
867a0fe0-62e2-46e0-8953-ef4f3f5fd83f/0_0_0_867a0fe0-62e2-46e0-8953-ef4f3f5fd83f_0_0_0_867a0fe0-62e2-46e0-8953-ef4f3f5fd83f: no such file or directory
Morning All. Im busy with a POC for a client. I've setup move 3.0 and added hyperv as my source environment. when I start a migration, the snapshot is done on the hyperv side and the syncing of the MoveSnap starts but after about 5-10min the process fails with the below error. Can anyone perhaps point me in the right direction on where to find the issue please?

Writer operation open on file /opt/xtract-vm/datamover/vdisk/0_0_0_867a0fe0-62e2-46e0-8953-ef4f3f5fd83f/
2bc5de66-2cf4-404a-92ad-64b0fdceff67/867a0fe0-62e2-46e0-8953-ef4f3f5fd83f/
0_0_0_867a0fe0-62e2-46e0-8953-ef4f3f5fd83f_0_0_0_867a0fe0-62e2-46e0-8953-ef4f3f5fd83f failed with 'open /opt/xtract-vm/datamover/vdisk/0_0_0_867a0fe0-62e2-46e0-8953-ef4f3f5fd83f/2bc5de66-2cf4-404a-92ad-64b0fdceff67/
867a0fe0-62e2-46e0-8953-ef4f3f5fd83f/0_0_0_867a0fe0-62e2-46e0-8953-ef4f3f5fd83f_0_0_0_867a0fe0-62e2-46e0-8953-ef4f3f5fd83f: no such file or directory




Need to add the Move IP in the File system whitelist in Prism.
Userlevel 3
Badge +11
@MannesNijeboee Did the file system whitelist suggestion help or are you still stuck?
Morning All. Im busy with a POC for a client. I've setup move 3.0 and added hyperv as my source environment. when I start a migration, the snapshot is done on the hyperv side and the syncing of the MoveSnap starts but after about 5-10min the process fails with the below error. Can anyone perhaps point me in the right direction on where to find the issue please?

Writer operation open on file /opt/xtract-vm/datamover/vdisk/0_0_0_867a0fe0-62e2-46e0-8953-ef4f3f5fd83f/
2bc5de66-2cf4-404a-92ad-64b0fdceff67/867a0fe0-62e2-46e0-8953-ef4f3f5fd83f/
0_0_0_867a0fe0-62e2-46e0-8953-ef4f3f5fd83f_0_0_0_867a0fe0-62e2-46e0-8953-ef4f3f5fd83f failed with 'open /opt/xtract-vm/datamover/vdisk/0_0_0_867a0fe0-62e2-46e0-8953-ef4f3f5fd83f/2bc5de66-2cf4-404a-92ad-64b0fdceff67/
867a0fe0-62e2-46e0-8953-ef4f3f5fd83f/0_0_0_867a0fe0-62e2-46e0-8953-ef4f3f5fd83f_0_0_0_867a0fe0-62e2-46e0-8953-ef4f3f5fd83f: no such file or directory

Hi,
have you managed to solve this issue? I faced similar.
Move 3.0.2
Migrating from vSphere cluster to AHV, testing on one VM - Windows Server 2016 Datacenter. Whitelisted, user has permissions to create anything on AHV cluster.

Error I recieve is as follows:
Writer operation open on file /opt/xtract-vm/datamover/vdisk/a6cd46b7-f6cd-4899-a0c5-8e01b324e33a/de903ed0-6c39-479c-a2a7-b9aea19dc7d6/5006017f-3bdf-df40-69c8-6b197ff73352/2000_AMP-vSVR-12.vmdk failed with 'open /opt/xtract-vm/datamover/vdisk/a6cd46b7-f6cd-4899-a0c5-8e01b324e33a/de903ed0-6c39-479c-a2a7-b9aea19dc7d6/5006017f-3bdf-df40-69c8-6b197ff73352/2000_AMP-vSVR-12.vmdk: no such file or directory'

Regards,
A.
Badge
Move needs to add AHV to AHV migration. This would add a method of Storage vMotion, a basic missing Hypervisor function.

@bbeavis this could be done with a Nutanix Protection Domain. Since both clusters running AHV are also Nutanix clusters you can leverage the Native VM Replication to move VMs from AHV to AHV. If you're referring to cross-container migration, then yes, this needs to be fixed and I have heard it is coming in the June 2019 timeframe (yes, a basic hypervisor function for sure). There are scripts to perform this migration to make it easier but nothing inside the Prism interface as of yet.

Reply