Configuring virtual machine replication fails with error "locked by another ongoing operation"

Products

• VMware vSphere ESXi

Issue/Introduction

Symptoms:

• Errors seen in Site Recovery UI at Protected site:
  

  Unable to configure replication for virtual machine '<virtual-machine-name>' because group '<virtual-machine-name>' cannot be created. Another virtual machine '<virtual-machine-name>' that has the same instance UUID ########-####-####-###############' already exists on protection site '<vcenter-FQDN>'.

  Error on remote DR site: Object '########-####-####-###############' is locked by another ongoing operation in vSphere Replication Management Server. Try again

• Following error shows up in Protected Site Recovery UI:
  
  
  
  
• "VM_Name configuration error: Replication 'VM_Name' on the source site has been force-stopped" error seen on the SRM UI.
  
  
• DR Site Recovery UI showing the job stuck in 'Configuring' state:
  
  

Environment

vSphere Replication 8.x

vSphere Replication 9.x

Cause

• Issue is caused due to stale entry of the VM replication at DR Site Recovery UI while no entry is there in Protected Site Recovery UI.
  
  
• This is seen when removal of the VM replication job is not done cleanly and 'Force stop replication(s)' option is used instead of Gracefully stop replication(s).
  
  

Resolution

1. Restart the following services on DR VR Appliance Management to clear-off the stuck replication job:
   
   Login to the VR appliance Management https://VR-IP:5480 > Click on 'Services' tab 
   
   • hms
   • dr-client
   • hbrsrv
     
     
2. Re-launch site Recovery UI.
   Stuck job in 'Configuring' state changes to 'RPO Error'.
   
   
   
3. Select the VM Replication job at DR site Recovery UI > Click on 'Remove' > select option 'Force stop replication(s)'.
   
   
   
4. Add back the replication of the VM.