Move Application Migration
Migrate applications to the cloud in a single click
- 119 Topics
- 229 Replies
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?
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
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
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?
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.
After converting a VM running Windows 2012 r2 from VMware to Nutanix using Move version 3.4.1, we are receiving event IDs 257 and 259 regularly as shown below.Log Name: ApplicationSource: vmStatsProviderDate: 3/15/2021 8:35:34 AMEvent ID: 257Task Category: GeneralLevel: ErrorKeywords: ClassicUser: N/AComputer: ServerADescription:The "vmStatsProvider" can not be initialized. "vmGuestLib" returns error "VMware Guest API is not running in a Virtual Machine" (2). Log Name: ApplicationSource: vmStatsProviderDate: 3/15/2021 8:35:34 AMEvent ID: 259Task Category: Guest Library APILevel: ErrorKeywords: ClassicUser: N/AComputer: ServerADescription:Unable to start "vmGuestLibrary". Error: "VMware Guest API is not running in a Virtual Machine" (2).VMware Tools is still installed on the server however it won’t uninstall cleanly after the migration so I’ve disabled all of the ‘VMware’ services i
We’ve migrated a handful of test VMs from our vSphere legacy architecture to Nutanix (also running ESXi) Both on ESXi 6.5 and latest Prism/software builds, etc. When using Nutanix Move to do the migration, we’ve noticed that the migrated VM is taking on GMT for its time when the VM boots up. We are in Michigan so the VM is five hours ahead, but the local windows timezone Eastern. After logging in and/or rebooting, the time typically syncs up fine. However, this proved to be a major problem when we moved a domain controller and it caused time to be off everywhere. ncc health_checks network_checks check_ntp all comes back fine and our time sources are defined properly both in Nutanix as well as NTP oin the ESXi host. What are we missing or is this a bug?
We are migrating workloads from VMware (vSphere 6.5) to Nutanix AHV (AOS 5.15 LTS). With regards to VM templates, any advantage in creating new templates on AHV? Any gotchas if we migrate (as per procedure, prepare and use Nutanix Move) VM templates to AHV? Anyway, we will have to migrate most workloads, but was wondering about VM templates. We’re leaning towards erring on the side of caution and creating new templates (Linux/Windows) on AHV. However, I just wanted to know if anybody experienced issues with VMs built from migrated templates on AHV and any feedback.
I’m trying to move a VM (Ubuntu 18.04), when the cutover is done and i make a console connection the VM, at first the screen is blank, but after a few enters, i start getting the following signs on the console:Anyone has any ideas how to avoid this? I’ve tried installing NGT prior to moving the VM - no luck. On the initial GNU GRUB screen where I choose which OS to boot, everything is fine.
When migrating Windows VMs from AWS into a Nutanix cluster and while using automatic Windows VM preparation, it is important to verify permissions configurations in two places within AWS. Specifically, the permissions for the AWS account that is provided when adding an AWS source into Move and the permissions of the IAM profile associated with the VM instance to be migrated. AWS allows permissions configurations to be viewed/updated in a JSON format. Further, the Move User Guide also lists the necessary permissions for these entities in a JSON format. These JSON values can then be reviewed/compared and, if any of the permissions are missing or configured incorrectly from AWS, simply update the permissions according to the User Guide values. Also, it should be verified that the Windows VM instance is properly managed by the AWS SSM Manager prior to a migration attempt. Further information regarding this can be found within the AWS to Nutanix Clusters on AWS and AHV VM Migration section
If I want to migrate Linux (Centos,RHEL,Ubuntu/SUSE) Vms from VMware to AHV using Nutanix move then is below information enough.Below are the configuration settings to look out for when migrating a Linux VM using credentials. Ensure ssh localhost using only password authentication, ie. set “PasswordAuthentication yes” in sshd_config Ensure using sudo, user assume root privileges without entering a password Ensure read and write permission for /tmp. root access, sshd service running If this is correct then I can normally migrate the Linux VMs same as I migrated the Windows VM?
So guys I’ve got a flexlm license server running Windows Server 2019 that I am trying to use Move to migrate into my AHV cluster. I tried migrating it once and it blew up the license server since I guess it builds a unique machine ID using a disk and perhaps CPU ID. Any idea on how to clone this in Move so when it comes across FlexLM and other license daemons are none the wiser?
Login to the community
Login with your account
Enter your username or e-mail address. We'll send you an e-mail with instructions to reset your password.