check-circle-line exclamation-circle-line close-line

VMware Cloud Director Availability™ 4.0.0.2 | 23 JUN 2020 | Build 16407624

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

VMware Cloud Director Availability 4.0.0.2 includes several resolved issues and updates of third-party libraries that provide security fixes.

What's new in VMware Cloud Director Availability 4.0, see the VMware Cloud Director Availability 4.0 Release Notes document.

Configuration Maximums

For the tested uptime, concurrency, and scale limits, see VMware Configuration Maximums.

Upgrade

VMware Cloud Director Availability 4.0.0.2 supports an in-place upgrade from vCloud Availability 3.x. For more information, see Upgrading in the Cloud and Upgrading On-Premises.

Upgrading from 4.0 to 4.0.0.x must be performed by using the command line interface. For more information, see Command-Line Upgrading.

Caveats and Limitations

For interoperability between paired sites with different VMware Cloud Director Availability versions, see Managing Connections Between Cloud Sites.

For interoperability between VMware Cloud Director Availability and other VMware products, see VMware Product Interoperability Matrices

Note: The VMware Cloud Director Availability vSphere Client Plug-In requires vSphere Client support. You can use the VMware Cloud Director Availability Portal if your vSphere environment does not support vSphere Client.

Supported Browsers

VMware Cloud Director Availability 4.0.0.2 supports the following browsers:

  • Google Chrome 78 and later
  • Mozilla Firefox 69 and later
  • Microsoft Edge 44 and later
  • Safari 13 and later

Resolved Issues

  • Cannot use test failover for replications residing on a data store that the primary resource pool of the provider VDC does not see

    In a topology where the primary resource pool of the provider VDC does not see the datastore on which the replica files of a replication are located, then the test failover for that replication does not work.