vSphere Replication 8.5.0.8 | 05 OCT 2023 | Build 22480522 | Download Check for additions and updates to these release notes. |
vSphere Replication 8.5.0.8 | 05 OCT 2023 | Build 22480522 | Download Check for additions and updates to these release notes. |
VMware vSphere Replication 8.5.0.8 is a minor product patch release that provides bug fixes. The content of the VMware vSphere Replication 8.5 Release Notes and all following 8.5.0.x patch release notes applies to this version as well.
The vSphere Replication 8.5.0.8 Express Patch provides bug fixes.
For the supported upgrade paths for vSphere Replication, select Upgrade Path and VMware vSphere Replication in the VMware Product Interoperability Matrices.
You use the ISO file and the VRMS Appliance Management Interface to upgrade from vSphere Replication 8.3.x or 8.4.x to vSphere Replication 8.5.0.x.
If you are running vSphere Replication 8.5, upgrade to vSphere Replication 8.5.0.8. See Upgrading vSphere Replication in the VMware vSphere Replication Administration 8.5 for instructions about upgrading vSphere Replication.
If you use vSphere Replication with Site Recovery Manager 8.5.0.x, upgrade the vSphere Replication appliance to version 8.5.0.8. See the VMware Site Recovery Manager 8.5.0.8 Release Notes for information about VMware Site Recovery Manager 8.5.0.8.
Note: If you are upgrading from vSphere Replication 8.3.x, you must configure a password for the admin account. See Step 12 of the procedure in Upgrade vSphere Replication Appliance.
New - Cannot remove a virtual machine replication operation
When you attempt to remove the replication for a virtual machine, the unconfigure virtual machine replication operation stays at 0% progress.
This issue is resolved in vSphere Replication 8.5.0.8.
New - The vSphere Replication server experiences an unusual restart
The vSphere Replication server experiences an unusual restart and the logs show the following error: Panic: Assert Failed: 'bufLen > 0' @ bora/apps/hbr/hbrsrv/src/BoostVmacoreStream.cpp:574 with values 0 and 0.
This issue is resolved in vSphere Replication 8.5.0.8.