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

VMware Site Recovery Manager 8.2.0.2 |  03 OCT 2019 | Build 14761905 | Release Notes

VMware Site Recovery Manager 8.2.0.2 Virtual Appliance |  03 OCT 2019 | Build 14761906 | Release Notes

VMware vSphere Replication 8.2.0.2 | OCT 3 2019 | Build 14761900 | Release Notes

VMware Site Recovery Manager 8.2.0.1 |  13 AUG 2019 | Build 14338491 | Release Notes

VMware Site Recovery Manager 8.2.0.1 Virtual Appliance |  13 AUG 2019 | Build 14383141 | Release Notes

VMware vSphere Replication 8.2.0.1 | AUG 13 2019 | Build 14338525 | Release Notes

VMware Site Recovery Manager 8.2 | 09 MAY 2019 | Build 13480383 | Release Notes

VMware Site Recovery Manager 8.2 Virtual Appliance | 09 MAY 2019 | Build 13481390 | Release Notes

VMware vSphere Replication 8.2 | 09 MAY 2019 | Build 13480246  | Release Notes

Check for additions and updates to these release notes.

What's in the Release Notes

The release notes cover the following topics:

What's New January 14, 2020

  • vSphere Replication Configuration Import/Export Tool

VMware Site Recovery™ now offers vSphere Replication Configuration Import/Export Tool, which can be used to export and import configuration data of the replications created in vSphere Replication. If you plan to migrate vSphere Replication configuration to a different SDDC, you can use the tool to export the replications settings the related objects into an XML file. You can then import the configuration data from the previously exported file. You can find more details about the tool in the VMware Site Recovery documentation covering Exporting and Importing Replication Configuration Data.

What's New November 3, 2019

  • VMware Site Recovery 1-year and 3-year subscriptions

Avail of significant cost savings compared to on-demand consumption with VMware Site Recovery 1-year and 3-year subscriptions. In addition to the on-demand model where you can pay as you go for usage of VMware Site Recovery, you can now also commit to and pay upfront for virtual machine protection and secure term discounts for one or three year terms. The commitment is made for a number of virtual machines and a specific region. Once a subscription is created, hourly usage for a given region up to the cumulative number of virtual machines committed to across all active subscriptions for that region will not incur on-demand VMware Site Recovery charges. Usage over the cumulative committed number of virtual machines in a given region will incur on-demand charges according to prevailing on-demand rates published at https://cloud.vmware.com/vmc-aws/pricing. For more details, see the VMware Site Recovery FAQ page, and for instructions on how to create a VMware Site Recovery subscription, consult the Getting Started section in the VMware Site Recovery documentation.

What's New October 21, 2019

  • DR protection for up to 1500 VMs per SDDC

VMware Site Recovery™ now supports replication of up to 1,500 virtual machines to a single target VMware Cloud™ on AWS Software Defined Data Center (SDDC), allowing you to protect larger environments. For more details, see Operational Limits of Site Recovery Manager in the VMware Site Recovery documentation.

What's New June 13, 2019

  • Site Recovery Manager available as appliance for on-premises deployment

For customers protecting between on-premises datacenter and VMware Cloud on AWS SDDC, reduce layers of complexity associated with Windows Server by leveraging a Linux based operating system - Photon OS, purpose-built for only disaster recovery functions. Streamline deployment on-premises by installing the Site Recovery Manager virtual appliance directly from vCenter Server.

  • Enhancements to Site Recovery UI 

Includes ability to import/export configuration, a dark theme, view capacity information in Protection Groups Datastores tab, and monitor target datastores in the replication details pane.

What's New April 19, 2019

  • DR protection of on-premises NSX-T based data centers

VMware Site Recovery now supports DR protection of on-premises NSX-T based data centers to VMware Cloud on AWS using VMware Site Recovery. For more details, see the VMware Site Recovery Manager 8.1.2 Release Notes.

What's New February 12, 2019

  • Site Recovery connectivity checker in Troubleshooting tab

Accelerate your deployment of VMware Site Recovery™ using single-click tests from the Troubleshooting tab of the SDDC in the VMware Cloud on AWS console. These tests can help to identify network connectivity issues affecting VMware Site Recovery™. The tests verify connectivity from the current SDDC toward the remote site, which itself can be an on-premises site or another VMware Cloud on AWS SDDC. The "Site Recovery" option will show up in the use case drop-down menu of the Troubleshooting tab when the Site Recovery add-on is active for the SDDC. For more information, see Validate Network Connectivity for VMware Site Recovery in the VMware Site Recovery documentation.

  • Support for fan-in and other multi-site topologies

VMware Site Recovery™ now supports fan-in and other multi-site topologies, allowing you to connect a single VMware Cloud™ on AWS SDDC that is based on NSX-T to multiple on-premises sites and/or to other VMware Cloud on AWS SDDCs for disaster recovery purposes. You can pair up to ten remote sites with a single SDDC. You can recover virtual machines from multiple protected sites to the same VMware Cloud on AWS SDDC, or recover different sets of virtual machines from a single VMware Cloud on AWS SDDC to multiple recovery sites. Other complex multi-site topologies are also now possible provided you can establish network connectivity between the remote sites and the shared VMware Cloud on AWS SDDC. For more information, see VMware Site Recovery in a Multi-Site Topology in the VMware Site Recovery documentation.

What's New December 18, 2018

The following new features and changes are Available or in *Preview for this release:

Definitions

Available: Feature now available for use by applicable customers and may not be available in all AWS regions

*Preview: Feature released in preview to gather feedback. May not be available to all applicable customers or in all AWS regions*

*We cannot guarantee that features marked as ‘Preview’ will become available within any particular time frame or at all. Make your purchase decisions only on the basis of features that are Available

Features listed below are Available unless indicated as *Preview.

  • Support for fan-in and other multi-site topologies (*Preview)

VMware Site Recovery™ now supports fan-in and other multi-site topologies, allowing you to connect a single VMware Cloud™ on AWS SDDC that is based on NSX-T to multiple on-premises sites and/or to other VMware Cloud on AWS SDDCs for disaster recovery purposes. You can pair up to four remote sites with a single SDDC. You can recover virtual machines from multiple protected sites to the same VMware Cloud on AWS SDDC, or recover different sets of virtual machines from a single VMware Cloud on AWS SDDC to multiple recovery sites. Other complex multi-site topologies are also now possible. For more details on multi-site topologies, see the VMware Site Recovery documentation.

What's New December 7, 2018

  • DR protection for up to 1000 VMs per SDDC

VMware Site Recovery™ now supports replication of up to 1,000 virtual machines to a single target VMware Cloud™ on AWS Software Defined Data Center (SDDC), allowing you to protect larger environments. For more details, see Operational Limits of Site Recovery Manager in the VMware Site Recovery documentation.

What's New November 2, 2018

  • Support for NSX-T

VMware Site Recovery™ now supports protecting to or from VMware Cloud™ on AWS SDDCs based on NSX-T, giving users more flexibility and control over their networking configuration for their disaster recovery needs.

What's New October 22, 2018

  • Fan-out topology improvements - Activate DR with custom Site Recovery Manager extension ID 

VMware Site Recovery can now be activated on a VMware Cloud on AWS SDDC with a custom extension ID which allows you to pair this instance with an on-premises Site Recovery Manager installation using a custom plug-in identifier or a VMware Site Recovery instance on another VMware Cloud on AWS SDDC deployed with the same custom extension ID. This makes it easier to incrementally implement fan-out disaster recovery topologies. For example, if you already have an on-premises Site Recovery Manager installation deployed with the default plug-in identifier and paired with another on-premises Site Recovery Manager instance or with another VMware Cloud SDDC, you can now install a second on-premises Site Recovery Manager in the same vCenter Server instance with a non-default custom plug-in identifier and pair it to a newly deployed VMware Site Recovery instance activated with the same custom extension ID.

What's New September 6, 2018

  • New region: Asia Pacific (Sydney)

VMware Site Recovery™ now supports activation on SDDCs provisioned in the Asia Pacific (Sydney) region of VMware Cloud™ on AWS.

  • Optimize resource management of your DR cluster after failover, by automating cluster scaling with Elastic DRS.

You can now automate cluster scaling with Elastic Distributed Resource Scheduler (DRS). The Elastic (DRS) automatically scales the number of hosts up or down in an SDDC cluster based on CPU, memory, and storage utilization.

 

What's New May 17, 2018

  • New region: EU (Frankfurt)

VMware Site Recovery™ now supports activation on Software Defined Data Centers (SDDCs) provisioned in the EU (Frankfurt) region of VMware Cloud™ on AWS.

  • Multi-site disaster recovery topology support: fan-out from on-premise

Extend your existing on-premises disaster recovery strategy to the cloud by protecting some on-premises workloads to VMware Cloud™ on AWS using VMware Site Recovery™ while simultaneously protecting other workloads managed by the same on-premises vCenter Server to a secondary on-premises disaster recovery site. Multiple instances of Site Recovery Manager 8.1 can be deployed on-premises, with one paired to VMware Cloud™ on AWS for disaster recovery as a service (DRaaS) and others paired to secondary data centers.

  • Replication Seeding

Accelerate time to protection by leveraging previously replicated base disks of virtual machines as the seeds for the new replication. Replication for VMs that have been protected in the past is able to use previously replicated base disks as seeds, instead of requiring an initial full synchronization.​ For more information, see Replicating Virtual Machines Using Replication Seeds in the vSphere Replication 8.1 Administration guide.

  • Backward compatibility with older vCenter Server versions

Simplify DR protection by pairing VMware Site Recovery™ with sites running earlier versions of vCenter Server. Building on previous releases, VMware Site Recovery™ is compatible with multiple versions of vCenter Server, allowing you to protect sites running vCenter Server versions 6.7, 6.5, and 6.0U3.

 

What's New March 7, 2018

  • New region: EU (London)

VMware Site Recovery™ now supports activation on Software Defined Data Centers (SDDCs) provisioned in the EU (London) region of VMware Cloud™ on AWS.

  • Site Recovery Firewall Rules Accelerator

VMware Site Recovery™ now provides a Firewall Rules Accelerator user interface in the VMware Cloud™ on AWS console to streamline the process of creating firewall rules between your on-premises data center and the Management Gateway for disaster recovery purposes. Currently, these firewall rules must be manually created in the Network tab of the SDDC to allow data replication traffic in both directions, communication with the Site Recovery Manager and vSphere Replication management components, and access to the VMware Site Recovery user interface. While you can still follow this manual process to create the rules, now you also have the option of using the Firewall Rules Accelerator to automatically generate the required rules for a remote network that you specify. Rules created through the Firewall Rules Accelerator can be subsequently viewed, edited, and deleted using the Network tab of the SDDC.

What's New November 28, 2017

  • Disaster Recovery as a Service VMware Site Recovery now Generally Available

About VMware Site Recovery

The VMware Site Recovery™ service expands and simplifies traditional disaster recovery operations by delivering on-demand site protection across a common, vSphere-based operating environment from on-premises to the cloud. The service protects workloads between on-premises datacenters and VMware Cloud™ on AWS, and between different instances of VMware Cloud™ on AWS. Built on top of the enterprise-grade recovery plan automation of VMware Site Recovery Manager and the native hypervisor-based replication capabilities of vSphere Replication, the service provides an end-to-end disaster recovery solution that reduces the requirements for a secondary disaster recovery site, accelerates time-to-protection, and simplifies disaster recovery operations.

Key Features

  • Natively integrated into VMware Cloud™ on AWS
  • Proven Site Recovery Manager orchestration and automation capabilities
  • Recovery plan orchestration delivers aggressive RTO capabilities
  • Non-disruptive testing of disaster recovery plans
  • VM-centric replication for fine-grained control
  • Support for bulk migration of workloads to VMware Cloud on AWS
  • Streamlined HTML 5 user interface
  • Support for multiple vSphere versions on-premises

Localization

VMware Site Recovery is available in the following languages:

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

Earlier releases of VMware Site Recovery components

VMware Site Recovery Manager

Features, known issues, and resolved issues of Site Recovery Manager are described in the release notes for each release. Release notes for earlier releases of VMware Site Recovery Manager are:

vSphere Replication

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 are:

Caveats and Limitations

VMware Site Recovery

  • Site Recovery Manager server call-out scripts and Pre-Power On Steps on the recovery Site Recovery Manager server on VMware Cloud on AWS are not supported.
  • VMware Site Recovery supports the protection of a single VMware Cloud on AWS SDDC to up to ten different recovery sites.
  • VMware Site Recovery supports the protection of up to ten protected sites to a single VMware Cloud on AWS SDDC shared recovery site.
  • Array-based replication is not supported with VMware Cloud on AWS.
  • vApps replication is not supported with VMware Cloud on AWS.
  • vSphere Replication self-replication is not supported.
  • Multiple point in time instances are not supported.
  • Replication to a vCloud Director-based cloud is not supported.
  • If the Alarms tab is not selected, there is no visible notification for new Site Recovery Manager or vSphere Replication alarms.
  • VMware Site Recovery standalone UI does not display vSphere Replication server tasks, events, and alarms. To check the vSphere Replication server tasks, events, and alarms, go to the vSphere Client.
  • The cloud admin user cannot define, acknowledge or reset alarms in Site Recovery Manager and on the cloud site vCenter Server.
  • The following advanced settings are available in the VMware Site Recovery UI but are not supported in VMware Site Recovery
    • Storage Provider
    • ABR Storage Policy
    • Storage
  • vSphere Flash Read Cache is disabled on virtual machines after recovery and the reservation is set to zero. Before performing a recovery on a virtual machine that is configured to use vSphere Flash Read Cache, take a note of the virtual machine's cache reservation from the vSphere Web Client. You can reconfigure vSphere Flash Read Cache on the virtual machine after the recovery.
  • To use Two-factor authentication with RSA SecureID or Smart Card (Common Access Card) authentication your environment must meet the following requirements:
    1. Use the administrator credentials of your Platform Services Controller to install Site Recovery Manager and to pair your Site Recovery Manager sites.
    2. The vCenter Server instances on both Site Recovery Manager sites must work in Enhanced Linked Mode. To prevent failures during upgrade of Site Recovery Manager from to a newer version of Site Recovery Manager, the vCenter Server instances on both sites must be direct replication partners.

vSphere Replication

  • Encryption of replication traffic flows from the source ESXi host to the vSphere Replication server at the target site is not supported when using VMware Site Recovery.
  • You cannot configure the vSphere Replication appliance when the Platform Services Controller is installed with a custom port.
  • 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.
  • 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.
  • The 5 minute RPO requires the source host to be ESXi 6.0U3 or later for vSAN, and ESXi 6.5 for other supported datastores.
  • vSphere Replication 8.2 does not support the virtual NVMe (vNVMe) capability in VMware vSphere.
  • The 5 minute RPO scales to a maximum supported limit of 50 VMs on a provisional VVOL datastore.

Resolved Issues

  • If you open the History tab of a recovery plan that you have not run yet, you might see an Operation Failed error

    When you open the History tab of a recovery plan that you have not run yet, you might see the following error:
    Error: Operation Failed
    The recovery plan history identified by '-2300' was not found.

    This issue is fixed.

  • If you use a Firefox browser, you cannot configure for replication multiple virtual machines

    If you use a Firefox browser, you receive an error when you attempt to configure for replication multiple virtual machines.

    This issue is fixed.

  • If you use an Active Directory user account for VMware Site Recovery operations​, you receive the error: Permission to perform this operation was denied.

    When you use Hybrid Linked Mode the Active Directory user account that is used to access inventories both on the cloud and on-premises is not authorized to work with VMware Site Recovery. If you try to pair Site Recovery sites or to replicate virtual machines, you receive the error: Permission to perform this operation was denied. You must log in with the cloudadmin@vmc.local user for VMware Site Recovery operations on the VMware Cloud on AWS site.

    This issue is fixed.

  • When using Internet Explorer 11 or Edge browsers, you might notice slow performance in rendering while interacting with the VMware Site Recovery UI

    You experience slow performance in rendering of the VMware Site Recovery UI in Internet Explorer 11 and Edge browsers.

    This issue is fixed.

  • Unsupported version errors appear on every refresh operation in the Site Recovery Manager 6.5 user interface

    If you have Site Recovery Manager 6.5 and Site Recovery Manager 8.x registered under the same Platform Services Controller or under federated PSCs, you get unsupported version errors on every refresh operation in the Site Recovery Manager 6.5 UI.

    This issue is fixed in Site Recovery Manager 6.5.1.1.

Known Issues

  • NEW You can access the ability to resize virtual machine disks replicated by vSphere Replication, if you have disaster recovery protection between two VMware Cloud on AWS SDDCs of version 1.9. This ability is not fully supported and has known limitations.

    If you plan to use the ability to resize virtual disks, you might encounter the following known limitations:

    1. When the replicated disk is resized, vSphere Replication 8.2.x automatically resizes the corresponding replica disk on the recovery site. During the process of resizing the replica disks, the replica disks are not in a consistent state and the replication is not recoverable during that time. Depending on the size of the delta to sync (generated on the protected VM in the meantime) and the network bandwidth, the duration of the non-recoverable period might vary. 
    2. If the multiple points in time option is configured for the replication, during the process of resizing the replica disk, all existing points in time are lost. After the disk resizing completes, the creation of new points in time will continue. As a result, after recovery you will get snapshots of the recovered VM only for the points in time after the protected disk was extended. 

    Workaround: Avoid using the ability to resize virtual machine disks replicated by vSphere Replication until full support for the ability is announced. If the replication is configured with seed disks, you can manually resize the disk files on the replica site. See Resize the Virtual Machine Disk Files of a Replication that Uses Replication Seeds in the VMware Site Recovery Administration guide.

  • You might see a warning "Privilege check failed for user VMC.LOCAL\cloudadmin for missing permission VirtualMachine.Hbr.ConfigureReplication. Session user performing the check:" in the Task & Events view on various management virtual machines

    When you have Vware Site Recovery activated with Site Recovery Manger 8.2 or earlier and you log in to the vSphere user interface on the VMware Cloud on AWS SDDC, you might see a warning "Privilege check failed for user VMC.LOCAL\cloudadmin for missing permission VirtualMachine.Hbr.ConfigureReplication. Session user performing the check:" in the Task & Events view on various management virtual machines. The message is a result of the Site Recovery Manager plug-in present in the vSphere UI when Site Recovery Manager is installed. The plug-in does not consider that by design the cloudadmin user does not have certain permissions on the management VMs in the SDDCs, which in turns triggers the warnings.

    Workaround:Ignore the warnings. They do not impact the workflows.

  • The Summary page of the Site Recovery user interface displays an Unable to retrieve vSphere Replication summary data error message

     In SDDC Version 1.8 and later, the vCenter Server Extension Manager does not return vSphere Replication data for users in the Cloud Admin group. When you open the Summary page of a site pairing, the value for the Domain Name/IP for the vSphere Replication appliance is blank and the following error message appears: Unable to retrieve vSphere Replication summary data. 

    Workaround: Ignore the error.

  • You cannot remove or force stop a replication

    If you are logged only in the target site and not on the source site, you cannot remove or force stop a replication.

    Workaround: Use the vSphere Replication Management Server Managed Object Browser by opening https://vrms_address:8043/mob/?vmodl=1.

    1. For incoming replications, navigate to content > replica-manager > getIncomingReplications. For outgoing replications, navigate to content > replication-manager > getOutgoingReplications.
    2. Change the parametres as follows:
    start: 0
    count: 2000
    Clear sorters and filter and leave them blank, then click Invoke Method.
    3. Find the replication that you need to remove by looking for the VM name and copy the replication ID (GID-<uuid> value).
    4. Click on the replication ID value > destroy > Invoke method.
    5. Click on val > info and ensure that the state value is success and the error value is Unset.

    If the task is still in progress, refresh the info window and wait until it completes.

  • When you open the Site Recovery user interface from the vSphere Client, you might receive a connection timeout error

    The Site Recovery Manager and vSphere Replication user interface client service instance runs inside the vSphere Replication appliance and each Site Recovery Manager appliance. Each UI client service has a browser part and UI-backend part. The UI-backend is a java process called dr-client and is a web application. The Site Recovery single pane of glass from the vSphere Client scans for all Site Recovery Manager and vSphere Replication UI instances in the Lookup Service, checks which are healthy and which are on the latest version, and reports it. As a result the link from the vSphere Client might point to a Site Recovery UI served by one of the Site Recovery Manager appliances. Depending on the firewall configuration, that might cause some connections to fail.

    Workaround: Open the Site Recovery user interface from the vSphere Replication appliance on the Site Recovery add-on card in the VMware Cloud on AWS Console.

  • The default datastore storage policy is not applied on the target vSAN datastore

    When you configure a new replication or reconfigure an existing replication to a vSAN datastore from the Site Recovery user interface and select Datastore Default storage policy, the policy is not applied on the replication files at the target datastore. The datastore policy is correctly applied if it is explicitly selected from the drop-down menu.

    Workaround: Select the correct storage policy from the drop-down menu, when the target datastore is vSAN.

  • Configuration of the Site Recovery Manаger resource mappings fails with a permission error for the cloud SDDC

    If your cloud SDDC is not using flexible permission model and you add an additional cluster after the activation of the VMware Site Recovery service, when you select a resource pool or datastore from that additional cluster in the resource mappings, you receive a permission error.

    Workaround: Open a case with VMware support to fix the permissions configuration for your cloud SDDC.

  • 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. Migrate 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.

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

    If you are using vSphere Replication and you are running a protected VM on ESXi 6.7 or ESXi 6.7 Update 1, an initial or full synchronization of replications might stop progressing before completion. The synchronization of replications remains in progress, but the checksum bytes value in the replication details information does not progress. The power off, take a snapshot, revert to snapshot, and migration VM operations fail with a timeout or Task in progress errors.Workaround:

    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.
    Note: This workaround disables the checksum part of the sync process and all of the allocated blocks will be sent to the remote site, regardless of whether they are different or not. This workaround disables the seed functionality.

  • During the very first login in the vCenter Server on VMware Cloud on AWS, the VMware Site Recovery plug-in might not appear into the vSphere HTML5 client

    When you simultaneously deploy a Software-Defined Data Center on VMware Cloud on AWS and activate the VMware Site Recovery service, the VMware Site Recovery plug-in does not appear into the vSphere HTML5 client on the very first login.

    Workaround: Log out from the vSphere HTML5 client and then log in again.

  • Site Recovery Manager status in the VMware Site Recovery HTML 5 and Flex plug-in in the vSphere Web Client might indicate OK, if the SRM server is installed but disconnected

    Site Recovery Manager status in the VMware Site Recovery HTML 5 and Flex plug-in in the vSphere Web Client might indicate OK, if the Site Recovery Manager server is installed but disconnected.

    Workaround: Check the Site Recovery Manager connection status in the VMware Site Recovery HTML 5 standalone user interface.

  • When using Internet Explorer or Firefox, you cannot select custom date from the drop down menu for a recovery plan history report

    If you use Internet Explorer or Firefox browsers, when you select a custom date in the Recovery Plan>History tab a java.lang.NullPointerException error occurs.

    Workaround: Use Chrome browser.

  • When using Internet Explorer the Register new replication server list is empty

    When you attempt to register new vSphere Replication server using Internet Explorer, the Register new replication server list is empty

    Workaround: Use Chrome browser.

  • The Configure Replication action in the VMware Site Recovery HTML 5 UI plug-in is not displayed when you use vSphere 6.5 U1 HTML 5 UI in your on-premises environment

    If you use vSphere 6.5 U1 HTML 5 UI for your on-premises environment, the Configure Replication action in the VMware Site Recovery HTML 5 UI plug-in is not displayed.

    Workaround 1: Restart the vSphere HTML 5 client and login again.

    1. Logout from vSphere HTML 5 client.
    2. SSH to vCenter Server and run the following commands:
      service-control --stop vsphere-ui
      service-control --start vsphere-ui
    3. Login in the vSphere HTML 5 client.

    Workaround 2: Use the vSphere Flex Web Client.

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

    By default the VMware Site Recovery 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 VMware Site Recovery 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.

  • When you select Export All from Recovery Plans History for a time period with no entries, you get Response with status: 500 OK for URL: error

    When you go to the Site Pair > Recovery Plan History and select Export All for a time period with no entries, you get the following error.
    500 - OK
    Response with status: 500 OK for URL:...

    Workaround: Discard the error and select a time period with run plan entries to export.

  • Recovery fails for VMs that have CD or floppy images backed with images from vmimages folder

    If you have a protected virtual machine that has CD or floppy images that were backed with images from vmimages folder, recovery operation fails with Invalid datastore path error.

    Workaround: Do not use images from vmimages folder for backing.

  • vSphere HTML 5 client does not load if you have Windows vCenter Server 6.5 U1 installed with custom port

    If you have installed Windows vCenter Server 6.5 U1 with a custom port, for example 8443, when you attempt to use the vSphere HTML 5 client, you get the following error: Empty SSO response string.

    Workaround 1:

    1. Open file C:\ProgramData\VMware\vCenterServer\runtime\vsphere-ui\server\configuration\tomcat-server.xml
    2. Find the entries below and edit port 443 to 8443 accordingly:
      <connector ...="" address="127.0.0.1" port="5090" protocol="HTTP/1.1" proxyport="443"></connector>
      <connector ...="" address="::1" port="5090" protocol="HTTP/1.1" proxyport="443"></connector>
    3. Restart the vsphere-ui service:
      C:\Program Files\VMware\vCenter Server\vmon\vmon-cli" --restart vsphere-ui

    Workaround 2: Use the vSphere Flex Web Client.

  • You might see a link to Configure vSphere Replication appliance in a VMware Cloud on AWS environment

    You might see a link to Configure vSphere Replication appliance in a VMware Cloud on AWS environment. When you click on the link nothing happens as you do not have access to the virtual appliance management interface UI.

    Workaround: None. Ignore the link.

  • Site Recovery Manager plug-in does not display in the vSphere Web Client if Site Recovery Manager service stops

    After you install Site Recovery Manager and the service stops for any reason, the vSphere Web Client does not display the Site Recovery Manager plug-in.

    Workaround: Restart the vSphere Web Client.

  • You cannot configure replication for a virtual machine that has vmdk files with the same name

    A virtual machine can have vmdk files (hard disks) with the same name. This might happen when you add a new hard disk to a virtual machine after you have created the VM, and the new disk is on a different datastore from the existing hard disks. Such virtual machine cannot be configured for replication.

    Workaround: None.

  • After uninstalling vSphere Replication 8.0, the VMware Site Recovery plug-in is still visible in the vSphere Client

    If you uninstall vSphere Replication 8.0 of the VMware Site Recovery service, the VMware Site Recovery plug-in in the vSphere Client is still visible.

    Workaround: Restart the vSphere Client service.