VMware Cloud Director Availability | 23 FEB 2023 | Build 21291908 (Product version:

Check for additions and updates to these release notes.

What's new

VMware Cloud Director Availability includes important resolved issues.


VMware Cloud Director Availability supports an in-place upgrade directly from versions 4.3.x, 4.4.x, and 4.5.0.

For information about the upgrade process, see Upgrading in the Cloud Director Site and Upgrading On-premises and Provider Site.

Note:When upgrading from 4.3.x or 4.4.x:

  • vSphere DR and migration between vCenter Server sites requires when upgrading that both sites upgrade to version or 4.5.0. After upgrading one of the sites, the existing replications continue to replicate and the workloads can be recovered in case of disaster. The other site must be upgraded before creating new replications or new pairing or before performing any management tasks. After upgrading both sites to version or 4.5.0, as a tenant you must Re-pair with the provider site. For information about re-pairing from the tenant site, see step 3 in Repair a Site.

  • Also for vSphere DR and migration, if using a single-sign-on administrator user with custom privileges in vSphere, you must add the StorageViews.View privilege. For information about all the required vSphere privileges, see Users Roles Rights and Sessions in the Security Guide.

  • For replications using the VMC data engine, after an upgrade to or 4.5.0 you must regenerate each Replicator Service certificate. For information about replacing these certificates, see Replace the Replicator Service Certificate.

Configuration maximums

For the tested uptime, concurrency, and scale limits, see VMware configuration maximums.

Caveats and limitations

  • For replications using the Classic data engine, VMware Cloud Director Availability uses vSphere Replication module called Host-based Replication (HBR) version 8.6. For information about its inherited caveats and limitations, see vSphere Replication 8.6 Release Notes.

  • The VMware Cloud Director Availability vSphere Client Plug-In requires vSphere Client support. When using an earlier vSphere version:

    • To configure replications, use the VMware Cloud Director Availability Tenant Portal.

    • Alternatively, in VMware Cloud Director use the VMware Cloud Director Availability plug-in.

  • In on-premises sites backed by VMware Cloud Director, to access the VMware Cloud Director Availability vSphere Client Plug-In in previous versions, the tenants had to authenticate with a user member of the Administrators group. Since version 4.5.0, once configured with the vCenter Server Lookup Service, the On-Premises to Cloud Director Replication Appliance creates the VrOnpremUsers group. Membership of this group allows access to the VMware Cloud Director Availability vSphere Client Plug-In.

Resolved issues

The following issues have been resolved in this release.

  • Cannot change from password to key-based SFTP authentication

    For a scheduled backup, attempting to change the SFTP server authentication method from password-based to key-based has no effect and VCDA continues to use the previously saved password-based authentication.

  • For encrypted replications VMware Cloud Director does not report the storage space that is taken

    In VMware Cloud Director, you cannot see the storage space consumed by encrypted replications.

  • Cannot configure the Cloud Director Replication Management Appliance with VMware Cloud Director if the Tunnel Appliance cannot connect to it

    When the Tunnel Appliance has no connectivity to the local VMware Cloud Director in the cloud site, you cannot configure the Cloud Director Replication Management Appliance with the same VMware Cloud Director.

  • Randomly ordered cloud sites in drop-down menus

    In the New replication wizard, on the Replications page, and in the Tasks pane, the drop-down menus that list the paired cloud sites are not sorted and show the cloud sites in random order on every page visit.

    Note: The on-premises sites are always sorted by name.

Known Issue

The following known issue is currently identified in this release.

  • Applying the Recovery Settings for replicated virtual machines with no consecutive indexes fails when selecting networks

    For a virtual machine with two network adapters, by deleting the first one, the second network adapter keeps its index, for example, NIC 2.

    After configuring such virtual machine for replication, clicking its All actions > Recovery Settings and selecting a network for the first network adapter, displayed as NIC 1 does not apply the selected network.

    Workaround: Upgrade to VMware Cloud Director Availability 4.6.1.

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