To upgrade vCloud Director to a new version, install the new version on each server in the vCloud Director server group, upgrade the vCloud Director database, and restart vCloud Director services. You must also upgrade the vSphere components that support vCloud Director, including vShield Manager, vCenter, and ESX/ESXi.

After you upgrade a vCloud Director server, you must also upgrade its vCloud Director database. The database stores information about the runtime state of the server, including the state of all vCloud Director tasks it is running. To ensure that no invalid task information remains in the database after an upgrade, you must ensure that no tasks are active on the server before you begin the upgrade.

Important

The upgrade process requires you to upgrade vCloud Director, vShield Manager, vCenter, and ESX/ESXi. You must prevent users from accessing vCloud Director until the vShield Manager upgrade step is complete.

The upgrade preserves the following artifacts:

Local and global properties files are copied to the new installation.

Microsoft sysprep files used for guest customization are copied to the new installation.

If your cloud uses a load balancer, you can upgrade a subset of the server group while keeping existing services available on the others. If you do not have a load balancer, the upgrade requires sufficient vCloud Director downtime to upgrade the database and at least one server. You might also have to upgrade registered vCenter servers if they are not running a compatible version of vCenter software. Upgrading vCenter servers or ESX/ESXi hosts can incur additional vCloud Director downtime, because virtual machines are inaccessible while their hosts or vCenter server are being upgraded.

1

Disable user access to vCloud Director. If you want, you can also display a maintenance message while the upgrade is underway. See Displaying the Maintenance Message During an Upgrade.

2

Use the cell management tool to quiesce all cells in the server group and shut down vCloud Director services on each server. See Use the Cell Management Tool to Quiesce and Shut Down a Server.

3

Upgrade vCloud Director software on all members of the server group. See Upgrade vCloud Director Software on Any Member of a Server Group. You can upgrade the servers individually or in parallel, but you must not restart vCloud Director services on any upgraded member of the group before you upgrade the vCloud Director database.

4

Upgrade the vCloud Director database. See Upgrade the vCloud Director Database.

5

Restart vCloud Director on the upgraded servers. See Start or Stop vCloud Director Services.

6

Upgrade vShield Manager. All vShield Manager installations registered to this server group must be upgraded to a version of vShield Manager software that is compatible with the version of vCloud Director installed by the upgrade. If the upgrade program detects an incompatible version of vShield Manager, upgrading will not be allowed. The latest version of vShield manager listed in Supported vCenter Server, ESX/ESXi, and vShield Manager Versions is required to use networking features introduced in this release of vCloud Director.See Upgrade vShield Manager

7

Re-enable user access to vCloud Director.

8

Upgrade vCenter and ESX/ESXi Hosts. See Upgrade vCenter, ESX/ESXi Hosts, and vShield Edge Appliances. All vCenter servers registered to this server group must be upgraded to a version of vCenter software that is compatible with the version of vCloud Director installed by the upgrade. Incompatible vCenter servers become inaccessible from vCloud Director after the upgrade is complete. See Supported vCenter Server, ESX/ESXi, and vShield Manager Versions.

9

Review the changes in your upgraded networks and reconfigure firewall rules as needed. See Changes to Upgraded Networks.

If you are using a load balancer or other tool that can force requests to go to specific servers, you can upgrade a subset of the server group while keeping existing services available on the remaining subset. This approach reduces vCloud Director service downtime to the length of time required to upgrade the vCloud Director database.

1

Use the load balancer to redirect vCloud Director requests to a subset of the servers in the group. Follow the procedures recommended by your load balancer.

2

Use the cell management tool to quiesce the cells that are no longer handling requests and shut down vCloud Director services on those servers. See Use the Cell Management Tool to Quiesce and Shut Down a Server.

3

Upgrade vCloud Director software on the members of the server group on which you have stopped vCloud Director, but do not restart those services. See Upgrade vCloud Director Software on Any Member of a Server Group.

4

Use the cell management tool to quiesce the cells that you have not yet upgraded and shut down vCloud Director services on those servers.

5

Upgrade the vCloud Director database. See Upgrade the vCloud Director Database.

6

Restart vCloud Director on the upgraded servers. See Start or Stop vCloud Director Services.

7

Upgrade vShield Manager. See Upgrade vShield Manager.

8

Upgrade vCenter and ESX/ESXi Hosts. See Upgrade vCenter, ESX/ESXi Hosts, and vShield Edge Appliances.

9

Use the load balancer to redirect vCloud Director requests to the upgraded servers.

10

Upgrade vCloud Director software on the remaining servers in the group, and restart vCloud Director on those servers as the upgrades complete. See Upgrade vCloud Director Software on Any Member of a Server Group.

11

Review the changes in your upgraded networks and reconfigure firewall rules as needed. See Changes to Upgraded Networks.

If you anticipate a lengthy upgrade process and want to have the system display a maintenance message while the upgrade is underway, verify that at least one cell remains accessible while the others are being upgraded. Run the /opt/vmware/vcloud-director/bin/vmware-vcd-cell command on that cell to turn on the cell maintenance message.

[root@cell1 /opt/vmware/vcloud-director/bin]# ./vmware-vcd-cell maintenance

You can run this command on a cell before or after it has been upgraded. When you are ready to upgrade the cell or return an upgraded cell to service, run the following command on the cell to turn off the maintenance message.

[root@cell1 /opt/vmware/vcloud-director/bin]# ./vmware-vcd-cell stop