Operation Failed. Object '<GID>' is locked by another ongoing operation in vSphere Replication Management Server. Try again later.

Products

• VMware vSphere ESXi

Issue/Introduction

• Attempting to forcefully remove a replication fails with the following error:
  
  
  
  
  
• Replication task appears stuck or unresponsive.
• Disk consolidation status shows as in-progress but not advancing (e.g., 0% done).

Environment

Site Recovery Manager 8.x
Site Recovery Manager 9.x

Cause

• The replication removal operation fails due to a file lock on the VM disk (*.sesparse.vmdk) held in exclusive mode by an ESXi host. This prevents cleanup and consolidation from completing.
• The disk was locked in exclusive mode by an ESXi host, preventing replication cleanup and VM folder deletion.
• Lock was confirmed through VMFS heartbeat and MAC address identification.
  

  [root@xx:/vmfs/volumes/xxxx/VM] vmfsfilelockinfo -p hbrdisk.RDID-xxxx-sesparse.vmdk
  vmfsfilelockinfo Version 2.0
  Looking for lock owners on "hbrdisk.RDID-xxxx-sesparse.vmdk"
  "hbrdisk.RDID-xxxx-sesparse.vmdk" is locked in Exclusive mode by host having mac address ['xx:xx:xx:xx:xx:xx']
  Trying to use information from VMFS Heartbeat

  Host owning the lock on file is x.x.x.x, lockMode : Exclusive
  Total time taken : 4.900337650906295 seconds.

Resolution

1. Reboot the ESXi host that owns the file lock to release the lock.

2. After the reboot:

• Navigate to the vCenter.

• Manually delete the corresponding VM folder from the datastore.

• Remove the VM from replication using the vSphere Replication Management Server (VRMS) interface.

Additional Information

For identifying and resolving VM file locks on ESXi hosts, refer to the KB : Investigating Virtual Machine file locks on ESXi Host(s)