Existing Registration Warning when Registering Second VMware Live Site Recovery Appliance
Article ID: 450102
Updated On:
Products
Issue/Introduction
When attempting to register a second On-Premises VMware Live Site Recovery (VLR) / Site Recovery Manager (SRM) appliance to an existing vCenter Server to establish a secondary site pairing, the registration wizard fails with an Existing Registration Warning:
An Existing Registration Warning indicating that another Live Site Recovery instance, <HOSTNAME>, is already registered with the same extension key.
Continuing with the overwrite option warns that it will replace the existing Live Site Recovery registration, resulting in loss of recovery capability, protection groups, recovery plans, inventory mappings, replications, and vSphere Replication site connections for the active site pairing.
Environment
VMware Live Site Recovery 9.0.5.1 and below
Cause
Deploying a second Full VMware Live Recovery appliance to the same vCenter Server causes an extension key collision. vCenter Server enforces a strict limit of one Primary appliance instance registered to the default extension key per vCenter Server instance.
Resolution
RESOLUTION
Deploy a VMware Live Recovery Add-On Appliance rather than a Full (Primary) Virtual Appliance for any additional site pairing beyond the primary instance.
During the Add-On appliance deployment and registration wizard, proceed to the Name and Extension configuration page.
Select Custom extension ID and specify a unique extension identifier string.
Ensure that the target remote Site Recovery instance on the secondary recovery site is configured with the exact same Custom Extension ID string.
Complete the registration wizard to register the Add-On appliance to the protected vCenter Server without impacting or overwriting the existing Primary appliance configuration.
Additional Information
Feedback
