You cannot configure a replication because another virtual machine already exists at the target site.

Problem

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.

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 or reset its database on one of the sites, the other site contains information about the old appliance and database, and prevents you from configuring new replications.

Procedure

  • If you have not reinstalled the vSphere Replication Management server, an orphaned replication exists in your environment, and you know the GID value of that replication, use the Managed Object Browser (MOB) of the vSphere Replication Management server to delete the replication.
    1. Navigate to https://vrms_address:8043/mob/?moid=GID-orphaned_replication_GID&vmodl=1

      Where vrms_address is the IP address of the vSphere Replication Management server.

    2. Invoke the destroy method to remove the replication from the site on which the vSphere Replication Management server runs.
  • If you have not reinstalled the vSphere Replication Management server and orphaned replication exists in your environment, but you do not know the GID value of that replication, the value can be retrieved from the log files or the vSphere Replication Management server database. Contact VMware Global Support Services for assistance.
  • 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.