vCloud Availability 3.0.1 | 23 MAY 2019 | Build 13737106

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

This release of vCloud Availability 3.0.1 includes a number of resolved issues and provides the following new capabilities:

Restricting administrative sessions from the Internet

By default, administrative sessions to dedicated vCloud Availability appliances are restricted, based on the source IP address of the client. Combined Appliances operate as in the previous release. For more information, see Managing Public Administrative Access to vCloud Availability.

An interactive installation checklist

Simplify the vCloud Availability installation with an installation checklist available in the service management interface, that guides you through the required steps of the installation process. For more information, see Installation Checklist.


You upgrade vCloud Availability from version 3.0 to version 3.0.1 by using the command-line interface of the appliance.  You can perform an in-place upgrade from vCloud Availability 3.0 or from vCloud Availability for Cloud-to-Cloud DR 1.5.X.

For more information about the upgrade, see Upgrading vCloud Availability

Resolved Issues

  • When using the same browser tab, you can see and edit replications that belong to an organization to which you previously logged in

    After you log out from an organization, without closing the browser tab, if you log in to another organization you can see and modify the replications for both organizations. This issue manifests only when your session persists and you use the same browser tab.

  • An incoming replication using a seed VM succeeds but is not faster than a full sync

    You see that the incoming replication is successful but that the selected seed virtual machine is not removed from the vCenter Server inventory, indicating that the VM is replicated from scratch.

  • You cannot change the storage policy for outgoing replications by using the vCloud Availability vSphere Client Plug-in

    In the on-premises vCloud Availability vSphere Client Plug-in, if you try to change the storage policy of an outgoing replication, a blank window displays, and you cannot proceed further.

Known Issues

  • After deploying and configuring vCloud Availability, in the vCloud Availability Portal, on the Cloud sites page you see Login required for the local site

    Deploy and configure vCloud Availability in both cloud sites, enable the vCloud Availability Tunnel and do not restart the vCloud Availability services. Log in to the vCloud Availability Portal, click Sites and in the Management Session column you see Login required  for the local site.

    Workaround: To be able to set up a new replication, log out from the vCloud Availability Portal and log back in.

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

    After cloud to cloud re-pair, the 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.

    Workaround: In both sites, log in to the vCloud Availability vApp Replication Manager service management interface with the root user. In the left pane, click System Monitoring and under System health, click Restart service.

  • 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.

    Workaround: In the on-premises site, log in to the vCloud Availability Replicator service management interface with the root user. In the left pane, click System Monitoring and under System health, click Restart service.

  • After upgrading to vCloud Availability 3.0.1, if you upgraded from version through version 3.0, you cannot re-enable the vCloud Availability Tunnel appliance

    If you upgraded vCloud Availability to version 3.0 and later upgraded vCloud Availability 3.0 to version 3.0.1, you cannot re-enable the vCloud Availability Tunnel appliance.


    1. Open an SSH connection to the vCloud Availability Tunnel appliance and log in as the root user.
    2. Run the following command: psql -U h4postgres h4tunnel -c "UPDATE clientauth SET version=0 WHERE version IS NULL"
check-circle-line exclamation-circle-line close-line
Scroll to top icon