Operational Defect Database
BugZero updated this defect 43 days ago.
Data sources
All data on this page is proprietary to BugZero® or gathered from public sources
VMware | 91724
Configuring Replication Fails Because Another Virtual Machine Has the Same Instance UUID
Last update date:
4/6/2024
Affected products:
vSphere Replication
Affected releases:
8.x
Fixed releases:
No fixed releases provided.
Description:
Symptoms
1. You cannot configure a replication because another virtual machine already exists at the target site. ERROROperation FailedUnable to configure replication for virtual machine 'virtual machine' because group 'virtual machine' cannot be created. Another virtual machine 'virtual machine' that has the same instance UUID '50206a21-d177-e2ea-7085-c950815fd0b2' already exists on protection site '(Protected Site)'.Operation ID: c4eb75b7-ee33-4086-a385-3ba2553c5ea6
Purpose
This is to clear the stale replication entries in the vSphere replication servers which can happen when trying to remove the replications and re-add.
Cause
This error message might appear on the following occasions. If, due to a connectivity issue or some other problem, an orphaned replication remains on one of the sites while it is deleted from the other site, the orphaned replication prevents you from configuring a new replication for the same virtual machine. If you have paired two sites and reinstall the vSphere Replication Management server appliance, the other site contains information about the old appliance and database, and prevents you from configuring new replications.
Impact / Risks
VM replications cannot be configured.
Resolution
If you have not reinstalled the vSphere Replication Management server, an orphaned replication exists in your environment. You can force stop this replication to delete it. 1. Log in to the vSphere Client. 2. On the home page, click Site Recovery and click Open Site Recovery. 3. On the Site Recovery home page, select the site pair which contains the protected site, mentioned in the error message that you received. 4. Click the Replications tab and select a replication from Outgoing or Incoming. 5. Click the Remove icon and select Force stop replication(s). Alternatively, you can use the Managed Object Browser (MOB) of the vSphere Replication Management server to delete the replication. Configuring Replication Fails Because Another Virtual Machine Has the Same Instance UUID 1. Navigate to https://vrms_address:8043/mob/?vmodl=1 a. Where vrms_address is the IP address of the vSphere Replication Management server. 2. Click the content value. 3. Select the replicaManager or replicationManager value, depending on the type of replication you want to delete. i. For an outgoing replication, click replication-manager > getOutgoingReplications. ii. For an incoming replication, click replica-manager > getIncomingReplications. Set the relevant start, count, sorters, and filter values. NOTE:You must set the start value to 0 and delete the sorters and filter values, to invoke the first page of maximum 50 listed replications. For more than 50 replications, you can use paging and make additional calls for the next pages of replications or use the sorters and filter values. 4. Click Invoke Method. 5. Locate the replication and click the GID link under replication value. 6. Invoke the destroy method to remove the replication. If the vSphere Replication Management server on one of the sites was reinstalled or otherwise reset: 1. Reinstall the vSphere Replication Management server at the other site or reset its database. 2. Connect the sites and register any additional vSphere Replication server appliances. 3. Remove any temporary hbr* files left over from the target datastore folders. 4. Configure all replications, reusing the existing replica .vmdk files as replication seeds.
Related Information
FAQ: Site Recovery Manager & vSphere Replication Redeployment Guidelines (97140)
