vSphere Replication 9.0 | 19 MAR 2024 | Build 23464962 | Download

vSphere Replication Configuration Import/Export Tool 9.0 | 19 MAR 2024 | Build 23467824 | Download

Check for additions and updates to these release notes.

vSphere Replication 9.0.0.1 | 19 APR 2024 | Build 23690274 replaces the previously released vSphere Replication 9.0 | 19 MAR 2024 | Build 23464962

What's New

vSphere Replication 9.0 provides the following new capabilities:

Product Support Notice

vSphere Replication has undergone some major enhancements in this release. The now Enhanced vSphere Replication includes automated load balancing and scaling to achieve higher performance, and when enabled with VMware Live Recovery provides a 1 minute RPO.

Traditional vSphere Replication routes traffic to the replication appliance at the target site. With Enhanced vSphere Replication, replication traffic goes directly to the host at the target site, bypassing the replication appliance while supporting backward compatibility at the same time supporting a more optimized data path allowing for increased simplicity, automatic scalability and automatic load balancing.

This release of vSphere Replication supports both versions of the data paths, while the next release will deprecate the traditional vSphere Replication data path and replication through the appliance in favor of Enhanced vSphere Replication. Switching over is simple and easy, and non-disruptive with details included in the documentation. See How do I reconfigure existing replications to use vSphere Replication with enhanced replication capabilities.

Localization

The new features and documentation of vSphere Replication 9.0 are available only in English.

Product Documentation

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

Compatibility

vSphere Replication 9.0 is compatible with vSphere 7.0 Update 3 and later, and supports ESXi versions 7.0 Update 3 and later.

For interoperability and product compatibility information, see the Compatibility Matrices for vSphere Replication 9.0.x.

For interoperability with earlier or later releases of VMware vSphere, see the Compatibility Matrices for vSphere Replication 9.0.

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 the installation, see the 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 8.8 or 9.0.

vSphere Replication 9.0 requires a supported vCenter Server version on both the source site and the target site. For more information, see VMware Product Interoperability Matrices.

Upgrading vSphere Replication

You use the ISO file and the VRMS Appliance Management Interface to upgrade from vSphere Replication 8.7.x or 8.8.x to vSphere Replication 9.0.

You cannot upgrade vSphere Replication from versions earlier than 8.7 to version 9.0 by using the Virtual Appliance Management Interface (VAMI). 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 9.0.

Notes:

  • When you use vSphere Replication with Site Recovery Manager, upgrade vSphere Replication on both of the protected and the recovery sites before you upgrade the Site Recovery Manager Server. After upgrading vSphere Replication, you must restart the Site Recovery Manager Server. For more information, see the VMware Site Recovery Manager Documentation.

Operational Limits of vSphere Replication

The operational limits of vSphere Replication 9.0 are documented in the VMware Knowledge Base. See Operational Limits for vSphere Replication 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 8.х and Configuring Upgraded vSphere Replication Appliances to Support up to 4000 Replications.

Open Source Components

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

Caveats and Limitations

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

  • Activating VMware Live Recovery is not supported if you have replications within a single vCenter Server (ROBO replications).

  • In a federated environment with linked vCenter Server instances, when you log in to the REST API gateway local site this will automatically log you in to the remote site. You do not have to make a POST /remote-session request. It is not possible to log in to the remote site with a different user name.

  • Resizing a replicated disk of a virtual machine by non-multiple of 512 bytes is not supported. If the disk is resized by non-multiple of 512 bytes, the replication fails. To return to the OK state, the disk size must be set to a multiple of 512 bytes.

  • vSphere Replication does not support the protection of virtual machines using persistent memory (PMem) devices.

  • vSphere Replication will stop working correctly if you run the vSphere Prevent Guest Operating System Processes from Sending Configuration Messages to the Host procedure on the vSphere Replication Appliance.

  • vSphere Replication does not support single virtual machine protection with two replication technologies. If a virtual machine is protected with VMware Live Cyber Recovery, it cannot be protected with vSphere Replication.

  •  vSphere Replication 9.0 does not provide support bundle management in the VRMS Appliance Management Interface. This includes lists with support bundles and deleting support bundles. To manage the support bundles through SSH, establish an SSH connection to the vSphere Replication Appliance.

  • 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 during the initial configuration process in the VRMS Appliance Management Interface. This requires user confirmation to proceed with the new appliance. This situation does not occur when deploying more than one vSphere Replication servers.

  • Each vSphere Replication Management Server can manage a maximum of 4000 replicated virtual machines. See Configuring Upgraded vSphere Replication Appliances to Support up to 4000 Replications (KB 2102463) and Requirements to the Environment... (KB 2107869).

  • vSphere Replication supports a maximum disk size of 62TB. If you attempt to activate 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.

  • vSphere Replication does not support VMware vSphere® Trust Authority™. vSphere Replication supports Standard Key Provider and VMware vSphere® Native Key Provider™.

  • When using the TRIM/UNMAP commands to reclaim space, if the UNMAP command is used at the source site, the replication traffic sends the command as a large stream of zeroes, unless compression is used on the replication. The data is stored as zeroes at the target site and space on the replica disks is not reclaimed.

Known Issues

  • New - You cannot upgrade from vSphere Replication version 8.7 to version 9.0.X

    When you try to update to vSphere Replication version 9.0.x from version 8.7, the process fails with the following error:

    Loading Linux 4.19.182-2. ph3error: file'/uMlinuz-4.19.182-2.ph3' not found.Loading initial ramdisk (...)

    Workaround: Upgrade to vSphere Replication version 8.8 first, then upgrade to version 9.0.x.

  • New - vSphere Replication alarms are not visible in the alarm definitions

    vSphere Replication events might not be visible when adding an alarm definition in vCenter Server 8.0 and vCenter Server 8.0 Update 1.

    Workaround: Upgrade your vCenter Server instance to vCenter Server 8.0 Update 2.

  • New - Upgrading the additional vSphere Replication server from version 8.x to 9.0 fails

    When you try to upgrade the additional vSphere Replication server from version 8.x to 9.0, the process fails, because the additional server does not have enough space in the filesystem to download the whole set of upgrade RPMs.

    Workaround 1: Temporarily increase the RAM of the additional vSphere Replication server to 4GB, until the upgrade is complete.

    1. Increase the RAM of the VM to 4GB.

    2. Reboot the vSphere Replication appliance.

    3. Perform the upgrade.

    4. Revert the RAM back to its previous setting.

    Workaround 2: Alternatively, if increasing the RAM is not possible, you can change the storage for the upgrade.

    1. Log in to the vSphere Replication appliance.

    2. Create the directory /var/tmp/upgrade.

    3. Modify the /usr/lib/systemd/system/dr-configurator.service file by adding Environment=TMPDIR=/var/tmp/upgrade to the [Service] section.

    4. Restart the dr-configurator service by using the commands systemctl daemon-reload && systemctl restart dr-configurator.

    5. Perform the upgrade.

    6. After the successful upgrade, clean up the /var/tmp/upgrade directory and revert the changes made to the dr-configurator service by using the rm -rf /var/tmp/upgrade command.

    7. Restart the dr-configurator service again by using the commands systemctl daemon-reload && systemctl restart dr-configurator.

  • New - Enhanced replications in a large-scale environment go into error state

    In a large-scale environment with configured enhanced replications, some replications might enter error state with the following message:

    The storage for datastore path '[iscsi-non-replicated-2] VM-001_-V7IK9/hbrdisk.RDID-0af5c276-5c88-3c25-a57f-d930548415ec.600.59577748295260.vmdk' is locked

    Workaround:

    1. Open /etc/vmware/hbrsrv.xml on all ESXi hosts.

    2. Add a new tag <useSVMirrorCombine>false</useSVMirrorCombine> under the <hbrsrv> tag and save the file.

    3. Restart all hbrsrvuw processes on all ESXi hosts.

    4. Once the processes are complete, reboot all ESXi hosts one by one.

  • New - Upgrading vSphere Replication from version 8.7.x to 9.0 appears to fail with an error

    When you upgrade vSphere Replication from version 8.7.x to 9.0, the process appears to fail with the following error: Unexpected status code: 503 or Operation Failed.

    The error messages are false positives and the upgrade is successful.

    Workaround: Restart the vSphere Replication appliance and verify the version number to confirm the successful upgrade.

  • New - If you are using vSphere Replication with a VMware Live Recovery license and try to configure a replication without enhanced capabilities, you see an incorrect RPO in the Configure Replication wizard

    When you start configuring or reconfiguring a replication without enhanced replication capabilities and you are running vSphere Replication with a VMware Live Recovery license, the RPO slider starts at 1 minute. While the minimum RPO for vSphere Replication with a VMware Live Recovery is 1 minute, the minimum RPO for replications without enhanced capabilities is 5 minutes.

    Workaround: Adjust the RPO slider to a minimum of 5 minutes.

  • New - vSphere Replication issues for VMware Live Site Recovery degraded and suspended modes remain after returning to operational mode

    You entered VMware Live Site Recovery degraded or suspended mode, returned to operational mode and the vSphere Replication issues remain. The problem is observed due to a delay in clearing the issues.

    Workaround: Wait one hour or restart the vSphere Replication Management server.

Known Issues from Previous Releases

For additional information, see the Troubleshooting vSphere Replication chapter in the vSphere Replication Administration guide.

  • The vSphere Replication Management service does not start after the upgrade

    After you upgrade vSphere Replication, the vSphere Replication Management (VRM) service appears as stopped in the VAMI, and the /opt/vmware/hms/logs/hms-configtool.log file in the virtual appliance contains java.net.ConnectException: Connection refused error messages.

    This problem is observed if the upgrade procedure of the embedded DB schema fails because the vPostgreSQL service was not fully started.

    Workaround:

    1. In the virtual appliance console, log in as the root user.

    2. Run the following command:

      $ /opt/vmware/hms/bin/hms-configtool -cmd upgrade -configfile /opt/vmware/hms/conf/hms-configuration.xml

      The DB schema upgrade starts.

    3. Wait for the DB upgrade procedure to complete.

    4. In the vSphere Replication VAMI, navigate to the Configuration tab, and complete the SSO registration of the appliance.

  • Changing the storage policy of a replication fails for an encrypted VM when the target datastore is vSAN or vSAN ESA

    If a replication uses a storage policy with vSAN storage attributes and virtual machine encryption, and then the replication is reconfigured to a storage policy without the vSAN storage attributes, the replication gets into an error state with the following message: 'Cannot apply policy to vSAN object <id> (status: 'failed'), fault: InvalidArgument, message: Non vSAN Profile' . This might happen in the workflows of configuring a replication with seeds, reversing a replication during a reprotect operation, or changing the storage policy during reconfigure replication.

    Workaround: Change the attributes of the new storage policy to use vSAN attributes.

  • Continuous HBR Agent VIB install errors in the vCenter Server tasks after upgrade

    After upgrading vCenter Server, if there are ESXi hosts in the inventory that are not managed by vSphere Lifecycle Manager, you might observe HBR Agent VIB install errors in the vCenter Server tasks view.

    Workaround: Reconfigure the vSphere Replication Management Server.

  • Failover or planned migration might fail due to storage errors

    At 4000 scale on the target datastore, the test failover or planned migration might fail with the following error: "Cannot create a failover image for group <GID> on vSphere Replication Server <server>. A problem occurred with the storage on datastore path <path>".

    Workaround: None.

  • A recovered virtual machine with multiple point-in-time instances enabled can lose the attached disks to the latest snapshot when you revert to a previous snapshot and then revert to latest snapshot again

    When you recover a virtual machine for which you enabled point-in-time instances and attach a disk for unresolved disks, if any, the disks attach to the latest snapshot. If you revert to a previous snapshot and then revert to the latest one, the attached disks are not available.

    Workaround: Edit settings of the virtual machine and add the required disks as existing hard disks.

  • Registering additional vSphere Replication servers takes a long time

    If vCenter Server manages several hundred ESXi Server hosts, registering an additional vSphere Replication server with the vSphere Replication appliance can take several minutes.This is because the vSphere Replication server must register with each ESXi Server host.

  • Recovery operation does not progress

    If, within a short period of time, you exclude a virtual disk with a vVOL target datastore from the replication, and then incluce it again, this might affect a subsequent recovery operation. If you attempt to perform the recovery, it might not progress.

    Workaround 1

    If you already started the recovery operation:

    1. Remove the replication, retaining the replica disks.

    2. Configure the replication again, using seeds.

    3. Perform recovery.

    Workaround 2:

    If you have not yet started the recovery operation:

    1. Exclude the disk with a vVOL target datastore.

    2. Sync the replication.

    3. Include the disk again.

    4. Perform recovery.

  • Replication sync does not progress

    If, within a short period of time, you exclude a virtual disk with a vVOL target datastore from the replication, and then incluce it again, this might affect a subsequent replication sync operation. If you attempt to perform a replication sync, it might not progress.

    Workaround:

    1. Exclude the disk with a vVOL target datastore.

    2. Sync the replication.

    3. Include the disk again.

  • When you attempt to configure IPv6 through the VMware VRMS Appliance Management you receive an invalid property - dns error

    When you attempt to configure IPv6 through the VMware VRMS Appliance Management and select the 'Obtain IPv6 settings automatically through router advertisement' option with auto assigned dns, the following error occurs invalid property - dns.

    Workaround:

    SSH to the vSphere Replication Appliance host machine and run $netmgr ip6_address --set --interface --dhcp 0 --autoconf 1.

    To receive an IP address through DHCP run $netmgr ip6_address --set --interface --dhcp 1 --autoconf 1.

  • You cannot reconfigure the IPv6 settings through the VMware VRMS Appliance Management

    If you have configured the IPv6 network with the 'Obtain IPv6 settings automatically through router advertisement' or 'Obtain IPv6 settings automatically through DHCP' option, you are unable to reconfigure the IPv6 settings with only 'Obtain IPv6 settings automatically through DHCP'. Either both options must be selected or none of them.

    Workaround:

    SSH to the vSphere Replication Appliance host machine and run $netmgr ip6_address --set --interface --dhcp 0 --autoconf 1.

    To receive an IP address through DHCP run $netmgr ip6_address --set --interface --dhcp 1 --autoconf 1.

  • Reconfiguring a replication fails after removing and then adding the same disk to a different Virtual Device Node on the source VM

    If you remove a virtual disk and add a new one with the same VMDK file, and then you try to perform a manual or an automatic (if you activated the Auto include new disks option) reconfiguration of the replication, the process fails with the following error:

    Cannot reconfigure replication group '<VM_ID>' (managed object ID: 'GID-<group-ID>'). Details: 'Duplicate key (hms.Disk) { dynamicType = null, dynamicProperty = null, deviceKey = <DEVICE_KEY>, destination = (hms.ExtendedDatastorePath) { dynamicType = null, dynamicProperty = null, datastore = MoRef: type = Datastore, value = <DATASTORE>, serverGuid = null, path = <PATH>, fileName = <FILENAME>, dsCluster = null }, storageProfileId = null, useOfflineCopy = false, virtualDiskType = thin, skipDiskUuidValidation = true, replicationDiskId = null, contentId = null, capacityInKb = <CAPACITY> }'. ThrowableProxy.cause The operation is not allowed in the current state.

    Workaround

    1. Stop the replication and preserve the replica disks.

    2. Configure the replication again by using the disks as seeds.

  • Configuring replication fails after switching from vSphere Trust Authority to KMS as an encryption mechanism

    If you are using vSphere Trust Authority as an encryption mechanism, but switch back to the old encryption mechanism using KMS servers, and then try to configure a replication, the process might fail. The problem is observed, because the encryption keys might not be properly distributed to the target hosts, after switching the encryption mechanisms.

    Workaround: Restart the HMS service.

  • Test recovery fails with an error

    If you configure a replication to a VMFS datastore and then reconfigure any disk of this group to be replicated to a vSAN datastore (while the VM home is still configured to a VMFS datastore), when you try to perform a test recovery, it fails with the following error:

    Cannot create a test bubble image for group '<group-ID>' on vSphere Replication Server...

    Workaround 1: Reconfigure all replica disks back to using a VMFS datastore.

    Workaround 2: Reconfigure the VM home to be replicated to a vSAN datastore.

  • When you right-click on a replicated VM and select Reconfigure Replication in the vSphere UI, the pop-up window for the Site Recovey UI is blocked without notification in Mozilla Firefox browser

    By default the Site Recovey UI opens in a new tab. When you right-click on a replicated VM and select Reconfigure Replication in the vSphere UI, the pop-up window for the Site Recovey UI is blocked without notification in Mozilla Firefox browser.

    Workaround: From the Options menu in Mozilla Firefox, select the Content tab and add the URL of the vCenter Server to the Pop-ups exception list.

  • Configuring a replication that uses seeds on a vVol target datastore succeeds, but the replication is in Error state

    If you configure a replication to use as a seed a VM that has snapshots, the configure operation succeeds, but the replication goes into the Error state at the end of the Initial Full Sync. An issue with a similar error description appears:

    A replication error occurred at the vSphere Replication Server for replication 'vmname'. Details: 'Error for (datastoreUUID: "vvol:9148a6192d0349de-94149524b5f52bc4"), (diskId: "RDID-fd3ed4de-2356-43c7-a0e2-7bc07a7da012"), (hostId: "host-33"), (pathname: "vmname/vmname.vmdk"), (flags: retriable): Class: NFC Code: 10; NFC error: NFC_DISKLIB_ERROR (Input/output error); Set error flag: retriable; Can't write (multiEx) to remote disk; Can't write (multi) to remote disk'.

    Workaround: Delete the snapshots from the seed VM.

  • During full synchronization vSphere Replication fails with error: A replication error occurred at the vSphere Replication Server

    During full synchronization vSphere Replication might fail with the following error.

    A replication error occurred at the vSphere Replication Server for replication <group_name>. Details: 'Error for (datastoreUUID: "..."), (diskId: "..."), (hostId: "..."), (pathname: "..."), (flags: retriable, pick-new-host, nfc-no-memory): Class: NFC Code: 5; NFC error: NFC_NO_MEMORY; Set error flag: nfc-no-memory; Code set to: Host unable to process request.; Set error flag: retriable; Set error flag: pick-new-host; Can't write (single) to remote disk'.

    Usually, this error is transient and the operation succeeds after some time.

  • Replacing the SSL certificate of vCenter Server causes certificate validation errors in vSphere Replication

    If you replace the SSL certificate on the vCenter Server system, a connection error occurs when vSphere Replication attempts to connect to vCenter Server.

    Workaround: For information about how to update vCenter Server certificates and allow solutions such as vSphere Replication to continue to function, see http://kb.vmware.com/kb/2109074.

  • Data synchronization fails and the log file of the source vSphere Replication Management Server contains error DeltaAbortedException

    If your environment experiences connectivity issues during data synchronization, you might observe the following problems.

    • Replication group synchronizations fail and the hms<n>.log file in the vSphere Replication Management server at the source site contains the following error message:

      DeltaAbortedException.

    • In Site Recovery Manager, replication group synchronizations fail with the following error message:

      VR synchronization failed for VRM group <group_name>. A generic error occurred in the vSphere Replication Management Server. Exception details: 'com.vmware.hms.replication.sync.DeltaAbortedException'.

    Workaround: Resolve the connectivity issues in your environment before you proceed.

  • Failover with "Sync latest changes" might fail with SocketTimeoutException when multiple replications are recovered concurrently and there is a huge accumulated delta since the latest synchronization

    The vSphere Replication Management server might not receive due responses through the vCenter reverse proxy when there is heavy replication traffic at the same network. Some replication management or monitoring operations might fail with the following error message:

    com.vmware.vim.vmomi.client.exception.ConnectionException: java.net.SocketTimeoutException: Read timed out

    Workaround: Configure network traffic isolation for vSphere Replication traffic, so that the management communication between vCenter and the vSphere Replication Management server is not affected by the heavy replication traffic. See Isolating the Network Traffic of vSphere Replication.

  • Replications appear in Not Active (RPO violation) status after changing the IP address of the vSphere Replication server at the target site

    If the IP address of the vSphere Replication server at the target site changes, the status of all replications to this site turns to Not Active (RPO violation). This problem is observed because replications on the source site are not reconfigured automatically when the IP address changes.

    Workaround: Reconfigure all replications, so that the source hosts use the new IP address of the target vSphere Replication server.

  • The option to activate quiescing is deactivated in Configure Replication wizard for a powered off replication source VM, though the guest OS supports quiescing

    For both Linux and Windows sources, the Enable Quiescing option is activated based on the information about the guest OS. If a virtual machine has never been powered on, ESXi hosts always report no support for quiescing, because the guest OS information is not available.

    Workaround: Verify that replication source VMs have been powered on at least once before you configure replications.

  • vSphere Replication service is inaccessible after vCenter Server certificate changes

    If the vCenter Server certificate changes, vSphere Replication becomes inaccessible.

  • During replication of multiple virtual machines, a vSphere Replication server might enter a state where it does not accept any further VRMS connections but continues to replicate virtual machines

    Workaround: Reboot the vSphere Replication server.

  • vSphere Replication operations fail with a Not Authenticated error

    If you start an operation on one site, for example configuring vSphere Replication on a virtual machine, and then restart vCenter Server and the vSphere Replication appliance on the other site, vSphere Replication operations can fail with the error VRM Server generic error. Please check the documentation for any troubleshooting information. The detailed exception is: 'com.vmware.vim.binding.vim.fault.NotAuthenticated'.

    This problem is caused by the fact that the vSphere Replication server retains in its cache the connection session from before you restarted vCenter Server and the vSphere Replication appliance.

    Workaround: Clear the vSphere Replication connection cache by logging out of the vSphere Web Client and logging back in again.

  • Operation in vSphere Replication Management Server fails with error "... UnmarshallException"

    When the vSphere Replication Management Server experiences high load or transient network errors, operations can fail with UnmarshallException due to errors in the communication layer.

    Workaround: Try the failed operation again.

  • vSphere Replication operations fail when there is heavy replication traffic

    vSphere Replication operations might fail with error java.net.UnknownHostException. These errors occur because DNS requests are dropped due to network congestion.

    Workaround: Configure your network to ensure that management traffic is not dropped, by configuring traffic shaping, quality of service, or DNS on the vSphere Replication appliance. One possible solution is to modify the network address caching policy for the vSphere Replication appliance.

    1. Log into the vSphere Replication appliance as root.

    2. Open the file /usr/java/jre-vmware/lib/security/java.security in an editor.

    3. Uncomment the line networkaddress.cache.ttl and set its value to at least 86400 seconds (24 hours) or to the longest time that is required for an initial full sync to complete.

    4. Save the file and reboot the vSphere Replication appliance.

    5. Repeat the procedure for all remaining vSphere Replication appliances.

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