VMware Cloud Director Availability™ 4.0 | 2 JUN 2020 | Build 16295568
Check for additions and updates to these release notes.
What's in the Release NotesThe release notes cover the following topics:
- What's New
- Configuration Maximums
- Caveats and Limitations
- Supported Browsers
- Resolved Issues
- Known Issues
VMware Cloud Director Availability 4.0 introduces the following new features:
- Storage reporting: VMware Cloud Director Availability now shows the disk space used by each virtual machine replication and aggregates the disk usage information per organization. You can monitor the disk usage for every replication in all directions. You can also monitor the disk usage for every organization.
- Event notifications: You can now monitor the event notifications that VMware Cloud Director Availability generates either by using a syslog server or in VMware Cloud Director by monitoring the VMware Cloud Director Availability events.
- Bandwidth throttling: You can now configure a limit for the replication data traffic from the on-premises to cloud sites. You can also set a global limit in VMware Cloud Director Availability for the total incoming replication traffic from all cloud sites.
- Public API enhancements for tenant onboarding, storage, network, and usage reporting: VMware Cloud Director Availability now provides public APIs that help to onboard tenants, see the storage usage, the network settings, and the compute resource usage of the replications.
- Multi-NIC support: After completing a VMware Cloud Director Availability appliance deployment, you can now modify the network settings of the appliance by using the appliance management interface that now supports multiple Network Interface Cards (NICs).
- SLA profiles: You can now define and control the following Service Level Agreement (SLA) replications settings: Recovery Point Objective (RPO), retention policy for the point-in-time instances, quiescing, compression, and initial synchronization time by using SLA profiles that can be assigned to organizations.
- Improved user interface for a better usability and efficiency: VMware Cloud Director Availability now provides easier replication management and overview of the tasks by simplifying the management interface.
- Resource requirements: VMware Cloud Director Availability now shows the compute resource requirements of the replications that are required on a failover. This information provides the required destination capacity, the virtual CPU, and memory resources to fail over the protected workloads successfully to the destination site.
- Live disk resizing in vSphere 7.0: In the source site with vCenter Server 7.0 and ESXi 7.0, when resizing the disk of the source virtual machine, VMware Cloud Director Availability now automatically resizes the protected virtual machine disk in the destination site, running any supported vSphere version. The existing replication instances are retained. Failover and Test Failover are supported from any instance, before and after the disk resizing. Until the replication instances before the resizing expire, the replica files continue to take the additional storage space. To save the storage space, you can remove the old replication instances or change the retention policy.
- Stored instances: To restore a workload to a previous state, you can use point-in-time or stored instances. To avoid the automatic retention of point-in-time instances, now you can store particular point-in-time instances. The stored instances do not change and you can use them to recover the workload to the stored instance, regardless of the overall retention period of the point-in-time instances.
- VMware Cloud Director context-menu integration: Protected vApps and virtual machines now have a protection indicator badge in the interface of VMware Cloud Director. The protection badge is visible to providers in VMware Cloud Director with VMware Cloud Director Availability 4.0 in the source and in the destination cloud site. Also, you can now use a VMware Cloud Director Availability context menu for the vApps and virtual machines directly from the VMware Cloud Director interface. The context menu allows you to start a new replication quickly. Tenants with policy that does not allow replications now see a VMware Cloud Director Availability plug-in with steps to enable the service. The steps are similar to the steps in the VMware Cloud Director Availability vSphere plug-in, without showing the service providers list.
- Interoperability with NSX-T: In on-premises sites and in cloud sites, you can now replicate workloads that use NSX-T 2.5.0 and NSX-T 2.5.1 networks. You can also use environments with mixed NSX-V and NSX-T networks, and you can replicate workloads from NSX-V to NSX-T and from NSX-T to NSX-V. VMware Cloud Director Availability does not apply or translate the networking features that the latest VMware Cloud Director 10.1.1 and NSX-T 2.5.1 do not support. VMware Cloud Director Availability replicates the source site NSX-V to NSX-T NAT-routed vApp networks as bridged vApp networks, and does not replicate the DHCP service.
- VMware vCloud Usage Meter integration: There is an indication in the management interface that vCloud Usage Meter meters the Cloud Service instance. When vCloud Usage Meter has not requested metering information for more than three days, you now see a warning message in the management interface. To collect product consumption data and generate reports for the VMware Cloud Provider Program, see How do I add VMware Cloud Director Availability for metering in the vCloud Usage Meter documentation.
Since June 2020, vCloud Availability changed its product name to VMware Cloud Director Availability. In the following table you can see the new appliances names and the new services names:
|VMware vCloud Availability||VMware Cloud Director Availability|
|Previous Appliance Name||Previous Service Name||New Appliance Name||New Service Name|
|vCloud Availability Replication Management Appliance||vCloud Availability vApp Replication Manager||Cloud Replication Management Appliance||Cloud Service|
|vCloud Availability Replication Manager||Manager Service|
|vCloud Availability Cloud Replicator Appliance||vCloud Availability Replicator||Cloud Replicator Appliance||Replicator Service|
|vCloud Availability Cloud Tunnel Appliance||vCloud Availability Tunnel||Cloud Tunnel Appliance||Tunnel Service|
|vCloud Availability On-Premises Appliance||VMware Cloud Director Availability On-Premises Appliance|
For the tested uptime, concurrency, and scale limits, see VMware Configuration Maximums.
Caveats and Limitations
For interoperability between paired sites with different VMware Cloud Director Availability versions, see Managing Connections Between Cloud Sites.
For interoperability between VMware Cloud Director Availability and other VMware products, see VMware Product Interoperability Matrices.
Note: The VMware Cloud Director Availability vSphere Client Plug-In requires vSphere Client support. You can use the VMware Cloud Director Availability Portal if your vSphere environment does not support vSphere Client.
VMware Cloud Director Availability 4.0 supports the following browsers:
- Google Chrome 78 and later
- Mozilla Firefox 69 and later
- Microsoft Edge 44 and later
- Safari 13 and later
- Cannot protect or migrate virtual machines or vApps that are incompatible with the destination hardware version
When migrating or failing over a virtual machine with a hardware version that is incompatible with the ESXi host at the destination site, the vCloud Availability task completes successfully but you cannot power-on the virtual machine at the destination site. For example, at the destination site, after a failover from an on-premises site with vCenter Server 6.7 to a cloud site with vCenter Server 6.0, you cannot start a virtual machine with hardware version 13. For more information on the virtual machine compatibility, see Virtual Machine Compatibility in vSphere Virtual Machine Administration.
- Replication seed with excluded disks cannot be used for a new replication
If you attempt to use an existing seed that has some disks excluded to start a new vApp or virtual machine replication fails with an error message, such as
Disks of provided seed VM don't match the disks of the source VM.
- For on-premises to cloud replications, configuring the network settings of a virtual machine also causes a change of its computer name
In an on-premises to cloud replication, you can configure the destination network settings of the virtual machine. At the destination cloud site, in addition to applying the network settings, the computer name in the operating system of the virtual machine gets incorrectly changed to xxxxxxx-01, where xxxxxxx is the original computer name. As a result of this computer name change, Windows virtual machines can disjoin from the domain controller.
- Cannot exclude disks from a replication started with a replication seed
If you attempt to exclude any of the disks from an existing vApp or virtual machine replication that is configured with a replication seed, the replication sync times out.
- Cannot upgrade to VMware Cloud Director Availability 4.0.0 with less than 60% free disk space on the appliance
When upgrading from 3.x to 4.0.0, the upgrade process requires 60% free disk space on the appliance and the upgrade script does not validate whether this disk space or more is available.
Upgrade to VMware Cloud Director Availability 18.104.22.168. For more information, see the VMware Cloud Director Availability 22.214.171.124 Release Notes document.
- Clicking the VMware Cloud Director Availability menu in VMware Cloud Director with expired session causes an error
In VMware Cloud Director, if your session has expired and you click the VMware Cloud Director Availability menu, you see the following error message
The service at https://ip-address:8048 is not accessible.
Workaround: Refresh the VMware Cloud Director web page and click the VMware Cloud Director Availability menu again.
- With multiple Cloud Service instances registered in VMware Cloud Director, the context-menu shows only the latest configured Cloud Service
If you register more than one Cloud Service in VMware Cloud Director, when you right-click in VMware Cloud Director to start a new replication by using VMware Cloud Director Availability, you see only the lastly configured Cloud Service instance listed in the context-menu.
Workaround: To start a new replication, you can access all registered VMware Cloud Director Availability instances by using the main menu in VMware Cloud Director.
- With a selected SLA profile, reversing a cloud to cloud replication, or reprotecting a reversed replication, results in a replication with custom SLA settings and the replication fails if the custom SLA settings are not allowed
When you perform a reverse task on a replication that is configured with an SLA profile, the resulting replication in the source organization contains custom SLA settings, instead of the selected SLA profile. If Allow custom SLA settings is deselected for the source organization, the reversed replication fails with the error message
Replication with custom SLA settings can not be configured because it violates policy "sample policy" configured at site "sample site".
Similarly, for reprotect configured with an SLA profile, the replication in the destination organization contains custom SLA settings. If Allow custom SLA settings is deselected for the destination organization, the reversed replication fails with the same error message.
Workaround: To use the existing replications without incurring this error, select Allow custom SLA settings for reverse - in the source organization or for reprotect - in the destination organization. By allowing custom SLA settings, the SLA settings are the same as the SLA settings in the selected SLA profile.
Alternatively, to use SLA profiles at both the source and destination, delete the replication to reverse and create new replication in the reverse direction: after failover, delete the original source to destination replication and create a new replication in the destination to the source by selecting the SLA profile for the source site.
Similarly, to reprotect a replication and use SLA profiles, after failover delete the destination to source replication and create new replication from source to destination by selecting the SLA profile for the destination site.
- Failover and test failover fail when in the network settings Connected is deselected, for IP Mode None is selected, and Cloud Director 10.1.1 is running in the destination cloud site
When Cloud Director 10.1.1 is running in the destination cloud site, and in the network settings for a NIC of a virtual machine in a vApp you deselect Connected and select None for IP Mode, attempting a failover or a test failover fails with the
Invalid network parameter: Unknown IP Addressing Modeerror message.
Workaround: For cloud to cloud replications, all NICs shown in the network settings always associate with a network, either connected or not connected to that network. When running Cloud Director 10.1.1, for the NICs either do not select None for IP Mode, or temporarily select Connected when in combination with IP Mode None selected.