Is there a limitation known for Cross vCenter vMotion with Multiple Disks on different Datastores?
Cmdlet Failes with: Move-VM Operation is not valid due to the current state of the object.
But Tasks in both vCneter Servers resume (so far).
PowerCLI Version: VMware PowerCLI 11.1.0 build 11289667
Other Cross vCenter vMotion processes worked fine so far.
If the cmdlet is doing the job while still returning this error message, this could be a known error discussed here:
I have opened an improvement idea here: