VMware Cloud Director Availability 4.5 | 24 NOV 2022 | Build 20795276 (Product version: 4.5.0.5226630-ab9eb01ccb)

Check for additions and updates to these release notes.

What's new

VMware Cloud Director Availability 4.5 now supports the following new functionality, depending on the deployment type:

Enhancements in DR and migration to vSphere

  • Enhancements in DR and migration to vSphere: now the on-premises appliance no longer requires public URL and supports a single-step pairing to the provider site. The pairing from on-premises to a provider no longer requires additional steps for confirming the pairing from the provider site. However, the pairing between two provider sites remains a two-step process, initiated from one provider site, then completed from the other provider site.

  • Add Replicator appliances in the provider site: in the provider-hosted vCenter Server instance, after configuring the vCenter Replication Management Appliance, you can now add one or more Replicator Appliance instances. That scales the performance when replicating tenant vSphere workloads between an on-premises vCenter Server instance and a provider-hosted vCenter Server instance or between provider-hosted vCenter Server instances. Adding Replicator Appliance instances is also supported for existing environments.

  • Recovery settings for vSphere DR and migration: now you can preconfigure the destination virtual machines location and compute resource and the network mapping that apply when recovering the workload in the destination site.

  • View-only vSphere user: VMware Cloud Director Availability now supports read-only users and allows users to only monitor replications or administrators to only monitor the system health and the replications.

  • Replicate encrypted virtual machines: VMware Cloud Director Availability now supports replicating virtual machines with an encryption-enabled storage policy, providing end-to-end encryption also in the case for vSphere DR and migration. For more information, see the Prerequisites.

Enhancements in Cloud Director sites

  • Extended control and management of replication policies: cloud to on-premises migrations can now be disallowed separately from cloud to cloud migrations. Once the cloud site is upgraded to version 4.5, disallowing migrations to on-premises stops all outgoing migrations to all on-premises appliances in the organization, regardless of their VMware Cloud Director Availability versions.

  • System-wide notifications to peer sites: these advisories notifications can now appear on the top of the VMware Cloud Director Availability pages after creating them in VMware Cloud Director. You can select a priority and duration for showing the message and its audience: to the administrator users, to users within a specific organization, or to the users in all organizations.

  • VM sizing policy selection: when creating or modifying a replication you can now also select a VM sizing policy in addition to the VM placement policy. Within an organization, the VDC compute policies control the compute resources allocation for the recovered workload to several predefined sizes.

  • View-only system user: VMware Cloud Director Availability now supports read-only users and allows users that are not an Organization administrator to manage replications.

  • Advanced recovery settings: you can modify the destination network settings, the guest customization, and the guest customization script that are applied when recovering the workload in the destination site.

  • Clone a replication policy: now you can duplicate each selected replication policy by clicking the Clone button.

Enhancements in all sites

  • Backup and restore automation: you can now schedule the creation and the upload of the VMware Cloud Director Availability appliance backup files to an external server using Secure File Transfer Protocol (SFTP).

  • Service and appliance uptime: you can now check the uptime of both the services and the appliance on the System Health page.

  • Recent Tasks: now, by expanding this global taskbar on the bottom of the page in the appliances interface, you can see both system and replication tasks that recently executed. To filter these tasks by exit criteria, click Running, Failed, or Succeeded.

Updated appliances names and hardware requirements

VMware Cloud Director Availability 4.5 and later require additional CPU cores and RAM for the appliances listed in the following table. After the upgrade, to take advantage of the updated performance settings, increase the CPU count and memory. The storage requirements remain at 10 GB for all appliances of VMware Cloud Director Availability. For information about all hardware requirements, see Deployment Requirements in the Cloud and Deployment Requirements On-Premises.

Appliance

Previous hardware requirements

Hardware requirements in version 4.5 and later.

Replicator Appliance

4 vCPUs and 6 GB RAM

8 vCPUs and 8 GB RAM

Tunnel Appliance

2 vCPUs and 4 GB RAM

4 vCPUs and 4 GB RAM

On-Premises to Cloud Director Replication Appliance

4 vCPUs and 4 GB RAM

8 vCPUs and 8 GB RAM

Since VMware Cloud Director Availability 4.5, the following appliances change their names:

Updated cloud appliances names for

Previous name of the appliance

Updated name of the appliance

vSphere DR and Migration

vCenter Replication Management Appliance***

N/A in version 4.4.

Replicator Appliance*

Cloud sites backed by VMware Cloud Director

Cloud Replicator Appliance

Cloud Tunnel Appliance

Tunnel Appliance**

Cloud Replication Management Appliance

Cloud Director Replication Management Appliance

* The Replicator Appliance instances in any cloud site operate in the same manner, regardless whether the cloud site is backed by VMware Cloud Director or not.

** The Tunnel Appliance operates only in cloud sites backed by VMware Cloud Director.

*** The existing names of the remaining appliances: the vCenter Replication Management Appliance and the two on-premises appliances stay the same.

Upgrade

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

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

Note:

  • vSphere DR and migration between vCenter Server sites requires when upgrading that both sites upgrade to version 4.5. 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 4.5, 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 4.5 you must regenerate each Replicator Service certificate. For information about replacing these certificates, see Replace the Replicator Service Certificate.

Legacy migrations

VMware Cloud Director Availability 4.5 continues supporting migrations from legacy vCenter Server versions 5.5 and 6.0. For information about the legacy migrations, see KB 89181.

Configuration maximums

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

Caveats and limitations

  • 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 sites backed by VMware Cloud Director, users only members of the VRADMINISTRATORS or of the VRUSERS groups in vSphere cannot use the VMware Cloud Director Availability vSphere Client Plug-In.

    • To use the plug-in, the users must be members of the Administrators group in vSphere.

For interoperability between paired sites backed by VMware Cloud Director with mismatching VMware Cloud Director Availability versions, see Managing Pairing with Cloud Director Sites.

For interoperability between VMware Cloud Director Availability and other VMware products, see the VMware product interoperability matrix.

Supported browsers

VMware Cloud Director Availability 4.5 supports the following browsers:

  • Google Chrome 107 and later

  • Microsoft Edge 107 and later

  • Mozilla Firefox 104 and later

  • Safari 15 and later

Resolved issues

The following issues have been resolved in this release.

  • Creating outgoing vSphere DR and migration allows selecting already replicated virtual machines

    This issue only applies to outgoing vSphere DR and migration between vCenter sites.

    After creating an outgoing replication, for example, from site A to site B, selecting the already replicated virtual machine is allowed, instead of being dimmed when creating another outgoing replication from site A. 

    As a result, attempting to replicate the same virtual machine in a second replication from site A:

    • to site B, produces the following error message: The virtual machine has an active replication activated. The original replication to site B continues uninterrupted and the second replication does not get created to site B.

    • to site C, starts replicating to site C without any errors. Because one workload can replicate to a single destination, you must manually delete the inactivated outgoing replication from site A to site B. However, this inactive replication has no effect on the new replication from site A to site C.

  • Changing the root password with a dictionary word errors out but changes the password

    Changing the root user password with one that contains a dictionary word successfully changes it but shows an error message: Could not change password. Try again with a strong password that hasn't been used before. A second attempt at changing the password by not entering a dictionary word results in an error message: The provided current password is not valid, since the password is already changed.

  • Filtering VM replications by Overall Health or Replication State shows an error and no replications

    Attempting to filter the listed VM replications by either of the two columns Overall Health or Replication State does not list any replications and shows an error: The operation is not supported. 

Known issues

The following known issues are currently identified 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.

    Delete the scheduled backup then create a new one by using key-based authentication.

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