VMware vSphere Replication 8.2.1 | OCT 29 2020 | Build 17079075 | 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.1 is available in the following languages:

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

What's New

VMware vSphere Replication 8.2.1 provides bug fixes аnd security fixes

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.

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

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

You cannot upgrade vSphere Replication from version 6.5.1 to version 8.2.x 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.x.

Operational Limits for vSphere Replication

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

Caveats and Limitations of vSphere Replication 8.2.1

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

  • vSphere Replication 8.2.1 does not support the virtual NVMe (vNVMe) capability in VMware vSphere.
  • 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

  • NEW vSphere Replication server enters in Not Connected state

    If you have recently replaced your SSL certificate, the embedded vSphere Replication server might enter in Not Connected state. This might be because the thumbprint of the vSphere Replication Management server is mismatched in the vSphere Replication Management Server database and the embedded vSphere Replication server database.

    This issue is resolved in vSphere Replication 8.2.1.

  • NEW Configuring a replication fails with an "Operation failed" error

    Configuring a replication to a target vCenter Server fails with the following error

    Operation Failed A generic error occurred in the vSphere Replication Management Server. Exception details: 'Unexpected status code: 503'.

    Workaround: This issue is fixed in vSphere Replication 8.2.1.

Known Issues

The known issues are grouped as follows.

Upgrade

    Known Issues from Previous Releases

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

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