To upgrade vCloud Director to a new version, 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.
If your existing vCloud Director server group consists of vCloud Director installations on Linux, you can use the vCloud Director installer for Linux to upgrade your environment. As an alternative, you can migrate your environment to a vCloud Director 10.0 appliance. See Migrating to vCloud Director Appliance.
If your existing vCloud Director server group consists of vCloud Director 9.5 appliance deployments, you can only migrate your environment to a more recent version of the vCloud Director appliance. Use the vCloud Director installer for Linux to upgrade the existing environment only as part of the migration workflow. See Migrating to vCloud Director Appliance.
For vCloud Director installations on Linux, you can either perform an orchestrated upgrade, or manually upgrade vCloud Director. See 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.
For the upgrade of vCloud Director appliance version 9.7 to version 10.0, see Upgrade the vCloud Director Appliance.
- Oracle databases are unsupported. If your existing vCloud Director installation uses an Oracle database, see the Upgrade and Migration Paths table.
- Enabling and disabling ESXi hosts is unsupported. Before starting the upgrade, you must enable all ESXi hosts. You can place the ESXi hosts in maintenance mode by using the vSphere Client.
- vCloud Director uses Java with an 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.
Starting with vCloud Director 10.0, Microsoft SQL Server databases are unsupported.
- The database software you are currently using for the vCloud Director database. For more information, see the Upgrade and Migration Paths table.
- The VMware vSphere ® release you are currently using.
- The VMware NSX® release that you are currently using.
- Any third-party components that directly interact with vCloud Director.
For information about the 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 your vSphere or NSX components as part of the vCloud Director upgrade, you must upgrade them after the upgrade of vCloud Director. See After you Upgrade or Migrate 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 the 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.
Upgrade and Migration Paths and Workflows
|Source environment||Target environment|
|vCloud Director 10.0 on Linux with an external PostgreSQL database||vCloud Director appliance 10.0 with an embedded PostgreSQL database|
|vCloud Director 9.0 and 9.1 with an external Oracle database||
|vCloud Director appliance 9.5 with an external PostgreSQL database||Not supported||
|vCloud Director 9.0, 9.1, and 9.5 on Linux with an external PostgreSQL database||
|vCloud Director 9.0, 9.1, and 9.5 on Linux with an external Microsoft SQL Server database||
|vCloud Director 9.7 on Linux with an external Microsoft SQL Server database||
|vCloud Director 9.7 on Linux with an external PostgreSQL database||
|vCloud Director appliance 9.7 with an embedded PostgreSQL database||Not supported|
|vCloud Director 10.0 on Linux with an external PostgreSQL database||N/A|