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

VMware vCloud Availability 3.0 Release Notes

vCloud Availability 3.0 | 11 APR 2019 | Build 13174385

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 vCloud Availability 3.0 solution introduces a unified product architecture for disaster recovery and migration capabilities. With vCloud Availability 3.0 you can perform:

  • Migration and Disaster Recovery of VMs from on-premise vCenter Server to a vCloud Director site.
  • Migration and Disaster Recovery of VMs from a vCloud Director site to on-premise vCenter Server.
  • Migration of vApps and VMs between two Virtual Data Centers that belong to a single vCloud Director Organization.
  • Replication and disaster recovery of vApps and VMs between vCloud Director sites.

vCloud Availability 3.0 release allows following capabilities:

  • Simplified installation
    • Appliance deployment with web-based configuration UIs.
    • A single configuration wizard for on-premise setup and pairing with the cloud site.
  • Replication management and monitoring
    • Cross-site management for all replication types.
    • Scheduling of initial sync between the source and target replications.
    • Co-existence with SDRS-enabled clustered datastore on the target site.
    • Change of replication storage policy on the target site.
    • Configuration of multiple replications using seed VMs on the target site.
  • Tenant security
    • Zero-config TLS encryption for data-in-motion with no incoming open ports required on the on-premise site.
    • Control over configuration of replications from the provider side.
  • Administrative features for providers
    • A single interface in the cloud to manage and monitor replications from multiple tenants.
    • Transfer replication ownership to the tenant. 
    • Enable policies that apply to all replication types.
    • Enable/disable network compression.
    • Monitor system health and connection state of paired sites.
    • Certificate management from the service management interface.
  • Network reconfiguration options on failover to cloud
    • Connect each NIC to a separate network.
    • Re-configure IP mode.
    • Reset MAC address.
  • Differentiation between Migrations and Protections
    • Simplified migration setup workflow.
    • Separate usage reporting.
  • Integrations
    • vCloud Availability plug-in for vCloud Director
    • vCloud Availability plug-in for vSphere Client


vCloud Availability 3.0 supports in-place upgrade from vCloud Availability for Cloud-to-Cloud DR 1.5.X. For more information, see Upgrading vCloud Availability.

You can also migrate your protected workloads from vCloud Availability for vCloud Director 2.X. For information, see Migrate from vCloud Availability for vCloud Director 2.0 to vCloud Availability DR 3.0.

Operational Limits

The following operational limits are discovered through rigorous testing of different disaster recovery scenarios. 

Scale Limits

  • 300 tenants with active protection paired to Cloud
  • 10 vCloud Availability Replicator instances per Cloud
  • 2000 active protections per vCloud Availability Replicator instance
  • 9500 active protections across tenants to a Cloud
  • 5TB protected VM size (Maximum Protected VM size depends on the size of single data store available on the cloud)

Concurrency Limits

  • 200 concurrent Protect, Test Failover, Failover, Reverse protect operations from on-premise to cloud
  • 200 concurrent Protect, Test Failover, Failover operations from cloud to cloud
  • 100 concurrent Reverse protect operations from cloud to cloud

Caveats and Limitations

The vCloud Availability vSphere Client plug-in requires you to use a vSphere version that supports the vSphere Client. If you use earlier version of vSphere, you cannot perform disaster recovery operations from the vSphere Web Client. If your vSphere does not support the vSphere Client, you can perform all disaster recovery operations from the vCloud Availability Portal. For information about interoperability between vCloud Availability 3.0 and other VMware products, see VMware Product Interoperability Matrices.

Known Issues

  • You cannot re-protect a replicated VM from a secondary vCloud Availability instance

    If а vCloud Availability appliance is corrupted, previously configured replications cannot be re-protected from a secondary vCloud Availability appliance. When you perform a migrate or protect operation on a replicated VM, you receive the following error message and you cannot perform any further operations:

    The virtual machine has an active replication enabled.

    Workaround: To work around this issue, see

  • After upgrading to vCloud Availability 3.0, the pairing of two sites fails

    After you upgrade from vCloud Availability for Cloud-to-Cloud 1.5 to vCloud Availability 3.0, pairing between two sites fails with the following error message:
    Certificate differs from the expected one."

    This issue can occur, if after the upgrade, the configuration settings in the two sites are not compatible.


    • If you upgrade from vCloud Availability for Cloud-to-Cloud 1.5 with a tunneling appliance, update the endpoint URL of the vCloud Availability 3.0 Tunnel appliance to 8048 and re-establish the trust between the two sites.
    • If you are upgrading from vCloud Availability for Cloud-to-Cloud 1.5 without tunneling appliance, configure the vCloud Availability 3.0 Tunnel appliance in both site that you are pairing and re-establish the trust between the two sites.
  • You cannot change the storage policy for outgoing replications using the vCloud Availability vSphere Client plug-in

    In the on-premise 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.

    Workaround: To change the storage policy of an outgoing replication, use the vCloud Availability Portal.

  • If you configure a replication to the cloud, and then reverse the replication back to the on-premise site, the reversed VM loses the network configuration

    After you perform migration, test failover, and failover tasks to reverse a replication, the resulting on-premise VM does not have a network configuration.

    Workaround: Update the network configuration for the reversed VM manually.

  • A failover task fails for a VM with multiple disks that is replicated to-the-cloud

    During a failover, the VM disks are replicated to a single datastore. When you try to failover the VM to your cloud site, the task fails with the following error message:
    Invalid or inaccessible datastore.

    This issue can occur, if the summarized source VM disks size is greater than the free storage space on the destination datastore.

    Workaround:  Before you run a failover task, ensure that the destination datastore has sufficient storage space to accommodate all source VM disks.

  • Your on-premise site is missing from the Replication Tasks drop-down menu in the vCloud Availability Portal

    You pair the on-premise site with the cloud site and configure replications between the two sites. When you go to the Replication Tasks list in the cloud vCloud Availability Portal, the on-premise site is not listed in the Replication Tasks drop-down menu.

    Workaround: To see the on-premise replications, use the date filter or the replication state filters in the Replication Tasks list.