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

vCloud Availability 3.5 | 14 NOV 2019 | Build 15038129

Check for additions and updates to these release notes.

What's in the Release Notes

These release notes cover the following topics:

What's New

vCloud Availability 3.5 introduces the following new features:

  • Integration with VMware vCloud Usage Meter to collect product consumption data and generate reports for the VMware Cloud Provider Program, see Add vCloud Availability in the vCloud Usage Meter documentation.
  • Support for multiple vCloud Availability instances per a vCloud Director instance. The service providers can control the accessible Provider VDCs in each vCloud Availability instance, see Cloud Deployment Architecture and Manage the Accessible Provider VDCs.
  • Cloud to cloud pairing is now possible over private networks, without allowing public administrative access and without providing the remote site credentials, see Pair Cloud Sites.
  • For on-premises to cloud replications, multiple virtual machines can be grouped and managed as a single unit, to specify boot order and boot delay settings, see Grouping VMs in a Replication.
  • Replication of additional vCloud Director settings: vApp networks, VM Guest OS Customization, and VM Guest properties, see Using Replications.
  • Traffic monitoring for each replication and each tenant; exporting of usage and traffic data, see Traffic Monitoring.
  • Datastore evacuation, vCloud Availability Replicator maintenance mode, and rebalancing replications, see vCloud Availability Maintenance.
  • Exclusion or inclusion of virtual machine hard drives in replications, see Selecting Replicated Disks.
  • Configuring the replications network settings in the target cloud site, see Configuring Network Settings of Replications to the Cloud.

Configuration Maximums

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


vCloud Availability 3.5 supports an in-place upgrade from vCloud Availability 3.0.x, see Upgrading vCloud Availability in the Cloud and Upgrading vCloud Availability On-Premises.

Caveats and Limitations

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

vCloud Availability 3.x can not pair with vCloud Availability for Cloud-to-Cloud DR 1.5.x and vCloud Availability for vCloud Director 2.x. You can migrate the protected workloads from vCloud Availability for vCloud Director 2.x to vCloud Availability 3.x, see Migrate from vCloud Availability for vCloud Director 2.0.

Note: The vCloud Availability vSphere Client Plug-In requires vSphere Client support. Use the vCloud Availability Portal if your vSphere does not support vSphere Client.

Supported Browsers

vCloud Availability 3.5 supports the following browsers:

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

Known Issues

  • The vCloud Availability vSphere Client Plug-In displays a 503 Service Unavailable screen if the browser session remains idle

    After you perform an operation by using the vSphere Client Plug-In and leave the browser session idle for a longer time, usually more than 30 minutes, the vSphere Client Plug-In times out and returns a 503 Service Unavailable error.

    Workaround: Logging out and logging back in to the vSphere Web Client does not fix the issue. To renew the vSphere Client Plug-In session, wait for several minutes and refresh the browser.

  • After upgrading the cloud site to vCloud Availability 3.5, on-premises tenants running vCloud Availability 3.0.x receive an error message when using the vCloud Availability vSphere Client Plug-In

    When on-premises tenants running vCloud Availability 3.0.x are paired with a cloud site running vCloud Availability 3.5, attempting to use the vCloud Availability vSphere Client Plug-In shows an error: Operation aborted due to an unexpected error.


    • Upgrade all on-premises tenants to vCloud Availability 3.5.
    • Alternatively, in the cloud site you can add the following property to the vCloud Availability Cloud Replication Management Appliance:
    1. Open an SSH connection to the Appliance-IP-Address and authenticate as the root user.
    2. In the /opt/vmware/h4/cloud/config/ file, add api.strict.deserialization = false.
    3. Restart the service systemctl restart cloud.service.
  • When selecting virtual machines to group in a vApp, advancing the pagination list clears the selection

    In the inventory list of virtual machines, if you select virtual machines from another page to group in a vApp, the selected virtual machines on previous pages are deselected.

    Workaround: Select to display more items per page and select virtual machines from the same inventory list page.

  • Deselecting a disk for replication removes the disk from the interface

    If you deselect a disk from a replication, you can no longer select this disc as it is removed from the user interface.

    Workaround: n/a

  • Test failover intermittently fails, leaving a pending vApp in vCloud Director

    Performing a test failover might not fail over all virtual machines successfully.

    When virtual machine operations fail, the resulting vApp is not cleaned from vCloud Director. This results in inability to import the corresponding virtual machines.


    • Execute test cleanup.
    • Manually remove any pending vApps in vCloud Director.
    • If you cannot delete the target vApps, change the vApp name in the replication.
  • In vSphere Client 6.7 Update 1, when you right-click on a virtual machine you cannot use Configure Protection or Configure Migration

     In vSphere Client 6.7 Update 1, when browsing the inventory of the virtual machines, if you right-click and select Configure Protection or select Configure Migration, the corresponding wizards do not open.


    To configure virtual machine protection or migration, use the vCloud Availability vSphere Client Plug-in or the vCloud Availability Portal.

  • Cannot configure the DNS servers by using the service management interface

    By default, the primary DNS server is set to and the secondary DNS server is not configured. Attempting to modify the DNS configuration results in no change to the DNS servers in the service management interface. This is a display issue and the DNS functionality is not affected. 

    Workaround: To verify that the DNS configuration is applied, open an SSH session to the appliance and run the following command

    resolvectl status

  • Cannot modify the domain name by using the service management interface

    In the Network Settings window, entering a domain name adds it to the Domain Search Path instead.

    Workaround: None

  • Cannot monitor traffic of vCloud Availability 3.0.x instances

    In vCloud Availability 3.5, when you click the Traffic tab for replications to vCloud Availability 3.0.x instances you see a Permission denied error message.

    Workaround: n/a