Live Site Recovery failure on Protection Group showing Not Configured due to duplicate VMs
Article ID: 393283
Updated On:
Products
Issue/Introduction
Protection Group showing Not Configured
VMs inside of protection group appear twice. Once as "OK" and another time with the error, "Virtual Machine 'xxxxx' from protection group 'xxxxx' has no replication info."
"Operation Error: Unable to remove virtual machine 'xxxxx' from protection group 'xxxxxx' because this virtual machine is still configured for protection. Please remove protection for this virtual machine first."
Environment
Live Site Recovery
vSphere Replication
Cause
Live Site Recovery was either in a disconnected state or Powered off when VM's replicated through vSphere Replication were removed from vCenter Inventory. Upon re-adding the VM's into Inventory the vm-id is re-generated. Live Site Recoveries auto-protection feature has added the new vm-id into inventory but the old one was not removed properly causing the error, "this virtual machine is still configured for protection"
Resolution
There are two ways to fix this.
Contact Broadcom support to run the embedded SRM DB tool python script to remove the VMs from the Protection group.
In more extreme cases SRM will need to be unregistered from both Production and Recovery vCenters and then re-registered to wipe the database and deploy as if brand new. If Configuration has been exported previously to this error you can also import the configuration into this setup.
Additional Information
Feedback
