VMware Cloud Community
brantn
Contributor
Contributor

VMotion Across VCenter Multiple Datastores

I can move vms using the new cross vcenter vmotion by using "change computer resource only" as long as my vm has only one datastore. If I have more than one datastore I must use the option to change compute and storage. Is there a way to do the new vmotion without the need to change compute and storage? The storage is shared by all hosts in both vcenter environments and it works as long as I remove the extra datastores so I know all other requirements should be working as expected.

0 Kudos
4 Replies
LucD
Leadership
Leadership

Thread moved to VMware vCenter™ Server


Blog: lucd.info  Twitter: @LucD22  Co-author PowerCLI Reference

0 Kudos
virtualg_uk
Leadership
Leadership

When you have to specify both compute and storage, can you just specify the same storage destination as the source, and change the compute option as required?

There is no mention of the multiple datastore limitation in the documented requirements for cross vCenter vMotion: VMware KB: Cross vCenter vMotion requirements in VMware vSphere 6.0


Graham | User Moderator | https://virtualg.uk
0 Kudos
brantn
Contributor
Contributor

No it will not allow you to complete compute and storage without choosing a storage destination. I agree I saw nothing in requirements on datastore number as well. I narrowed it down by looking at what I could and could not vMotion. It is reproducible as soon as I add an additional datastore.

0 Kudos
mavatko
Contributor
Contributor

http://pubs.vmware.com/Release_Notes/en/vsphere/60/vsphere-vcenter-server-60u2-release-notes.html

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.

http://www.thevirtualist.org/cross-vcenter-vmotion-shared-storage-bug/

0 Kudos