To upgrade vCloud Director to a new version, you shut down the vCloud Director services on all cells in the server group, install the new version on each server, upgrade the vCloud Director database, and restart the vCloud Director cells.

You can use the vCloud Director installer for Linux to upgrade a vCloud Director installation that consists of vCloud Director appliances or vCloud Director installations on a supported Linux OS. You can either Perform an Orchestrated Upgrade of a vCloud Director Installation or Manually Upgrade a vCloud Director Installation. With the orchestrated upgrade, you run a single command which upgrades all cells in the server group and the database. With the manual upgrade, you upgrade each cell and the database in a sequence.

Starting with vCloud Director 9.5:

  • Oracle databases are unsupported. If your existing vCloud Director installation uses an Oracle database, see the Workflow for Upgrading a vCloud Director Installation with an Oracle Database.

  • Enabling and disabling ESXi hosts is unsupported. Before starting the upgrade, you must enable all ESXi hosts. You can put ESXi hosts in maintenance mode by using the vSphere Web Client.

  • vCloud Director uses Java 8 Update 181, which introduces improved LDAP support. If you are using an LDAPS server, to avoid LDAP login failures, you must verify that you have a properly constructed certificate. For information, see the Java 8 Release Changes at https://www.java.com.

When you are upgrading vCloud Director, the new version must be compatible with the following components of your existing installation:

For information about upgrade paths and compatibility of vCloud Director with other VMware products and with third-party databases, refer to the VMware Product Interoperability Matrices at http://partnerweb.vmware.com/comp_guide/sim/interop_matrix.php. If you plan to upgrade vSphere or NSX components as part of the vCloud Director upgrade, you must upgrade them After you Upgrade vCloud Director.

After you upgrade at least one vCloud Director server, you can upgrade the 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 verify that no tasks are active on any server before you begin the upgrade.

The upgrade also preserves the following artifacts, which are not stored in the vCloud Director database:

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

  • Microsoft Sysprep files used for guest customization support are copied to the new installation.

The upgrade requires sufficient vCloud Director downtime to upgrade all servers in the server group and the database. If you are using a load balancer, you can configure it to a return a message, for example, The system is offline for upgrade.

Workflow for Upgrading a vCloud Director Installation with an Oracle Database

Before upgrading a vCloud Director installation that uses an Oracle database, you must migrate the database to PostgreSQL from vCloud Director version 9.1.

  1. If your current vCloud Director version is earlier than 9.1, upgrade to version 9.1.

    For information about upgrading vCloud Director to version 9.1, see the vCloud Director Installation and Upgrade Guide 9.1.

  2. When your vCloud Director installation is of version 9.1, migrate the Oracle database to a PostreSQL database.

    For information about migrating to a PostgreSQL database, see the cell management tool reference in the vCloud Director Administrator's Guide documentation.

  3. Upgrade your vCloud Director installation from version 9.1. You can either Perform an Orchestrated Upgrade of a vCloud Director Installation or Manually Upgrade a vCloud Director Installation.