How to migrate vCenter Server VM

[GergMN]

(Using vSphere Essentials package)

So I need to migrate my vCenter Server VM (Windows 2008 Standard) from one ESXi host to another. I've migrated several others already using the "Migrate" wizard in vCenter Server, but now I want to migrate the vCenter Server VM itself. How can I do that, since the only way I've found to migrate VM's in vSphere Essentials is through the vCenter Server, but in order to migrate that VM, it must be powered down! I've tried using the vSphere Client to log directly into the host, but there are no options there to migrate/move a VM.

[puzzledtux]

Powering down your vCenter server would not cause problems to the ESX hosts and the virtual machines. But I think it would affect DRS and HA etc if your vCenter is shutdown. I can think of using the VMware Converter to do a v2v clone of your vCenter server from one ESX to another, and I think it allows you to do it on a running virtual machine.

[dickybird]

you can try after powering off the Virtual center VM, goto VI client on the ESX host and remove it form inventory.

Then goto VI client on the other ESX host and goto the config/storage and add to the inventory the VC VM

OR using command line

vmware-cmd -s register /full/path/to/file.vmx

Vmconverter is another option I used successfully in past too for such VM

[azn2kew]

Remove from inventory and re-add would work if both hosts have access to the same datastore. Wouldn't it be nice to have Storage VMotion on all vSphere editions? It was orginally free tool from Andrew Kutz but now its only offer for Enterprise edition and I'm wondering if Andrew still make that GUI tool for free with standard, advance editions of vsphere?

If you found this information useful, please consider awarding points for "Correct" or "Helpful". Thanks!!!

Regards,

Stefan Nguyen

VMware vExpert 2009

iGeek Systems Inc.

VMware, Citrix, Microsoft Consultant

[GergMN]

I'm not worried about shutting the vCenter Server down, and Essentials doesn't have HA or FT or any of the other fancy bells & whistles, so none of that is a concern. Unfortunately, when I log into the target host with the vSphere Client, I don't have access to any of the datastores, so removing it from the current host's inventory won't help, because I can't then add it to the target host.

[AndreTheGiant]

Unfortunately, when I log into the target host with the vSphere Client, I don't have access to any of the datastores

This is not possible: you must see your datastore under Configuration / Storage

And you must be able to browse them and see VM folders.

Andre

[GergMN]

Sorry, I meant that I don't have access to the OTHER datastores on my other hosts, so I can't 'grab' the VM from one inventory/datastore and move it to the desired target host.

[AndreTheGiant]

So you have only local storage? No shared storage?

In this case you have to copy with scp, WinSCP, FastSCP (or what you want) your VM folder from one ESX to another.

Then you have to manually add to inventory (and say that you have moved the VM) and power-on.

Andre

[jasonvines]

I am investigating the same thing right now. I need to apply updates to a host but need to move vCenter to do so. These are my thoughts:

clone the running virtual center server

Migrate that clone to the second host.

Shutdown vCenter server on host A.

Turn up clone on host B.

Apply updates to host A.

[AndreTheGiant]

Hot cloing could be a "solution".

It may work...

Andre

[artist-06]

Hi guys,

I have a VC running in a VM. I can Vmotion my VC to other hosts while it is running. I am using Vsphere 4 with VC4. I even tried powering off the esx host where my VC was running, surprisingly HA kicked in powered on my VC. VC was accessable in a few minutes after it was powered on.

Is not this the way that it should work?

Burak

[jasonvines]

No the Essentials package does not have vMotion or HA. So it appears the hot cloning or manual copy of the files are the only options.

[artist-06]

OK. I got the wrong end of the stick. Min level for Vmotion is the Advanced license. Thanks for clarification.