VC Server 2 & ESX Compatibility

[eableson]

I have a client running an older version of ESX (2.x) and will be migrating to ESX 3. I was wondering what versions of ESX Virtual Center Server 2 can manage directly.

Ideally, I'd like to build the new environment up from scratch, integrate the old server into the new Virtual Center Server, stop the VMs and copy them over to the new ESX 3 servers.

Any gotchas in there that I should be looking out for?

(all the machines are using local storage)

[Texiwill]

Hello,

VC2 can manage ESX2 and ESX3. There are no version constraints that I know about as with ESX2 there is a Launch MUI option and the standard VM movement/power on links just like VC1.0.

Sounds like a very good plan.

Best regards,

Edward

[esiebert7625]

Here's some good guides to read on upgrading....

Virtual Infrastructure 3: Beta to Production - http://download3.vmware.com/vmworld/2006/mdc5173.pdf

Understanding Virtual Infrastructure Upgrade Moving to the new ESX 3.0/VC2.0 Release - http://download3.vmware.com/vmworld/2006/tac9809.pdf

Details of What's New and Improved in VMware Infrastructure 3 - http://www.vmware.com/support/vi3/doc/whatsnew_esx301_vc201.html

Vmware Infrastructure 3 Release Notes - http://www.vmware.com/support/vi3/doc/releasenotes_esx301_vc201.html

Planning a Upgrade to Vmware Infrastructure 3 - http://www.vmware.com/pdf/vi3_upgrade_plan.pdf

Vmware ESX 3.x Server and VirtualCenter 2.x Upgrade Guide - http://www.rtfm-ed.co.uk/docs/vmwdocs/ESX3.x-VC2-upgradeguide.pdf

Upgrading your VI2 to VI3 - http://www.vmware-tsx.com/download.php?asset_id=25

Fyi…if you find this post helpful, please award points using the Helpful/Correct buttons.

-=-=-=-=-=-=-=-=-=-=-==-=-=-=-=-=-=-=-=-=-=-=-

Thanks, Eric

Visit my website: http://vmware-land.com

-=-=-=-=-=-=-=-=-=-=-==-=-=-=-=-=-=-=-=-=-=-=-

[jasonboche]

I have a client running an older version of ESX (2.x)

and will be migrating to ESX 3. I was wondering what

versions of ESX Virtual Center Server 2 can manage

directly.

VC1.x will manage ESX2.x hosts

VC2.x will manage ESX2.x and ESX3.x hosts

Ideally, I'd like to build the new environment up

from scratch, integrate the old server into the new

Virtual Center Server, stop the VMs and copy them

over to the new ESX 3 servers.

Any gotchas in there that I should be looking out

for?

(all the machines are using local storage)

Since all hosts have local storage, you can't take advantage of shared storage and the benefits that come with that such as VMotion and DMotion. Furthermore, once you are on ESX3, you won't be able to utilize DRS and HA.

You'll have to rebuild each host one at a time. What I would do is power down the VMs on the host to be upgraded, cold migrate those VMs to another 2.x host, then either rebuild (prefer) or upgrade your ESX2.x host to ESX3.x. Get your local data store formatted VMFS3, get your networks set up, then start cold migrating VMs back to the new ESX3 host. Repeat that process until all hosts are upgraded to ESX3. Along the way, or at the end, whichever you choose, you'll need to upgrade virtual hardware for your VMs and upgrade VMware Tools.

[eableson]

Actually in digging around, I did find that there are a number of subtle version limitations that need to be taken into account in this kind of scenario. I'm well aware that in this structure the client can't use DRS, HA, etc. but they're just taking baby steps right now and have no budget for a SAN right now.

In any case, there are some limitations of migrations between the various versions. I did finally find the following technote : which clearly states that:

"When performing migration upgrades using VMotion, you transfer virtual machines from a host with a supported version of ESX Server 2.x to an ESX Server 3.0.1 host. The following versions of ESX Server 2.x are supported for migration upgrades:

ESX Server 2.1.2

ESX Server 2.1.3

ESX Server 2.5.2

ESX Server 2.5.3

If you use unsupported versions of ESX Server 2.x, upgrades can fail. To avoid data loss or corruption, do not attempt to perform migration upgrades from the following unsupported versions:

ESX Server 2.5.0

ESX Server 2.5.1

ESX Server 2.1.0

ESX Server 2.1.1

ESX Server 2.0.x"

[eableson]

Check out that technote - that would be a really ugly situation to get into on a client site if they hadn't applied a patch and the VMs were corrupted in transit.

[jasonboche]

This is a good point no matter what migration method you choose, you should always ensure the safety and recoverability of your VMs should something go wrong.

Back up the VMs before migrating/converting them.

VMs should be backed up on a regular basis anyway.

[dmaster]

Hello maybe you are allready aware of.. but just incase..

it's true that you can host ESX 2 servers in Virtual Center 2.. but the virtual center agent licenses are not compatible and not working within Virtual Center 2 server

AND now comes the tricky part.. you cannot purchase seperate virtual center 2 agent licenses from VMware..

the only way is to upgrade you existing licenses to ESX 3 and use this lisence file in Virtual Center 2.