VMware Cloud Director Availability 4.7.1 | 15 FEB 2024 | Build 23265673 (Product version: 4.7.1.8968498-0422b55a9e)

Check for additions and updates to these release notes.

What's new

VMware Cloud Director Availability 4.7.1 includes important resolved issues and updates of third-party libraries that provide security fixes.

Upgrade

VMware Cloud Director Availability 4.7.1 supports an in-place upgrade directly from versions 4.5.x, 4.6.x and 4.7. To upgrade to version 4.7.1 from an earlier version, first upgrade to either version 4.5.x, or to version 4.6.x.

For information about the upgrade process, see Upgrading in the Cloud Director site and Upgrading on-premises and provider site.

APIs

Configuration maximums

For information about the tested and verified uptime, concurrency, and scale limits, see VMware Configuration Maximums.

Caveats and limitations

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

  • With deactivated telemetry in VMware Cloud Director 10.5 and later, when opening VMware Cloud Director Availability from the plug-in in VMware Cloud Director, providing Feedback is not possible.

Resolved issues

The following issues have been resolved in this release.

  • A recovered VM might have a different amount of NICs than the source VM

    After a failover or a test failover, the operation of adding or removing network adapters from a protected VM that is backed up by a replication tracking VM, might not be reflected on the resulting VM. Only the network adapters present at the start of the replication operation might be available to the recovered VM. The issue might occur only when using VCDA 4.7.0 with VCD 10.5.1 and later, and does not affect replications that are backed up by independent disks. This issue is fixed in this release.

  • For replications to Cloud Director sites, when using a flexible storage profile in a recovery plan, the health validation does not check the availability of the disk storage profiles

    If a disk in a replication is assigned with a storage profile that is no longer available, while the VM configuration is assigned with an available storage profile, once this replication is added in a recovery plan, the health validation reports no issues. This issue affects only replications to a Cloud Director site as destination. This issue is fixed in this release.

  • For vSphere DR and migration, using per-disk Placement Datastore on test failover produces a VM which seemingly has all its disks on the VM Placement Datastore

    When you perform test failover, the disks of the test failover VM appear on the VM Placement Datastore despite another storage policy assigned to its disks. Technically, the disks reside both on the Placement Datastore, where you select the disks to replicate, and on the VM Placement Datastore, where you select the VM configuration files to replicate. 

    Most of the replica data is still on the disks storage where you selected. Only a child disk resides on the configuration files datastore, which you can safely ignore. This issue only affects vSphere DR and migration between vCenter Server sites.

    This issue is fixed in this release.

  • The context menu in VMware Cloud Director does not allow to edit the replication settings page

    For existing replications, in VMware Cloud Director, selecting Actions > Availability (site) > Replication settings opens the Replication settings window, where all settings are inactive and cannot be modified. This issue is fixed in this release.

  • Replications using the Classic data engine fail to synchronize or show a red state

    Due to specific networking requirements, replications that use the Classic data engine are affected:

    • Attempting to configure a new replication results in a task that is stuck. After about 10 minutes, the task might finish successfully, but the replication remains in red state.

    • Attempting to synchronize an existing replication fails with sync timeout.

    This issue is fixed in this release.

Known issues

There are no known issues identified in this release.

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