Move Application Migration

Hi all!I’m trying to set up an ESXi environment in Nutanix Move but move complains that the user has insufficient access rights, despite the user being assigned the Admin role in vCenter (and on the user level, not on the group level). Insufficient privileges to perform the operation: User 'Move-User' is missing required privileges for 'vcenter.domain.obfuscated': virtualmachine.config.changetracking,virtualmachine.config.editdevice,virtualmachine.guestoperations.query,virtualmachine.provisioning.diskrandomread,virtualmachine.config.annotation,virtualmachine.config.removedisk,virtualmachine.guestoperations.execute,virtualmachine.state.createsnapshot,virtualmachine.state.removesnapshot,virtualmachine.interact.deviceconnection,global.disablemethods,virtualmachine.config.advancedconfig,virtualmachine.guestoperations.modify,virtualmachine.interact.poweroff,virtualmachine.interact.poweron,virtualmachine.config.rawdevice,virtualmachine.config.settings,global.enablemethods,global.licenses,ses

Hi!We are in the process of migrating our ESXi-vms to Nutanix AHV. Does anyone know if it is a problem to migrate a Witness VM (actually used for two 2-node clusters) to AHV with Nutanix Move or would it be better to install a new one on AHV and switch the clusters over to it?

I was able to build a Nutanix Move server on an AHV and move VMs from Hyper-V onto the AHV.I wanted to shut down the Nutanix Move server since I won't be using it for a while, so I logged in from the console(I found out when I logged in that it was Alpine Linux.) and ran the "poweroff" command, but I got an error "Operation not permitted".How can I shut it down from the console? 

Hi all, After a seeding a VM, I want to do a cutover… However, that timed out, and I see the errow below in the srcagent log..Any idea how to deal with this?Regards,Bart srcagentI1220 16:20:14.380829 7 scheduler.go:185] [VM: 10.180.1.50-VirtualMachine:vm-75] Released resources VM-P-EX03:2009 for host 10.180.1.50-HostSystem:host-70, Left 8 limits and 32 connectionssrcagentE1220 16:20:14.380844 7 commonvm.go:943] [VM: VM-P-EX03] Reader task completed with err: [Err="ServerFaultCode: Error caused by file /vmfs/volumes/5ab8ed45-09bba504-e4b4-ac162d759d80/GN3-P-EX03/VM-P-EX03_6-000001.vmdk", Location="/hermes/go/src/srcagent/esxvm.go:208", Snapshot="MOVESnap-1", VM="VM-P-EX03"] Failed to query changed blocks for snapshot. (error=0x3008)srcagentI1220 16:20:14.380868 7 esxvm.go:2003] [VM: GN3-P-EX03] Error: [Err="ServerFaultCode: Error caused by file /vmfs/volumes/5ab8ed45-09bba504-e4b4-ac162d759d80/VM-P-EX03/VM-P-EX03_6-000001.vmdk", Location="/hermes/go/src/srcagent/esxvm.go:208", Snapshot=

You can prepare and migrate VMs by using Move once the Move VM is deployed successfully. The steps involved during the entire migration process are as follows: Log on to the Move UI. Add environments for migration.For more information, refer to Adding Environment section for specific environments. Create a migration plan.For more information, refer to Creating Migration Plan section for the specific source and target. Prepare VMs automatically or manually.For more information, refer to Preparing VMs Manually and Preparing VMs Automatically section for the specific source and target. Perform test migration or cutover for migration in target environment.For more information, refer to Creating a Test Capable Migration Plan or Performing Cutover section for the specific source and target. Manage migration plans.For more information, refer to Environments and Migration Plan Management. Note: Before you migrate VMs, Move does not detect whether the source VMs have security construc

Just wondering if i need to convert the thick disk to thin provision disk prior to the migration process from VMware to Nutanix.

Hello, I’m facing this issue migrating a Windows VM from vCenter 5.5 to AHV 5.20 with Move 4.2.0. Migration Status “Failed” with Reader Client error: context deadline exceeded error. also in logs I found this errors:in srcagent.logI1124 14:02:28.270928      10 uvmcontroller.go:1092] [VM:'Migration-test1' (moID:vm-3682)] Cancelling context in UVM pre-migration operation. Got Context error: [<nil>]I1124 14:02:28.278034      10 esxvm.go:1205] [VMMoID: VirtualMachine:vm-3682] Prepare access for VME1124 14:03:28.278714      10 diskreaderclient_grpc_impl.go:65] failed to connect to diskreader grpc server running on port: diskreader:8092. Got error [context deadline exceeded]E1124 14:03:28.278811      10 esxvm.go:1168] Failed to connect with Disk Reader Service: [Location="/hermes/go/src/diskreader/client/diskreaderclient_grpc_impl.go:66", Msg="context deadline exceeded"] Reader client error (error=0x1001)E1124 14:03:28.278834      10 esxprovider.go:875] [VM:'Migration-test1' (moID:vm-3

It can be found that, when using Nutanix Move to migrate older Windows VMs, an error is exhibited regarding a failure to install the Nutanix App Mobility device drivers and to check if the operating system is SHA2 compatible. This can be due to the fact that certain Windows operating system versions (such as Windows 7 and Windows Server 2008R2) do not natively support SHA2-signed drivers, which is the type of drivers that Nutanix Move uses.This condition can be overcome by: Ensuring that the operating system has all of the latest updates (which are available for it) installed Confirming specifically that Microsoft KB 3033929 is installed. More information regarding this can be found within the VirtIO 1.1.6 installation on Windows 7, Windows Server 2008 R2 knowledge base article.

Hello Team,I am working on a project where Nutanix Move will be highly leveraged for migration from Hyper-V, VMware to AHV Cluster. I know the ports that are required to be opened between diff source and destination, however customer is asking for more details as in what is the usage of the ports. Do we have any docs with detailed explanation on port usage? For example usage of ports 2049 (I know its for udp nfs but little more details :))Also some of the follow up questions:Is it mandatory to open port 80 (http) for Nutanix Move to work? Cause in this environment only secured communication is allowed 443 (https) Port 22 used for SSH to Linux VMs - Does it use asymmetric or symmetric encryption?Please advice. Thank you in advance!

Nutanix Move is a cross-hypervisor mobility solution to move VMs with minimal downtime. Move supports migration from the following sources to targets, where first platform being the source and second platform being the target. MOVE-where to where?From ESXi to AHV, Legacy ESXi to Nutanix ESXi,AHV to EC2, Azure to AHV, Azure to ESXi on Nutanix,Hyper V to ESXi on Nutanix,HyperV to AHV, HyperV to Nutanix on AWS. What can MOVE do for you?Migration of power on/off VMs,pause and resume migration,schedule the migration activity,centralized platform for migration between several clusters,schedule data-seeding for the virtual machines in advance and cut over to a new AHV cluster, cancel migrations, monitor the migration activity at granular level. Deployment of MOVEThe MOVE package is available in the downloads section of the portal and can be installed on AHV or ESXi. Move must be able to communicate with vCenter Server on port 443, ESXi hosts on 902 and 443, and AHV on 9440. The move package m

While moving our vm’s from our old storage (ESXi) to our new storage (AHV) two of our vm’s are stuck on consolidating the disk and removing snapshots. Because of this the move to AHV keeps failing and we can’t shutdown the guest while it is consolidating. Any ideas on how we can fix this?

Can we migrate VM from KVM to Nutanix AOS using MOVE feature?

I am using MOVE 4.1 and uncovered a bug where the migrated machine network card fails to build properly.  In the windows server adapter configuration GUI the NIC shows as configured for DHCP.  You can edit that nic by clicking on the IPv4 and assigning an IP and all configuration items. As soon as you save and go back into the settings the IPv4 shows as being DHCP.  However; when you do a command prompt ipconfig /all the static IP actually does stick and is configured and the server responds to network pings/dns.  Troubleshooting attempted: Delete all registry items for the Network card GUID. Uninstalled adapters from device manager (hidden and visible). netsh winsock reset. netsh interface tcp reset. Deleted NIC and reprovisioned NIC. Rebooted after all action items tested. There is an issue with MOVE 4.1 that has to be causing this and I have a case open with NTX Engineering for resolution. I am rolling back to MOVE 3.7.

Hi,Having an issue migrating a Windows Server 2019 OS into Nutanix. We are using version 4.1.0 of Move and we have successfully migrated one VM already. However this 2nd VM fails with a “Query Changed Page Ranges” failed message. It appears to be able to create a snapshot of the disk but then fails after a while. Any ideas?

Hi All, Would like to seek your advice/recommendation way to migrate physical linux/windows to Nutanix AHV via free tools ONLY without purchase third party tools or additional costs. Just wondering is there any tools that available for us or any alternative way without any additional costs?  We have some requirements;5 physical linux servers. 5 physical windows servers. Appreciate it in advanced. Regards,John

Interested to test Nutanix Move on my CE installation in my lab. But I didn't found how to download it without registration on portal , that require real Nutanix serial number. How may I download Nutanix move? Please provide needed link.

Two separate but related questions to Move:I’d like to confirm/verify regarding the Antivirus requirement. Many AV vendors offer the ability to temporarily disable their scanning engines (or at least they used to) except for MS Defender (aka MS Security Essentials/Windows Defender/Microsoft Defender/aka MS Defender 365 etc - either paid or free versions https://techcommunity.microsoft.com/t5/microsoft-365-defender/advanced-hunting-product-name-changes/ba-p/2009233).During an unrelated troubleshooting support call with Microsoft, they indicated that the Defender engine cannot be turned off/it’s built into the OS.Q1:So, as long as VirtIO drivers are able to get installed while Defender is running, is Microsoft’s Defender product exempt from the AV requirements mentioned above?Q1.1: Are there any particular settings/combination of requirements (i.e. CIS level 1 or 2 like configuration items for Defender) that would not be supported with Move?https://docs.microsoft.com/en-us/compliance/reg

Long story short, W2016 server moving from HV to AHV. VirtIO drivers are installed but whenever the machine boots after migrating to AHV, it's bsods with inaccessible boot device. If I go through the whole booting to recovery, deleting the driver and injecting the driver, it boots up but thats a lot of manual handling.When MOVE migrates to AHV it boots up as SATA drive then it seems to clone the disk and reattaches it as a SCSI drive. It boots to the desktop as SATA but then as a SCSI drive it fails, so the driver issue makes sense. The issue is why the drivers are not working when they're installed on the HV machine before migration and don't work after.

The following migrations are not recommended, but can be performed with some limitations. Exchange should be migrated by installing newer versions of Exchange Server in parallel with existing production environments, then move user mailboxes from the old system to the new one. Domain controllers should be migrated by preparing a new domain controller, and then migrating the Flexible Single Master Operations (FSMO) roles. Move migrates database VMs similar to any other VMs;however, the migration happens at the VM level, not the application level. Move will not perform any application-level changes, disk layout updates or best practices on the migrated VM. The above approach should be fine for smaller SQL DB servers and for servers without PCI Pass-through, pRDM disks or multi-writer disks (clustered NTFS). Also, for larger SQL DB servers, Nutanix recommends you to apply Nutanix best practices to create additional vDisks and rebalance data across those disks to take advantage o

I am getting this error when adding my AWS environment to Nutanix Move toolAWS Authorization Error. RequestCanceled: request context canceled caused by: context deadline My move tool version is 4.0.0

Is it possible for purposes of DR in a cloud solution to move just the VMWare environment?Can you replicate your Production Nutanix VMware environment to a cloud based solution? Say IBM cloud? They say you can but i guess i am having a hard time seeing how that will work? I am really new to the whole cloud solution arena and my company wants to move our DR\Datacenter to cloud? We have business reasons for using IBM cloud but they do not have a nutanix cloud infrastructure but tell us we can bring our VMWare environment. 

I’m just getting started with Move. We need to move VMs from an ESXi cluster to a new Nutanix AHV cluster. The ESXi hosts are managed by vCenter.Do I start by deploying the Move appliance in vCenter or on the Prism Central or PE?The Release Notes for 4.0 show our versions of ESXi, vCenter, AOS and Prism Central are supported.

I have just install Move 4.0.0 and need to set the static IP address. I am using the procedures in the Move User Guide. When I bring up the console from PE, I am having prompt synchronization problems.The prompt appears after I provide the input. For example, I do not get a login prompt, but type the user id, then I get no prompt for password but enter the password. I was able to figure out the sequence to get through the password change without prompts, but now I can’t make it through the static IP configuration.Is any else having this problem and knows how to fix it?

Hi All,Does Nutanix Move support to move from google cloud platform (GCP) workflow to Nutanix AHV (On-premise)? Is there any alternative way for this?

Nutanix Move 4.0.0 was just released today.You can read more about it in our product updates community section.Let me know what you think about this release.Be sure to register for our annual .NEXT user conference happening September 20-23, 2021 online. It’s Cloud on your terms.