Replications are not reflecting after deploying a new vCenter appliance it shows an error "Replication on the source site has been force stopped"

Products

• VMware Live Recovery

Issue/Introduction

Symptoms  :

• Source vCenter server was redeployed to address patching-related issues.

• After deployment, the old source vCenter’s ESXi hosts (including the VR appliance) were migrated.

• Post-migration, all replications from the source site were not visible.

• On the destination site, replications reflected as if the source VMs were force stopped or removed from replication.

Environment

vSphere replication 9.0.2 

Cause

Due to the UUID change after redeployment of the vCenter, existing VRMS registrations became invalid. As a result, replications stopped reflecting at the source site and appeared orphaned at the destination site.

• The vSphere Replication (VR) appliance registers as an extension with a specific vCenter Server instance, and only one VR appliance is supported per vCenter.

• If the vCenter UUID changes, the VRMS (vSphere Replication Management Server) no longer matches the existing registrations.

• VRMS appliance settings (database, certificates, network, credentials) are only valid within the same vCenter instance

Resolution

1. Power off the existing vSphere Replication appliance in the new vCenter.

2. Remove service registrations and solution user of the old vSphere Replication appliance from both Sites 

3. Deploy new vSphere Replication appliances at both DC and DR sites.

4. Break the existing site pair.

5. Create a new site pair with the newly deployed appliances.

6. Reconfigure replications using existing seeds (ensure to note the target datastore of each VM beforehand and validate target datastore seeds as well.