5.1

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,” on page 9 is required to use
networking features introduced in this release of vCloud Director.See “Upgrade vShield Manager,” on
page 46
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,” on page 47. 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,” on page 9.
9 Review the changes in your upgraded networks and reconfigure firewall rules as needed. See “Changes
to Upgraded Networks,” on page 48.
Using a Load Balancer to Reduce Service Downtime
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,” on page 35.
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,” on page 42.
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,” on page 44.
6 Restart vCloud Director on the upgraded servers. See “Start or Stop vCloud Director Services,” on
page 29.
7 Upgrade vShield Manager. See “Upgrade vShield Manager,” on page 46.
8 Upgrade vCenter and ESX/ESXi Hosts. See “Upgrade vCenter, ESX/ESXi Hosts, and vShield Edge
Appliances,” on page 47.
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,” on page 42.
11 Review the changes in your upgraded networks and reconfigure firewall rules as needed. See “Changes
to Upgraded Networks,” on page 48.
vCloud Director Installation and Upgrade Guide
34 VMware, Inc.