Cross-vCenter vMotion

Traditionally, vMotion has been an intra-cluster solution for balancing workloads. vSphere 6 pushed vMotion further, allowing you to migrate VMs across clusters, virtual standard switches, virtual distributed switches, and vCenter Servers. In addition, you can migrate between geographically dispersed environments with an RTT of 150 ms or less.

Although these capabilities provide an increase in mobility of workloads, what are the operational impacts? The good news is that the universally unique identifier (UUID) of the VM (not to be confused with the BIOS UUID) is retained during the transfer, so most of the information that you want is transferred along with the VM. vSphere HA configurations and DRS rules, events, tasks, and alarms will all move with the VM, as will any configured shares, reservations, or limits. The only downside is that performance data—which is written to the vCenter Server database—will not be migrated with the VM. (Note, however...