Problem
The other site contains old information in the database, and prevents you from configuring replications. You might see the following error message:
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;
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
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.
Thanks a lot man for this great troubleshooting article. It solved my problem :)
ReplyDeleteThank you.
ReplyDeleteGreat 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
ReplyDelete8b&vmodl=1
The required MOB login credentials for the VRMS server are case sensitive. e.g: domain\user fails but DOMAIN\user succeeds.
Dude, this has saved me twice! Awesome stuff!!
ReplyDeleteJust an excellent article :)
ReplyDeleteThank You!! I Found any wrong query, but, this is correct and resolved my problem
ReplyDeleteAwesome.. It worked.. Great thanks.. I was successfully able to fix in the live running production environment.. Thanks a bunch..
ReplyDelete-Venugopal
On Clearing the entries it deletes the replicated data too.. so a fresh replication is configured..
ReplyDeleteWhat if there is no destroy option in the list?
ReplyDeleteWorked! Thank you very much!
ReplyDeleteWorked fine. Thx a lot !!
ReplyDeleteWhen I issue the ./psql -U vrmsdb command it ask for a password. any ideas?
ReplyDeleteIs this resolved David Moore
Delete