To upgrade to vCloud Availability 2.0 or 2.0.1, you upgrade the vSphere Replication components and redeploy the vCloud Availability Installer Appliance, the vCloud Availability Portal, and the vCloud Availability Administration Portal.

Upgrading to vCloud Availability does not require you to upgrade existing vCenter Server and vCloud Director instances. If you decide to upgrade your vCenter Server or vCloud Director instances, make sure that you do before upgrading the vCloud Availability solution. For more information about upgrading vCenter Server, see vSphere Upgrade. For more information about upgrading vCloud Director, see Upgrading vCloud Director in the vCloud Director Installation and Upgrade Guide. For more information about vCloud Availability 2.0 interoperability, see the Interoperability Pages for vCloud Availability for vCloud Director 2.0.

There should be no or minimal impact on Recovery Point Objectives (RPO) for existing replications. Existing replications might be impacted when vSphere Replication Server is down.

Configuring a new or performing a failover of existing replications is not possible when the vSphere Replication Cloud Service or the vSphere Replication Manager are down.

Upgrading vSphere Replication Components

The downloadable ISO file is the only means of upgrading the vSphere Replication components. It is important to follow the correct sequence of upgrading the individual vSphere Replication components of the vCloud Availability solution.

For more information, see Upgrading vSphere Replication Components of vCloud Availability.

Upgrading the vCloud Availability Installer Appliance

Download the latest version of the vCloud Availability Installer Appliance as an OVA file. Deploy, and configure a new appliance. By redeploying the appliance, you lose all previously created registry records, passwords, and trusted certificates.

For more information about deploying vCloud Availability Installer Appliance, see Create vCloud Availability Installer Appliance in the vCloud Availability for vCloud Director 2.0 Installation and Configuration Guide.

For more information about creating registry records, password files, and adding trusted thumbprints, see Creating a Registry File for an Automated Installation, Create Password Files on Your vCloud Availability Installer Appliance, and Add Trusted Thumbprints to the vCloud Availability Installer Appliance in the vCloud Availability for vCloud Director 2.0 Installation and Configuration Guide.

For more information about reconnecting the vCloud Availability Installer Appliance to the remaining vCloud Availability components, see Reconnecting to a vCloud Availability Component in the vCloud Availability for vCloud Director 2.0 Administration Guide.

Upgrading the vCloud Availability Portal Host

To upgrade the vCloud Availability Portal to version 2.0 or 2.0.1, you create and configure a new host.

For more information, see Create vCloud Availability Portal Host and Configure vCloud Availability Portal Host in the vCloud Availability for vCloud Director 2.0 Installation and Configuration Guide.

Upgrading the vCloud Availability Administration Portal Host

To upgrade the vCloud Availability Administration Portal to version 2.0 or 2.0.1, you create and configure a new host.

For more information, see Create vCloud Availability Administration Portal and Configure vCloud Availability Administration Portal in the vCloud Availability for vCloud Director 2.0 Installation and Configuration Guide.

Upgrading Third-Party Components

Upgrading to vCloud Availability 2.0 or 2.0.1 does not require you to upgrade existing Cassandra and RabbitMQ instances. If you decide to upgrade your Cassandra and RabbitMQ instances, follow the instructions provided by the respective vendor. For more information about upgrading Cassandra, see the Apache Cassandra Documentation. For more information about upgrading RabbitMQ, see the RabbitMQ Documentation provided by Pivotal.