Replications point to legacy IP after Protection and Recovery 9.1 migration

Products

• VMware vSphere ESXi

Issue/Introduction

• Replicated VMs show "Not Active" status after migration to Protection and Recovery 9.1.
• VM replication configuration shows the destination IP address of the legacy (old) vSphere Replication appliance.
• Reconfiguring or creating new replications still points to the old replication broker IP.

Environment

• VMware vSphere Replication 9.0.2.2 or earlier (Legacy)
• VMware Protection and Recovery 9.1 (Converged)

Cause

This issue occurs when attempting a direct convergence/migration from a legacy 9.0.2.2 environment to the 9.1 converged appliance. The direct path may fail to update HMS database entries and service registrations, causing the system to retain legacy IP identities.

Resolution

Fixed in Protection and Recovery 9.1 and higher. For legacy environments (9.0.2.2), a 2-stage upgrade is required. See Download Broadcom products and software for steps to download these releases.

1. Preparation: Revert to the legacy VLR 9.0.2.2 environment.
2. Stale Registration Cleanup: Manually remove stale service registrations from the VMDIR and lookup services on both protected and recovery sites.
3. Stage 1 Upgrade: Upgrade legacy vSphere Replication 9.0.2.2 to the 9.0.4 converged appliance.
4. Verification: Verify that replication resumes and uses the correct 9.0.4 appliance IPs.
5. Stage 2 Upgrade: Upgrade the converged 9.0.4 appliance to Protection and Recovery 9.1.

Subscribe to this article for further updates on automated convergence path improvements.

Additional Information:

• For assistance with manual database cleanup, contact Broadcom Support.
• See Photon Network Manager Commands for updating appliance network details.