Fixed: Cross vCenter vMotion with shared storage bug

I’m in the middle of the project where I need to split up my environment into two vCenters so I decided to update part of it to vSphere 6.0 to ease up my work and operations tasks later on.

I do have a stretched infrastructure across the datacenters including storage and network, and obviously there are another ways to migrate without cross site vMotion – like disconnect target hosts from vCenter with desired VMs running there already, however you would need to account there is no MAC addressees blacklisting in this case, you cannot do it with distributed switches configured and also you will loose custom stuff like annotations.

This is were cross vCenter vMotion brings a lot of benefits and a simple GUI šŸ™‚

As I have over 150TB of the storage per site I was mostly interested about migrating VM without changing storage aka “Change compute resource only”.

And sadly I discovered vMotion option is not showing in vSphere Web Client when your VM has disks spread across multiple datastores. Web Client GUI will simple not give you this option :/. Although it works when you want to change both compute and storage, you don’t want to migrate terabytes of the storage all the time….

I’m working on this with VMware support for two weeks now and at first we couldn’t find when or why it is not working as it looked more or less, like a random behavior for us. Luckily for me they were able to simulate it in their lab as well, therefore I hope we can have a fix for it soon.

Note this issue is present in vCenter 6.0 Update 2 and in the latest Update 1 as well.

Update May 9,2016: Release notes for vCenter 6 Update 2 were updated by VMware:

vMotion and Storage vMotion Issues

  • New IssueĀ vSphere 6.0 does not support cross vCenter vMotion if a VM belongs to multiple datastoresĀ 
    Attempts to migrate a virtual machine that belongs to more than one data store, to a host on a different vCenter Server is not supported in vSphere 6.0. This issue is seen only when you useĀ Change compute resource onlyĀ as the migrate option.

Workaround: UseĀ Change both compute resource and storageĀ as the migrate option.

Update March 5, 2017: vCenter 6 Update 3 fixes the issue

Attempts to perform an exclusive compute resource cross vCenter vMotion might fail.
When a VM is migrated using vMotion or cold migrate from a vCenter to another vCenter and space available on datastore is less than size of the Virtual Machine Disk (VMDK), an error similar to the following is displayed:
insufficient space

This issue is resolved in this release

The following two tabs change content below.
Dusan has over 6 years experience in Virtualization field. Currently working as Senior VMware plarform Architect at one of the biggest retail bank in Slovakia. He has background in closely related technologies including server operating systems, networking and storage. Used to be a member of VMware Center of Excellence at IBM, co-author of several Redpapers. His main scope of work consists from designing and performance optimization of business critical virtualized solutions on vSphere, including, but not limited to Oracle WebLogic, MSSQL and others. He holds several IT industry leading certifications like VCAP-DCD, VCAP-DCA, MCITP and the others. Honored with #vExpert2015 and 2016 awards by VMware for his contribution to the community. Opinions are my own!

About Dusan Tekeljak

Dusan has over 6 years experience in Virtualization field. Currently working as Senior VMware plarform Architect at one of the biggest retail bank in Slovakia. He has background in closely related technologies including server operating systems, networking and storage. Used to be a member of VMware Center of Excellence at IBM, co-author of several Redpapers. His main scope of work consists from designing and performance optimization of business critical virtualized solutions on vSphere, including, but not limited to Oracle WebLogic, MSSQL and others. He holds several IT industry leading certifications like VCAP-DCD, VCAP-DCA, MCITP and the others. Honored with #vExpert2015 and 2016 awards by VMware for his contribution to the community. Opinions are my own!
Bookmark the permalink.

6 Comments

  1. Hi Dusan,

    Any update on this issue?

    Thanks.

    • Hi Roman,
      sorry your comment went to spam.
      As you can see vmware updated release notes. Support told me it may be fixed in update 3 planned for Q3 2016. Meanwhile they promised me a hot patch for workaround, as there is a space validation if you are using change compute and storage, which is not good, if you don’t have an additional space in your datastores. Although it will not migrate storage, it will not let you migrate because of it….

  2. Not sure why you think using vSphere API for XVC vMotion is workaround and not suitable for the production. It is pretty much what the Web Client does when you run XVC vmotion.

    Btw, you can easily resolve this bug by enhancing Lam’s script to keep disks in the same datastores when running xvc compute-only vmotion. And you don’t even need to upgrade vSphere to 6U3.

    I will create a pull request for Lam’s script on github if anyone is interested in this functionality.

    • Thank you for your comment. The reason I don’t want to use it for production is that I’m not giving out solutions for which I don’t have support for. I don’t mind to use it internally thou. Also vsphere is not a cheap product and customers expects it will work out of the box, without need to code anything. As far as I know at time I was writing my own script for xvc vmotion move-vm cmdlet didn’t suppprt multiple datastores input, I could be wrong though and will be more than happy if you can share modified script where it will work. As for now even update 3 doesn’t support moving multiple VMs at once using compute resource only with multiple datastores. Engineering is planning to fix it, but they couldn’t give me a ETA for it.

Comments are closed