This scenario is a migration upgrade. The migration upgrade is a managed transition rather than a strict upgrade. By using vMotion to move virtual machines directly from one production host to another production host, you minimize downtime of the virtual machines.

The following example provides a high-level overview of the upgrade process in an environment with ESX 3.5/ESXi 3.5 or higher and vCenter Server 5.0, using vMotion to migrate your running virtual machines to ESXi 5.0. The hosts in your environment must be licensed for and able to use vMotion.

You can perform a migration upgrade without vMotion. The only difference is the amount of downtime for the virtual machines.

A migration upgrade calls for sufficient resources to run the production environment partly on older hosts and partly on upgraded hosts. Any required redundancies and safeguards must be available on both upgraded and non-upgraded infrastructure during the transition.

Verify that one or more machines meets ESXi 5.0 requirements.

Verify that empty host storage is sufficient to hold a portion of your production virtual machines. Ideally, the storage is large enough to hold all of the migrated virtual machines. A larger capacity for virtual machines on this extra storage means fewer operations are required before all your virtual machines are migrated.

If your environment has vCenter Guided Consolidation, uninstall it.

Run the vCenter Host Agent Pre-Upgrade Checker. See Run the vCenter Host Agent Pre-Upgrade Checker.

Upgrade VirtualCenter 2.5 Update 6 or higher or vCenter Server 4.0 to vCenter Server 5.0. See Upgrading to vCenter Server 5.0.

The downtime required for this upgrade is based on the amount of data in the database. During this time, you cannot perform provisioning operations, such as cloning or creating virtual machines.

Install the version 5.0 vSphere Client. See Upgrade the vSphere Client.

If your environment has vSphere Update Manager, upgrade it to the latest version. See Upgrading Update Manager.

1

Use vMotion to move the virtual machines from the ESX 3.5/ESXi 3.5 or higher host.

2

Upgrade the host to ESXi 5.0, or perform a fresh installation of ESXi 5.0.

3

Add the ESXi 5.0 host to vCenter Server.

4

Use vMotion to move the virtual machines that you removed from the ESX 3.5/ESXi 3.5 or higher host before the upgrade.

For vMotion to work, the hosts must be managed by the same vCenter Server instance.

For all hosts and virtual machines in the migration upgrade, take the following actions.

Upgrade your virtual machines. See Upgrading Virtual Machines.

Upgrade your product licenses:

a

Get your new license keys by email, or by using the license portal.

b

Apply the new license keys to your assets using the vSphere Client (or vCenter Server if you have it).

Use the vSphere Client to upgrade the host datastore to VMFS5.

See the information about upgrading datastores to VMFS5 in the vSphere Storage documentation.