This site will be decommissioned on December 31st 2024. After that date content will be available at techdocs.broadcom.com.

Site Recovery Manager 8.7.0.4 | 01 FEB 2024 | Build 23166357 | Download

Check for additions and updates to these release notes.

VMware Site Recovery Manager 8.7.0.4 is a minor product patch release that provides bug fixes and improvements. The content of the VMware Site Recovery Manager 8.7 Release Notes and all following 8.7.0.x patch release notes applies to this version as well.

What's New in Site Recovery Manager 8.7.0.4

  • The VMware Site Recovery Manager 8.7.0.4 Express Patch provides bug fixes.

  • Updated Postgres to version 13.13.

  • Updated the Tomcat server.

Installation and Upgrade

For information about installing and upgrading Site Recovery Manager, see Site Recovery Manager Installation and Configuration.

For the supported upgrade paths for Site Recovery Manager, select Upgrade Path and VMware Site Recovery Manager in the VMware Product Interoperability Matrices.

If you are running Site Recovery Manager 8.7.0.x, upgrade to Site Recovery Manager 8.7.0.4. See Upgrading Site Recovery Manager in Site Recovery Manager 8.7 Installation and Configuration for instructions about upgrading Site Recovery Manager.

If you use vSphere Replication with Site Recovery Manager 8.7.0.x, upgrade the vSphere Replication appliance to version 8.7.0.4. See the vSphere Replication 8.7.0.4 Release Notes for information about vSphere Replication 8.7.0.4.

NOTES:

  • VMware Site Recovery Manager 8.5.x was the last general version that supports storage policy protection groups (SPPGs). You must either remove or migrate your SPPGs to regular array-based replication protection groups before upgrading to Site Recovery Manager 8.7.0.x Site Recovery Manager 8.5.0.5 and 8.6.x has a dedicated Storage Policy Protection Group (SPPG) migration tool that you can use to migrate your SPPGs to regular array-based replication protection groups. See, Migrating Storage Policy Protection Groups to Array-Based Replication Protection Groups to learn how to use the tool.

  • If the vCenter Server instances on the protected and recovery sites are in Enhanced Linked Mode, they must be direct replication partners. Otherwise, upgrade might fail.

Resolved Issues

  • IP customization of RHEL 9 VMs might fail

    In RHEL 9, Network Manager introduced a change that employs key files as the default storage method for new connection profiles. Site Recovery Manager 8.7.0.3 and earlier 8.7.0.x versions use ifcfg files and as a result IP customization of RHEL 9 VMs might fail.

    This issue is fixed in Site Recovery Manager 8.7.0.4.

  • Running a failover of Virtual Volumes protection groups might fail

    When there are many virtual machines in a Virtual Volumes fault domain, the moId of some of the virtual machines has a common prefix, for example, vm-12 and vm-123, causing Site Recovery Manager to fail to match the correct storage profile. As a result the failover operation fails.

    This issue is fixed in Site Recovery Manager 8.7.0.4.

  • VM tags are changed after performing a failover

    When assigning tags to virtual machines, if there are more than ten categories on the same VM, the category of some tags changes after performing a failover.

    This issue is fixed in Site Recovery Manager 8.7.0.4.

  • Site Recovery Manager REST API GET request returns an error

    Using the VMware REST API Explorer to execute 'GET https://{api_host}//storage-replication-adapters' request returns "Config service not found error". The dr-rest-api.log contains the following errors.

    YYYY-MM-DD 06:39:56,590 [http-nio-127.0.0.1-9900-exec-2] INFO com.vmware.dr.restapi.infrastructure.requestHandlers.proxy.ProxyFilter YTlmNjk0MWItMDUzMy00YTIxLThhYmItOWEwZmYwZmQ3NzZj 65547c77-a35c-4586-ae9b-94cb49aa0499 /sra/load - Proxy GET request will be to URL
    [http://127.0.0.1:5480/sra/load].
    YYYY-MM-DD 06:39:56,620 [I/O dispatcher 398] WARN com.vmware.dr.restapi.infrastructure.http.AsyncHttpResponseConsumer - Response failed: javax.ws.rs.NotFoundException: HTTP 404 Not Found

    This issue is fixed in Site Recovery Manager 8.7.0.4.

  • Site Recovery Manager request for query sync status shows incorrect tag in the XML for ongoing sync use case

    There is an issue in the XML structure for querying the sync status. Instead of the <ConsistencyGroups> tag, the XML shows the <TargetGroups> tag.

    <QuerySyncStatusParameters>
    <ArrayId>xxxx</ArrayId>    
    <PeerArrayId>xxxx</PeerArrayId>
    <TargetGroups>
    <TargetGroup key="xxx.r12121" syncId="ongoing_syncing-xxx.r12121" />
    </TargetGroups>
    </QuerySyncStatusParameters>

    This issue is fixed in Site Recovery Manager 8.7.0.4.

  • You cannot remove a VM from a Protection Group by using the Site Recovery Manager REST APIs

    If a VM that was on an array-based replicated datastore is removed from the vCenter Server by using the vSphere client UI, the VM is still visible in the Site Recovery Manager protection group with an Invalid status and a message that the VM was removed. If you attempt to use any of the following REST API requests: 'Get Group VM', 'Remove VM From Protection Group', 'Remove VM Protection', 'Get VM Protection Settings', and 'Update VM Protection Settings', the requests fail with an error "Status: 404 Not Found".

    This issue is fixed in Site Recovery Manager 8.7.0.4.

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