Article Title: Protection Groups, Recovery Plans, and Mappings are missing after adding a new Site Pair
search cancel

Article Title: Protection Groups, Recovery Plans, and Mappings are missing after adding a new Site Pair

book

Article ID: 435694

calendar_today

Updated On:

Products

VMware Live Recovery

Issue/Introduction

After adding a new site pair in VMware Live Site Recovery, existing inventory objects—including Protection Groups, Recovery Plans, and Folder Mappings—are no longer visible or accessible within the user interface. This can occur when an attempt to expand a single-site pair into a multi-site or Shared Recovery Site configuration.

Environment

 

Product: VMware Live Site Recovery 9.x

Topology: Multi-site or Shared Recovery Site deployments

 

Cause

This issue is caused by an incorrect attempt at a multi-site deployment. Specifically, a new deployment of VMware Live Site Recovery was paired with an existing site that was already part of an active pair, without using the required unique "Service IDs" (formerly known as Site IDs).

When multiple VMware Live Site Recovery instances are pointed at the same vCenter Server or paired incorrectly, the plugin may fail to distinguish between the different instances, causing the UI to hide or fail to load the existing configuration data.

Resolution

To resolve the immediate visibility issue, you must revert the incorrect pairing and clean up the stale registration.

  1. Break the incorrect pairing: Disconnect the newly added site pair that caused the visibility issue.

  2. Clean up the configuration: Follow the steps outlined in KB Article Id 424580 (https://knowledge.broadcom.com/external/article?articleNumber=424580) to remove any orphaned extensions or stale site information from the vCenter Managed Object Browser (MOB).

  3. Validate existing data: Restart the VMware Live Site Recovery services on the original pair to ensure Protection Groups and Recovery Plans reappear.

Correct Multi-Site Configuration: To successfully deploy a multi-site (Shared Recovery Site) topology without impacting existing pairs, you must install multiple instances of the Site Recovery server and assign each a unique Service ID.

Refer to the official documentation for step-by-step instructions: Install Multiple Site Recovery Server Instances on a Shared Recovery Site