vCloud Availability 3.5 Beta

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.5 Beta includes a number of new features:

  • Support for multiple vCloud Availability instances per vCloud Director instance. Service providers can control the accessible Provider VDCs in each vCloud Availability instance. For more information, see Cloud Deployment Architecture and Manage the Accessible Provider VDCs.
  • Cloud to cloud pairing is now possible over private networks, without having to allow public administrative access and without providing the remote site credentials. For more information, see Pair Cloud Sites.
  • Group multiple virtual machines when performing on-premises to cloud replications and manage the virtual machines as a single unit, specify boot order and boot delay settings. For more information, see Grouping VMs in a Replication.
  • Replication of additional vCloud Director settings: vApp networks, VM Guest OS Customization, and VM Guest properties. For more information, see Creating Replications and Configure the Network Settings of a Replication.
  • Traffic Monitoring for each replication, and Traffic Monitoring for each tenant. For more information, see Traffic Monitoring.

For more information, see the following documentation links:

vCloud Availability 3.5 Beta Documentation
Online Documentation PDF Documentation
Installing and Configuring vCloud Availability in the Cloud 3.5 Beta Installing and Configuring vCloud Availability in the Cloud 3.5 Beta.pdf
Installing and Configuring vCloud Availability On-Premises 3.0 Installing and Configuring vCloud Availability On-Premises 3.0.pdf
Administering vCloud Availability 3.5 Beta Administering vCloud Availability 3.5 Beta.pdf
Using vCloud Availability 3.5 Beta Using vCloud Availability 3.5 Beta.pdf

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.

  • vCloud Availability does not preserve the replication traffic information for deleted replications

    If you delete an existing replication, the information about replication traffic associated to this replication is no longer available in the vCloud Availability Portal.

    Workaround: If you want to preserve replication traffic information for a replication, avoid deleting the replication.

  • You cannot start a replication of a group of virtual machines using replication seeds

    When you configure a to-the-cloud replication for a group of VMs, you cannot start the replication from a seed.

    Workaround: To use seeds, configure replications per virtual machine.

  • Replication traffic reporting is not yet available

    The option of exporting replication traffic information in a .csv file is not yet available in vCloud Availability 3.5 Beta.


  • Changing the network settings of the source vApp that is already in replication results in both the new and the old network settings shown for the target vApp

    When you change the network settings of a source vApp after its initial replication in the target site, after synchronizing the vApp settings, the target vApp shows both the new and the old network configuration.

    Workaround: Modify the vApp settings for the configured replication. Alternatively, after you perform a failover, modify the network settings of the vApp in the target site.

  • No replication traffic is reported for replications from the cloud to on-prem

    The Traffic tab for incoming or outgoing replications from the cloud does not show any data for either live or historical network traffic.

  • The support bundle file generated from the vSphere Client Plug-In is corrupt

    When you generate a support bundle by using the vSphere Client Plug-In, the downloaded files is corrupt and unreadable.

    Workaround: Append .tar.bz2 extension to the name of the support bundle file.

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