Error: Unsupported vSphere Replication 6.1 version during VMware Live Recovery 9.0.5 convergence

Products

• VMware Live Recovery

Issue/Introduction

Symptoms

• When upgrading or converging from VMware Live Recovery (VLR) 9.0.2 to 9.0.5, the deployment wizard in Step 2 displays an older, unsupported version of vSphere Replication (e.g., version 6.1).
• The identified 6.1 appliance does not exist in the current environment.
• The convergence process cannot proceed due to the presence of these 'ghost' registrations.

Environment

• VMware Live Recovery 9.0.5
• vCenter Server

Cause

Stale service registrations and service principal entries from a decommissioned vSphere Replication 6.1 deployment remain in the vCenter LDAP database. The VLR 9.0.5 convergence workflow proactively validates all registered replication services and is blocked by the legacy metadata.

Resolution

Manually remove the stale legacy entries from the vCenter LDAP using an LDAP browser such as Jexplorer.

⚠️ IMPORTANT: Always take a powered-off snapshot of the vCenter Server Appliance before modifying the LDAP database.

1. Remove Stale Service Registrations

1. Connect to the vCenter LDAP using Jexplorer.
2. Navigate to the following path: vSphere > Configuration > Sites > [Your_Site] > LookupService > Service Registrations
3. In the Table Editor on the right, search for any entries containing:
   • com.vmware.dr
   • dr.
4. Identify the entries corresponding to the stale 6.1 version and delete them.

2. Clean Up Service Principals

1. Navigate to: vSphere > ServicePrincipals
2. Locate the entries that match the service IDs or product strings (e.g., com.vmware, h5-dr) identified in the previous step.
3. Delete the matching service principal entries for the stale version.

3. Verify and Converge

1. Restart the vCenter lookupsvc or restart all services if the entries persist in the UI.
2. Relaunch the VMware Live Recovery 9.0.5 convergence wizard.
3. The stale 6.1 version should no longer appear in Step 2, allowing you to proceed with the upgrade.

If the issue persists, contact a customer representative. See Contact Broadcom Support.