Highlighted

Cross vCenter vMotion with Multiple Disks on different Datastores

Hello,

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.

Best regards

Markus

https://mycloudrevolution.com | https://twitter.com/vMarkus_K | https://github.com/vMarkusK
Tags (1)
0 Kudos
2 Replies
Highlighted
User Moderator
User Moderator

Is this consistent?
In other words, do you get the same error message after a stop/start of your PS session?

PS: you could try to upgrade to PowerCLI 11.2.0, but I don't think it would help in this case


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

0 Kudos
Highlighted
Enthusiast
Enthusiast

If the cmdlet is doing the job while still returning this error message, this could be a known error discussed here:

https://serverfault.com/questions/654415/powercli-move-vm-returns-failure-but-vm-still-moves

I have opened an improvement idea here:

Operation is not valid due to the current state of | VMware PowerCLI

0 Kudos