VMware Cloud Community
drdoom2k
Contributor
Contributor

Powercli migrate VM host to host with Fault Tolerance activated

Hi.

I have a vm with FT activated. With PowerCli I want to make a script for migrate the vm host to host. The primary VM no problem, but the second returns error.

Example:

VM= test3

PowerCLI C:\> Get-VM test3 | ft -Property ID -AutoSize

Id

--

VirtualMachine-vm-368 (primary)

VirtualMachine-vm-331 (secondary)

Primary runs on esxi1. I execute this command:

get-vm -ID VirtualMachine-vm-368 | move-vm -destination esxi1.test.local

The VM migrate without problem.

Secondary runs on esxi2. I execute this command:

get-vm -ID VirtualMachine-vm-331 | move-vm -destination esxi3.test.local

The task gets this error:

move-vm : XXXXXXXXXXXXX   Move-VM The operation is not supported on the object.

In line: 1 Charachter: 36

+ ... t-vm -ID VirtualMachine-vm-368 | move-vm -destination esxi4.isc.local

+                                      ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

    + CategoryInfo          : NotSpecified: (:) [Move-VM], NotSupported

    + FullyQualifiedErrorId : Client20_VMServiceImpl_RelocateVM_ViError,VMware.VimAutomation.ViCore.Cmdlets.Commands.MoveVM

Any ideas??

Best regards

Reply
0 Kudos
6 Replies
LucD
Leadership
Leadership

On which vSphere version is that?
And which PowerCLI version are you using?

Did you already check the vpxd logs, there might more explanatory messages in there.


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

Reply
0 Kudos
drdoom2k
Contributor
Contributor

Hi.

Vsphere 6.0 U3 and PowerCLi 6.5

I didn't check logs. I will do it tomorrow.

Best regards.

Reply
0 Kudos
drdoom2k
Contributor
Contributor

Hi again.

In the vpxd log only shows this line:

2017-04-20T17:26:48.795+10:00 error vpxd[05684] [Originator@6876 sub=ftUtils opID=3bd1236] Operation on VM (vim.VirtualMachine:vm-368) with name (test3) can notgo through because it is a fault tolerance secondary vm.

Best regards.

Reply
0 Kudos
LucD
Leadership
Leadership

Which seems to conflict with the info that one can vMotion a secondary FT VM.

Perhaps the Move-VM cmdlet is not calling this vMotion of a secondary FT VM correctly?

I'll have a look


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

Reply
0 Kudos
drdoom2k
Contributor
Contributor

Hi.

Any ideas?.

Best regards.

Reply
0 Kudos
ikiris
Enthusiast
Enthusiast

I'm having the same problem. I used to be able to migrate the secondary no-problem using versions esxi 5.5 -> esxi 6.0u2

Now that I'm on esxi 6.0u3, I get an error when I try to vmotion the secondary.

-Chris- http://www.twitter.com/ikiris http://blog.chrischua.net
Reply
0 Kudos