vCloud Availability 3.0.5 | 10 DEC 2019 | Build 15233044

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

Important: Since April 2021, vCloud Availability 3.0 is no longer available for download from VMware. vCloud Availability 3.0 also reached End of General Support. 

vCloud Availability 3.0.5 includes several resolved issues and updates of third-party libraries that provide security fixes.

Upgrade

You can perform an in-place upgrade directly to version 3.0.5 from version 3.0 or from versions 3.0.x. To upgrade to version 3.0.5, see Upgrading vCloud Availability in the Cloud and Upgrading vCloud Availability On-Premises.

Important: As versions 3.0.x passed End of General Support date on 11 April 2021 and are longer available for download from VMware, to upgrade to version 3.5 or to version 4.0 see:

Resolved Issues

  • In the vSphere vCloud Availability Plug-In, replication operations between vCloud Availability 3.5 and vCloud Availability 3.0.x instances may show error messages

    When performing failover, migration, and other replication operations by using the vSphere vCloud Availability Plug-In, between a site with vCloud Availability 3.5 and a site with Cloud Availability 3.0.x, you may see error messages. 

  • Opening the network settings for some vApps or virtual machines may show an error message

    For some cloud to cloud replications, when you select a vApp or a virtual machine and click Networks, you may see an error message such as Cannot read property 'nics' of null.

Known Issues

  • vCloud Availability 3.5 does not show the network settings of vCloud Availability 3.0.5 replications

    From a vCloud Availability 3.5 site, you cannot configure the network settings of replications to or from vCloud Availability 3.0.5 sites.

    Workaround: Upgrade the vCloud Availability 3.0.5 site to vCloud Availability 3.5.

  • For a vApp failover or test failover from vCloud Availability 3.0.5 to vCloud Availability 3.5, the virtual machines in the vApp are not connected to the configured network

    In the vApp, the virtual machines NICs are not attached to the organization network after a failover or a test failover from a vCloud Availability 3.0.5 site to a vCloud Availability 3.5 site.

    Workaround: 

    • In vCloud Director connect the virtual machine NICs to the created networks.
    • Alternatively, upgrade the vCloud Availability 3.0.5 site to vCloud Availability 3.5.
  • Cannot protect or migrate virtual machines or vApps that are incompatible with the destination hardware version

    When migrating or failing over a virtual machine with a hardware version that is incompatible with the ESXi host at the destination site, the vCloud Availability task completes successfully but you cannot power-on the virtual machine at the destination site. For example, at the destination site, after a failover from an on-premises site with vCenter Server 6.7 to a cloud site with vCenter Server 6.0, you cannot start a virtual machine with hardware version 13. For more information on the virtual machine compatibility, see Virtual Machine Compatibility in vSphere Virtual Machine Administration.

    Workaround: Move the virtual machine or vApp to a destination that supports the required hardware version:

    • for a vCloud Director destination, move to an Org VDC that is configured with the compatible hardware version.
    • for a vCenter Server destination, move to a cluster with a hardware version that is equal or higher than the source virtual machine.
  • For on-premises to cloud replications, configuring the network settings of a virtual machine also causes a change in its computer name

    In an on-premises to cloud replication, you can configure the destination network settings of the virtual machine. At the destination cloud site, in addition to applying the network settings, the computer name in the operating system of the virtual machine gets incorrectly changed to xxxxxxx-01, where xxxxxxx is the original computer name. As a result of this computer name change, Windows virtual machines can disjoin from the domain controller.

    Workaround: To prevent vCloud Availability from changing the computer name, set the network settings of on-premises to cloud replications in vCloud Director. If the computer name of a virtual machine changes after a failover or a migration, correct the computer name in vCloud Director.

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