vCloud Availability 3.0.2 | 4 JUL 2019 | Build 14070735 

Check for additions and updates to these release notes.

What's in the Release Notes

The release notes cover the following topics:

What's New

vCloud Availability 3.0.2 includes a number of resolved issues and updates of third-party libraries providing security fixes.

In vCloud Availability 3.0.2, you can customize the refresh rate for retrieving vApp settings from the source vCloud Director cell. For more information, see VMware Knowledge Base article 70888.

Upgrade

You upgrade vCloud Availability from version 3.0 to version 3.0.2 by using the command-line interface of the appliance.  

You can perform an in-place upgrade from vCloud Availability 3.0, vCloud Availability 3.0.1, or from vCloud Availability for Cloud-to-Cloud DR 1.5.X.

For more information about the upgrade, see Upgrading vCloud Availability.

Resolved Issues

  • On-premises to cloud re-pair results in the on-premises vCloud Availability Replicator instance reported as offline without affecting replications

    After on-premises to cloud re-pair, the on-premises vCloud Availability Replicator instances are reported as offline and replications are displayed in red state. Despite that, vCloud Availability replicates data and disaster recovery operations pass successfully.

  • Cloud to Cloud re-pair results in vCloud Availability Replicator instances reported as offline without affecting replications

    After cloud to cloud re-pair, the remote vCloud Availability Replicator instances are reported offline and replications are displayed in red state. Despite that, vCloud Availability replicates data and disaster recovery operations pass successfully.

Known Issues

  • When performing an outgoing replication by using seed, the option to select a network is not available

    You cannot choose the target network for a virtual machine when performing a cloud to on-premises replication with a seed virtual machine.

    Workaround: After you finish the failover task, attach the target network to the virtual machine.

  • When performing an outgoing replication, you cannot advance the list of seed virtual machines past 20 in the target vCenter Server

    When you configure a cloud to on-premises replication, on the Seed VM page, if there are more than 20 seed virtual machines, clicking next page does not load the remaining inventory of the seed virtual machines in the target on-premises vCenter Server.

    Workaround: If you cannot select a seed virtual machine in the 20 listed in the target vCenter server, you can protect the cloud virtual machines, without a seed virtual machine on-premises. 

check-circle-line exclamation-circle-line close-line
Scroll to top icon