![]() ![]() ![]() So, if you want to migrate a single VM, you need to have a dedicated PD for this operation. In my case, with 1x10Gbs link between the clusters, the migration of a standard VM (100Gb) is taking less than 1 minute, especially when the VM was already in a PD synced frequently.īe careful, when you “Migrate” a PD, it will migrate the whole list of VMs assigned to this PD. Depending on the bandwidth between the clusters, the synchronization can be fast. Of course, you need to poweroff the VM during this process. AHV will migrate your VM to the “Remote Cluster”. Then you assign your VM to this PD, click on “Migrate”. In a nutshell, all you need to do is creating a protection domain (PD) between your two clusters. This script is based on the first scenario from the KB which is using the Async DR functionality. For the lazy one, the whole script will be available “as-is” in the bottom of the article. I will present this script which will allow you to learn about Windows Presentation Foundation (WPF) and some of the nice Powershell cmdlets provided by Nutanix. To simplify all of this, I decided to write a Powershell script with a nice graphical user interface (GUI) so anyone can migrate a VM between our two clusters without risks. I am pretty sure we can find a lot of reasons to migrate VMs between AHV clusters and it is not that simple (yet)! If you are a Nutanix partner, you may install new clusters and help your customers to migrate their VMs to the new one. In my situation I needed to migrate workloads between two clusters because one of them contains less resources. Have you ever had some difficulty to migrate VM between Nutanix AHV clusters? The different scenarios provided by Nutanix available through KB 000004707 (need a support account) are manual operations and are time consuming and source of errors and confusion. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |