Tuesday 15 December 2015

Unable to configure replication for virtual machine VM_name because group group_name cannot be created. Another virtual machine configured_VM_name}' that has the same instance UUID instance_UUID already exists on protection site source_site_name.

Problem


The other site contains old information in the database, and prevents you from configuring  replications. You might see the following error message:

Unable to configure replication for virtual machine VM_name because group group_name cannot be created.
Another virtual machine configured_VM_name}' that has the same instance UUID instance_UUID already exists on protection site source_site_name.

Solution:

1. Login (SSH) Recovery Site vSphere Replication Appliance.

2. Go to cd /opt/vmware/vpostgres/9.3/bin

3. Take backup of DB ./pg_dump -U vrmsdb -Fp -c > /tmp/DBBackup.bak

4. login on DB ./psql -U vrmsdb

5. Open replciation VMs inventory table.
SELECT a.group_movalue AS "SECONDARY GID", b.name AS "VM Name", 'https://' || c.address || ':8043/mob/?moid=' || a.group_movalue || '&vmodl=1' AS "Link to Paste" FROM secondaryvirtualmachineentity a, virtualmachineentity b, localserverentity c WHERE a.movalue = b.movalue ORDER BY name;

6. Search for VM, which is occurring issue and copy Link to Paste URL of that VM (MOB). which will look like 
https://VRMS_IP:8043/mob/?moid=GID-87ae29b2-485f-4fd4-a19b-f5566c87e5
8b&vmodl=1
7. Now open this link in the browser.
8. Click on destroy in this list.
9. And new window click on Invoke Method.
10. Now go ahead and configure replication for that VM.

13 comments:

  1. Thanks a lot man for this great troubleshooting article. It solved my problem :)

    ReplyDelete
  2. Great article. Fixed my problem but you should mention that when logging into the https://VRMS_IP:8043/mob/?moid=GID-87ae29b2-485f-4fd4-a19b-f5566c87e5
    8b&vmodl=1
    The required MOB login credentials for the VRMS server are case sensitive. e.g: domain\user fails but DOMAIN\user succeeds.

    ReplyDelete
  3. Dude, this has saved me twice! Awesome stuff!!

    ReplyDelete
  4. Just an excellent article :)

    ReplyDelete
  5. Thank You!! I Found any wrong query, but, this is correct and resolved my problem

    ReplyDelete
  6. Awesome.. It worked.. Great thanks.. I was successfully able to fix in the live running production environment.. Thanks a bunch..
    -Venugopal

    ReplyDelete
  7. On Clearing the entries it deletes the replicated data too.. so a fresh replication is configured..

    ReplyDelete
  8. What if there is no destroy option in the list?

    ReplyDelete
  9. Worked! Thank you very much!

    ReplyDelete
  10. Worked fine. Thx a lot !!

    ReplyDelete
  11. When I issue the ./psql -U vrmsdb command it ask for a password. any ideas?

    ReplyDelete
    Replies
    1. Is this resolved David Moore

      Delete