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

VMware vSphere Replication 8.1.2 Release Notes

VMware vSphere Replication 8.1.2.1 | MAY 09 2019 | Build 13510692 | Download

VMware vSphere Replication 8.1.2 | APR 11 2019 | Build 13095593 | Download

Check for additions and updates to these release notes.

For information about the vSphere Replication 8.1.2.x patch releases, see the corresponding section.

What's in the Release Notes

These release notes cover the following topics:

Localization

VMware vSphere Replication 8.1.2 is available in the following languages:

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

Earlier releases of vSphere Replication 8.1

Features, known issues, and resolved issues of vSphere Replication are described in the release notes for each release. Release notes for earlier releases of vSphere Replication 8.1 are:

What's New

  • VMware vSphere Replication 8.1.2 is compatible with VMware vSphere 6.7 Update 2.

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.1.2.

Product Documentation

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

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.

NOTE: For vCenter Server to vCenter Server replications, the version of the vSphere Replication Management server on the source and the target site must match.

Upgrading vSphere Replication

The downloadable ISO image is the only means of upgrading from vSphere Replication 6.1.2 or 6.5.1 to vSphere Replication 8.1.2. You cannot upgrade vSphere Replication from version 6.1.2 or 6.5.1 to version 8.1.2 by using vSphere Update Manager or 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.1.2.

Operational Limits for vSphere Replication

The operational limits of vSphere Replication 8.1.x 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.1.2 are available at the vSphere Replication Open Source Disclosure page.

Caveats and Limitations of vSphere Replication 8.1.2

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

  • vSphere Replication 8.1 requires and fully supports vCenter Server 6.0 Update 3, vCenter Server 6.5, vCenter Server 6.5 Update 1, or vCenter Server 6.7.
  • You cannot configure the vSphere Replication appliance when the Platform Services Controller is installed with a custom port.
  • vSphere Replication does not support configuring a replication for an encrypted virtual machine.
  • 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 in this release.
  • 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).
  • If you move a virtual machine with replicated disks larger than 2032GB to an ESXi 5.1 or earlier host, vSphere Replication cannot replicate or power on the virtual machine.
  • 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 no longer supports IBM DB2 as the vSphere Replication database, in accordance with the removal of support for DB2 as a supported database for vCenter Server 5.5. If you use DB2 as an external vSphere Replication database, contact VMware support for instructions about how to migrate your data to a supported database.
  • 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 replications to cloud, a seed vApp can be used for only one replication.
  • The 5 minute RPO requires the source host to be ESXi 6.0 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.

Available Patch Releases

vSphere Replication 8.1.2.1 Express Patch Release

Released 09 MAY 2019 | Build 13510692

The vSphere Replication 8.1.2.1 Express Patch Release | 09 MAY 2019 | Build 13510692 adds a bug fix to the Resolved Issues section.

Installation and Upgrade Notes

See Upgrading vSphere Replication in vSphere Replication 8.1 Administration for instructions about upgrading vSphere Replication.

Resolved Issues

The resolved issues are grouped as follows.

General
  • NEW 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 vSphere Replication 8.1.2.1.

  • The vSphere Replication Management server database runs out of disk space and the server fails to start

    The disk partition in the vSphere Replication appliance for the vSphere Replication Management server database might run out of space without a warning. As a result, the server might fail to start.

    This issue is resolved in this release.

  • The vSphere Client creates a new, uniquely named folder to place the VMX files and disks without seeds when you try to configure a replication by using seeds

    When you try to configure a replication by using replication seeds, the vSphere Client creates a new, uniquely named folder in the target datastore to place the VMX files and disks without seeds.

    This issue is resolved in this release.

  • You do not see the replication configuration in the Site Recovery user interface after deleting the source virtual machine

    If you configure a replication within a single vCenter Server by using the Site Recovery user interface and delete the source virtual machine, the replication configuration is no longer displayed.

    This issue is resolved in this release.

  • If you configure vSphere Replication over a Mutual Transport Layer Security (MTLS) network, the operation might fail due to a timeout

    If you configure vSphere Replication over a MTLS network, a firewall rule might silently close the connection between the hbrsrv service and ESXi hosts, and the operation fails due to a timeout.

    This issue is resolved in this release. Add the line <pcMaxWaitSeconds>60</pcMaxWaitSeconds> to /etc/vmware/hbrsrv.xml and restart the hbrsrv service. This sets a maximum waiting time of the hbrsrv service for TCP response.

Upgrade
  • The IP Address for Incoming Storage Traffic property might not persist after an upgrade to vSphere Replication 8.1.1 from 6.5.x

    After an upgrade to vSphere Replication 8.1.1 from 6.5.x, the IP Address for Incoming Storage Traffic property might not persist. You might see the Management Network IP Address property instead.

    This issue is resolved in this release.

Cloud Replications
  • The vCloud Tunneling Agent might not start during the boot phase

    The vCloud Tunneling Agent might fail to start during the boot phase with an error message similar to Failed to start vmware-vcd.service: Unit vmware-vcd.service not found.

    This issue is resolved in this release.

  • You see multiple warnings for configuration issues on protection groups in VMware Site Recovery

    The restart of the vSphere Replication Management Server on one of the sites in an on-premises-to-cloud pair might trigger multiple warnings in VMware Site Recovery for configuration issues on protection groups that use this site as protected site.

    This issue is resolved in this release.

Known Issues

The known issues are grouped as follows.

Replications to vCenter Server
  • NEW 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

General
  • NEW If you reconfigure an upgraded replication that you initially configured with default seeds to a vSAN target datastore on vSphere Replication 8.1.1, 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 on vSphere Replication 8.1.1, 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.

    Workaround: Stop the replication and configure it again by using automatically detected or manually selected seeds.

  • You might see an error in the vSphere Replication inventory of the vRealize Orchestrator after replacing a vSphere Replication management server certificate at the local site of a pair

    If you change the certificate of the vSphere Replication management server at the local site of a replication pair, you might not be able to see the pair in the vSphere Replication inventory of the vRealize Orchestrator. You see an error similar to:
    Unable to execute 'fetchRelation' for type : Site : com.vmware.vim.vmomi.client.exception.SslException: com.vmware.vim.vmomi.core.exception.CertificateValidationException: Server certificate chain is not trusted and thumbprint doesn't match

    Stale certificates in the vRealize Orchestrator inventory cause the issue.

    Workaround:

    1. Restart the vRealize Orchestrator server:
      1. Launch a console to the virtual machine on which the vRealize Orchestrator server is installed.
      2. Log in to the console as root.
      3. Run the command service vco-server restart to restart the vRealize Orchestrator server.
    2. Restart the Orchestrator client. Wait for the validation to complete. You can monitor validation progress at this url pattern: https://{your vRealize Orchestrator server address}:8283/vco-controlcenter/config/#/control-app/validate
    3. In case the vSphere Replication management server is in a pair with another vSphere Replication management server, you must reconnect the pair.
    4. In the vRealize Orchestrator inventory, unregister the old server entries and register the new ones.
  • 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.

Known Issues from Previous Releases

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