Over the last few years, I have spoken to a number of customers who have greatly benefited from the ability to live migrate Virtual Machines across different vCenter Servers that are NOT part of the same vCenter Single Sign-On (SSO) Domain, which I had first shared back in 2015 here and here. This extended capability of the Cross vCenter vMotion feature enabled customers to solve new use cases that were challenging, especially for scenarios such as Datacenter migration, consolidation or even migrating existing workloads from their current environment into new SDDC deployments such as VMware Cloud Foundation (VCF) as an example.
Although customers could initiate Cross vCenter vMotions using the vSphere API which included PowerCLI (Move-VM cmdlet was enhanced in 6.5, more details here), the overall experience was still not as friendly. This was especially true for customers who may only have a small number of VMs to migrate and prefer a UI-based interface rather than an API/CLI only option. In addition, for large number of VM migrations, there was not an easy way to perform "batch" VM migrations that was easily consumable for folks who may not have a strong background in Automation or the vSphere APIs.
Today, I am pleased to share a new VMware Fling called the Cross vCenter Migration Utility that will help simplify the consumption of initiating VM migration(s) across different vCenter Servers, especially between dispart SSO Domains where a graphical interface was not available. This solution was developed out of our VMware Cloud Foundation (VCF) Engineering group which is part of the Integrated Systems Business Unit at VMware. I had spoken to a number of folks within the group about the extended Cross vCenter vMotion capability and I was super excited when I heard they were planning to release this tool as a Fling and make it available to all customers. I was fortunately to have been involved in the project alongside the Engineering lead Vishal Gupta and we are excited that we can finally talk about this project and see how customers will be using this new tool.
UPDATE (05/07/18) - The Fling has just been updated to 2.0 with the following new features:
- Added support to select individual host as the placement target
- Added support for migrating VMs with shared datastore
- Added clone functionality in addition to relocate
- Added resource summary details for placement targets
- Added a prompt to verify site thumbprint during SSL verification
- Added a link to refresh vm list in the inventory view
- Updated REST APIs to add operation type parameter
Cross vCenter Migration Utility Fling
Cross vCenter vMotion Requirements: KB 2106952
Download Fling here
- Completely UI-driven workflow for VM migration
- Provides REST API for managing migration operations
- Works with vCenter not part of the same SSO domain
- Supports both live/cold migration of VMs
- Batch migration of multiple VMs in parallel
- Flexible network mappings b/w source and destination sites