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

VMware vSphere Replication 8.2 Release Notes

VMware vSphere Replication 8.2 | MAY 9 2019 | Build 13480246 | Download

Check for additions and updates to these release notes.

What's in the Release Notes

These release notes cover the following topics:

Localization

VMware vSphere Replication 8.2 is available in the following languages:

  • English
  • French
  • German
  • Japanese
  • Korean
  • Spanish
  • Simplified Chinese
  • Traditional Chinese

What's New

  • VMware vSphere Replication 8.2 adds compatibility with VMware vSphere 6.7 Update 2.
  • Support for VM encryption: You can replicate encrypted virtual machines if you are using VMware vSphere 6.7 Update 1 or later.
  • Minimize security risks by enabling network encryption: You can enable encryption of replication data transfer in VMware vSphere Replication 8.2, if you are using VMware vSphere 6.0 or later.
  • Enhancements to the Site Recovery user interface: With vSphere Replication 8.2, you can monitor target datastores in the replication details pane of the Site Recovery user interface, and use vSphere Replication reports that display transferred bytes per virtual machine and per hour.
  • vRealize Operations Management Pack: The new vRealize Operations Management Pack for vSphere Replication 8.2 provides increased visibility into the status of your vSphere Replication environment, RPO violations and other details. For more information, see VMware vRealize Operations Management Pack for vSphere Replication 8.2 Release Notes.
  • vRealize Orchestrator Plug-In for vSphere Replication 8.2. For information about new workflows, see VMware vRealize Orchestrator Plug-In for vSphere Replication 8.2 Release Notes.

Note: For information about the features of vSphere 6.7 Update 2, see the vSphere 6.7 Update 2 documentation.
For interoperability with the releases of VMware vSphere, see the Compatibility Matrices for vSphere Replication 8.2.x.

Product Documentation

In addition to the current release notes, you can use the documentation set for vSphere Replication 8.2 that includes the following deliverables.

Product Support Notices

vSphere Replication 8.2 is the final release that supports VMware vCloud Availability for vCloud Director. For more information, see VMware vCloud Availability product page.

vSphere Replication 8.2 is the final release that supports external databases.

Installation

Download the vSphere Replication .iso image and mount it. You can deploy the vSphere Replication appliance by using the Deploy OVF wizard in the vSphere Web Client. Navigate to the \bin directory in the .iso image and use the corresponding OVF file:

  1. vSphere_Replication_OVF10.ovf: Use this file to install all vSphere Replication components, including the vSphere Replication Management Server and a vSphere Replication Server.
  2. vSphere_Replication_AddOn_OVF10.ovf: Use this file to install an optional additional vSphere Replication Server.

For more information on installation, see section Installing vSphere Replication in the vSphere Replication Documentation Center.

For vCenter Server to vCenter Server replications, the version of the vSphere Replication Management server on the source and the target site can be either 8.1 or 8.2.

Upgrading vSphere Replication

The downloadable ISO image is the only means of upgrading from vSphere Replication 6.5.x, 8.1.1 and 8.1.2 to vSphere Replication 8.2.

You cannot upgrade vSphere Replication from version 6.5.1 to version 8.2 by using the official VMware Update Repository from the VAMI of the vSphere Replication appliance. See the compatibility matrices for further information on supported versions.

Important: Before you initiate an upgrade, verify that the vSphere Replication appliance has an OVF environment, or context. See Checking and Restoring the OVF Context of the vSphere Replication Appliance (2106709).

Verify that you read the Upgrade and General sections under Known Issues.

See Upgrade Additional vSphere Replication Servers and Upgrade the vSphere Replication Appliance for the procedures on upgrading to vSphere Replication 8.2.

Operational Limits for vSphere Replication

The operational limits of vSphere Replication 8.2 are documented in the VMware Knowledge Base. See Operational Limits for vSphere Replication 6.x and 8.x (KB 2102453).

Note: vSphere Replication requires additional configuration to support more than 500 replications per a vSphere Replication Management server. See Operational Limits for vSphere Replication 6.x and 8.х and Configuring Upgraded vSphere Replication Appliances to Support up to 2000 Replications.

Open Source Components

The copyright statements and licenses applicable to the open source software components distributed in vSphere Replication 8.2 are available at the vSphere Replication Open Source Disclosure page.

Caveats and Limitations of vSphere Replication 8.2

To ensure successful virtual machine replication, you must verify that your virtual infrastructure respects certain limits before you start the replication.

  • You cannot configure the vSphere Replication appliance when the Platform Services Controller is installed with a custom port.
  • The 5 minute RPO scales to a maximum supported limit of 50 VMs on a provisional VVOL datastore.
  • vSphere Replication does not support VSS quiescing on Virtual Volumes.
  • vSphere Replication cannot replicate virtual machines that share vmdk files.
  • vSphere Replication does not support vSphere APIs for IO Filtering on both the source and the target sites. You cannot replicate a virtual machine that is assigned a VM Storage Policy that contains IOFilters, nor can you assign such a policy to the replication target VM. Before configuring a virtual machine for replication, verify that the VM Storage Policy that is assigned to it does not contain IOFilters. Do not assign VM Storage policies with IOFilters to virtual machines that are already configured for replication.
  • Deploying more than one vSphere Replication appliance produces a warning on the boot screen. This requires user confirmation to either continue and configure all replications again or shut down the new appliance so that it does not interfere with the old one. This situation does not occur when deploying more than one vSphere Replication servers.
  • Each vSphere Replication Management Server can manage a maximum of 2000 replicated virtual machines. See Configuring Upgraded vSphere Replication Appliances to Support up to 2000 Replications (KB 2102463) and Requirements to the Environment... (KB 2107869).
  • vSphere Replication supports a maximum disk size of 62TB. If you attempt to enable replication on a virtual machine with a disk larger than 62TB, the virtual machine will not perform any replication operation and will not power on.
  • vSphere Replication tracks larger blocks on disks over 2TB. Replication performance on a disk over 2TB might be different than replication performance on a disk under 2TB for the same workload depending on how much of the disk goes over the network for a particular set of changed blocks.
  • vSphere Replication does not support upgrading the VMware Tools package in the vSphere Replication appliance.
  • vSphere Replication supports replicating RDMs in Virtual Compatibility Mode. RDMs in Physical Compatibility Mode cannot be configured for replication.
  • vSphere Replication does not replicate virtual machine snapshot hierarchy at the target site.
  • You can configure virtual machines that are powered off for replication. However, actual replication traffic begins when the virtual machine is powered on.
  • When using Storage DRS at a replication site, ensure that you have homogeneous host and datastore connectivity to prevent Storage DRS from performing resource consuming cross-host moves (changing both the host and the datastore) of replica disks.
  • For VMware vCloud Availability for vCloud Director, a seed vApp can be used for only one replication.
  • The 5 minute RPO requires the source host to be ESXi 6.0 Update 3 or later for VSAN, and ESXi 6.5 for other supported datastores.
  • To use the network isolation feature, vSphere Replication requires the host to be ESXi 6.0 or later.

Supported Browser Versions

For supported browser versions for the vSphere Web Client and vSphere Client, see the documentation of the vSphere Web Client or vSphere Client that you use.

 

Resolved Issues

The resolved issues are grouped as follows.

General
  • If you reconfigure a replication that you initially configured with default seeds to a vSAN target datastore, replica disks might be deleted and replication status changes to Error

    If you configure a replication by using the default, not manually selected, seeds to a vSAN datastore, if you later reconfigure the replication, the replica base disks might be deleted regardless of the settings that you change. Also the replication status changes to Error immediately or within one RPO cycle. The deletion of the replica base disks leads to data loss upon recovery. The issue affects only replications configured to a vSAN datastore with seeds that are automatically suggested by the Site Recovery UI and not when seeds are manually selected by browsing datastores.

    This issue is resolved in this release. 

  • An encrypted recovered virtual machine in a vCenter Server 6.7 Update 1 system does not power on

    In a vCenter Server 6.7 Update 1 system, you can configure replication of encrypted virtual machines and even run a recovery, but the recovered virtual machines might not power on if the virtual machine configuration file (.vmx) encryption key is not available at the Key Management Server (KMS) in the target site. In rare cases, the encryption keys for the .vmx file and for some disks in an encrypted virtual machine might be different, and the vSphere Replication Management server can only validate keys for new replication placeholder disks.

    This issue is resolved in vCenter Server 6.7 Update 2. For vCenter Server 6.7 Update 1 systems, make sure all the encryption keys are available at the destination site. The issue does not affect environments using the same KMS.

  • When you configure an encrypted virtual machine for replication in a vCenter Server 6.7 Update 1 system, the replication might enter an error state

    When you configure an encrypted virtual machine for replication in a vCenter Server 6.7 Update 1 system, although the workflow succeeds, the replication might enter an error state, because encryption keys for existing seed disks might not be available at the Key Management Server (KMS) in the target site. When the vSphere Replication server tries to open a seed disk to read or write, the operation fails, because the server is not able to validate the seed disk encryption key.

    This issue is resolved in vCenter Server 6.7 Update 2. For vCenter Server 6.7 Update 1 systems, make sure all the encryption keys are available at the destination site. The issue does not affect environments using the same KMS.

  • If you deploy a vSphere Replication virtual appliance by using the OVF deployment wizard in the vSphere Client, the appliance fails to start

    If you deploy a vSphere Replication virtual appliance by using the OVF deployment wizard in the vSphere Client on a vCenter Server system with a version earlier than 6.7 Update 1, the deployment succeeds, but the OVF virtual appliance fails to start. You might see an error similar to:
    The virtual machine 'vSphere_Replication' has a required vService dependency 'vCenter Extension Installation' which is not bound to a provider.
    The vSphere Client in versions earlier than vCenter Server 6.7 Update 1 does not support selecting vService extensions in the Deploy OVF Template wizard, which causes the issue.

    This issue is resolved in the vSphere Client in vCenter Server 6.7 Update 1 and later. If you already face the issue in a vCenter Server system with a version earlier than 6.7 Update 1, use the vSphere Web Client, which supports vService extensions for the deployment of OVF virtual appliances.

Known Issues

The known issues are grouped as follows.

Upgrade
  • The upgrade of the vSphere Replication Management Server to version 8.2 in an IPv6 environment fails when upgrading VCTA

    The user interface of the console upgrade displays the following error:
    Failure during upgrade procedure at Upgrade Services phase: No such file

    Workaround: Select the Ignore option to continue with the upgrade.

  • After upgrading vSphere Replication Management Server to version 8.2 with an automatically generated certificate, a certificate problem occurs when you log in the Site Recovery UI

    The Site Recovery UI log file contains the following information: Caused by: javax.net.ssl.SSLException: Certificate for <HMS.FQDN> doesn't match common name of the certificate subject: <HMS.IP>. vSphere Replication Management Server is registered with the lookup service by using FQDN, but the SSL certificate uses the IP address, which causes a mismatch.

    Workaround:

    1. After the vSphere Replication Management Server upgrade, log in to the VAMI of the vSphere Replication Management Server and generate and install a new SSL certificate.
    2. Reconfigure the connection between the vSphere Replication servers.
  • After a fresh installation or upgrade to vSphere Replication 8.2, a vSphere Replication appliance configured with trust by certificate policy fails to connect to vCloud Availability

    After a fresh installation or upgrade to vSphere Replication 8.2, if you use trust by certificate instead of the default trust by thumbprint certificate policy, the vSphere Replication appliance might fail to connect to vCloud Availability. The connection fails, because the vSphere Replication Management Server does not find any certification authority (CA) in /opt/vmware/hms/security/hms-truststore.jks.

    Workaround: You must manually import additional trusted CA certificates in /opt/vmware/hms/security/hms-truststore.jks on the vSphere Replication appliance. 

General
  • Replications change state to Not Active if you try to configure a replication to use both the network encryption and network traffic isolation features

    If you try to configure a replication to use both the network encryption and network traffic isolation features, the replication changes state to Not Active. For example, if you try to use network traffic isolation on the replication of encrypted virtual machines, where network encryption is not optional.

    Workaround: Until a future vSphere Replication release to enable the full use of both features, you can only partially combine network encryption and traffic isolation. For example, if you go to the settings of the VMkernel network adapters on the source host and switch off the vSphere Replication tags, the replication state changes to OK, and only traffic isolation of the outgoing traffic from the source site is disabled.

  • If the source VM for a replication runs on ESXi 6.7 or 6.7 Update 1, an initial or full synchronization might stop progress before completion

    The synchronization of replications for which the source VM is running on ESXi 6.7 or 6.7 Update 1 remains in progress, but the checksum bytes value in the replication details information does not progress. Operations such as powering off, taking a snapshot, reverting to a snapshot, and migrations fail with a timeout or Task in progress errors.

    Workaround: 

    1. In the ESXi Advanced settings, disable the checksum for vSphere Replication by setting HBR.ChecksumUseChecksumInfo = 0.

    2. Migrate all VMs and power off the ones that cannot be migrated on the ESXi host.

    3. Place the host in maintenance mode.

    4. Reboot the ESXi host.

    With these steps, you disable the checksum part of the sync process and all of the allocated blocks are sent to the remote site, regardless of whether they are different or not. Also, you cannot use seeds.

  • Generation of self-signed certificates of the vSphere Replication Appliance fails if a domain name starts with a number

    Generation of self-signed certificates of the vSphere Replication Appliance might fail if a domain name starts with a number, such as 888xxx.

    Workaround: To generate a Certificate Authority certificate for fresh deployments, follow the steps in VMware knowledge base article 2080395.

  • You cannot recover or reconfigure virtual machines with names containing special characters

    You cannot recover or reconfigure virtual machines with names containing the special characters { or }. Although the use of special characters is allowed for file system names that are derived from the virtual machine name, the vSphere Replication Management Server fails to create disk files at the destination folder. If the recovery fails, you cannot rename the virtual machine.

    Workaround: None

  • If the source VM for a replication runs on ESXi 6.7, replication synchronization seems to progress, but the replication instance never completes successfully

    In ESXi 6.7, it is possible that more demand log chunks be scheduled for parallel transfer than the actual number that can be transmitted. If you are replicating a VM that is running on such a host and this coincides with a slow target host or temporary network errors, this might result in replication failure with DiskQueue is full errors.

    Workaround:

    1. Move all the VMs to another ESXi host.
    2. Edit the value of the HBR.DemandlogTransferMaxNetwork ESXi Advanced setting to 63 instead of the default 64.
    3. Place the ESXi host in maintenance mode.
    4. Reboot the ESXi host.
Replications to vCenter Server
  • You cannot encrypt an unencrypted source VM in an active replication

    If you try to encrypt an unencrypted virtual machine in an active replication configuration, the encryption fails and you lose the already replicated data on the remote site.

    Workaround: Recover the unencrypted virtual machine and configure a new replication with encrypted seed disks.

    1.    Recover the VM on the remote site, but do not power the VM on.
    2.    Edit the settings of the VM on the target site and change the VM storage policy to VM Encryption Policy.
    3.    Edit the settings of the source VM on the source site and change the VM storage policy to VM Encryption Policy.
    4.    Remove the replication of the source VM.
    5.    Configure a new replication and select the disks of the recovered VM on the target site as seeds.

  • If you reconfigure a replication to assign a new vSAN storage policy to some virtual machine disks, the policy is not applied to the replicas at the target site

    vSAN storage policy is applied to replicas at the recovery site at the time you first configure or recover a replication. If you reconfigure the replication with a new storage policy, the change is not automatically reflected to the pair site.

    Workaround:

    1. Recover the virtual machines with reconfigured replication.
    2. By using the vSphere Client, change the storage policy of the recovered virtual machines to the new policy.
    3. Unregister the recovered virtual machines from the vCenter Server inventory.
    4. Configure replication again by using seeds and with the new storage policy.
  • You cannot see the progress of the initial sync operation when configuring replications within the same vCenter Server

    If you configure replications within the same vCenter Server, when you expand the settings of the replication, you see Sync operation in progress: LOGIN REQUIRED instead of the actual progress of the initial sync operation. For replications within the same vCenter Server, login is not required, and this is unexpected behavior.

    Workaround: None

Known Issues from Previous Releases

To view a list of previous known issues, click here.