Protected VM not visible in Recovery Plan under Virtual Machine Tab

Products

• VMware Site Recovery Manager 8.x
• VMware Live Recovery

Issue/Introduction

•  Virtual machine is not appearing in the list of Protected VMs in the Recovery Plan VM tab.
• The CORRECT number of VMs are listed in the Recovery Plan Summary tab, under 'VM Status' >  'VMs ready for Recovery'
  
  
•  SRM vmware-dr.log.
               Detected index collision caused by same vmId part of more than one PGs.

Environment

VMware Site Recovery Manager 8.x
VMware Live Site Recovery 9.x

Cause

If VM has been cloned/copied from another VM, then the uuid.bios and vc.uuid in the vmx config files may be same.

However, if BOTH VMs are then added to an SRM Recovery Plan, this can cause conflict when SRM is parsing the VMs details.

In SRM vmware-dr.log

....... error vmware-dr.. Detected index collision caused by same vmId part of more than one PGs.
--> Existing index: vmId='########-####-####-8c33-############' ownedByLocalSite='1' group='vm-protection-group-##########' pvmRef=protected-vm-######'
--> Collided index: vmId='########-####-####-8c33-############' ownedByLocalSite='0' group='vm-protection-group-##########' pvmRef=protected-vm-######'

 

Tracing the vmId with an SRM DB query on the SRM pdr_vminfo table, returns more than one VM.   Connect to the Site Recovery Manager Appliance Embedded vPostgres Database

   srmdb#  select name, instanceuuid from pdr_vminfo where instanceuuid like '########-####-####-8c33-############';

          name      |                        instanceuuid
  --------------------------+--------------------------------------
  VM_Name_1    | ########-####-####-8c33-############
  VM_Name_2    | ########-####-####-8c33-############

Note the VMs returned.  

Run a uuid search against vmx and compare outputs for conflict uuids

egrep "uuid.bios|vc.uuid"  *vmx

eg:
uuid.bios = "## ## ## ## ## ## ## ##-## ## ## ## ## ## ## e2"
vc.uuid = "## ## ## ## ## ## ## ##-## ## ## ## ## ## ## 60"

Resolution

We can change uuid of any one VM to fix the issue.

1. Power off VM VM_Name_1

2. SSH to the ESX and enter into the VM home folder.

3. Using vi utility edit the uuid.bios and vc.uuid in .vmx file.


For example,

uuid.bios = "## ## ## ## ## ## ## ##-## ## ## ## ## ## ## e2"
vc.uuid    = "## ## ## ## ## ## ## ##-## ## ## ## ## ## ## 60"

Just change the last bit to another value....

uuid.bios = "## ## ## ## ## ## ## ##-## ## ## ## ## ## ## e3"
vc.uuid    = "## ## ## ## ## ## ## ##-## ## ## ## ## ## ## 61"

 

4. Power on the VM.


5. If the VM is not shown in recovery plan automatically, reconfigure the recovery plan or recreate it.