Removing a hung or non-existent vSphere Replication using the VRMS Managed Object Browser (MOB)

Products

• VMware Live Recovery

Issue/Introduction

There may be instances where a replication job is hung, stale or non existent and needs to be cleaned up from the vSphere Replication Appliance Managed Object Browser (MOB)

Environment

vSphere Replication 8.7.x | 8.8.x | 9.0.x

Cause

Replication jobs may be in a hung or non-existent state but still show up I the replication tab of the SRM UI as a running or hung task in vSphere Replication

Resolution

To remove a hung replication task, you must do so from the VRMS MOB and select "destroy" from the MOB menu

 

1. Open a notepad document first so you can edit the string that will be pasted into a browser

2. Paste the following URL into a notepad doc so it can be modified:

    https://vrmsfqdn:8043/mob/?moid=<GID-xxx>&vmodl=1     where <GID-xxx> is the Managed Object GID of the hung job displayed in the replications tab of SRM UI. 

3 Determine the VRMS appliance where the hung replication exists and note the FQDN of the appliance

4. Replace vrmsfqdn with the Fully Qualified Domain Name of the VRMS appliance where the hung replication task resides

5. Replace <GID-xxx> with the GID of the hung/non-existent replication task that is displayed in Site Recovery in the vCenter

    For Example, after making the necessary modifications it may look something like this:

    https://myreplication.example.com:8043/mobmoid/?=GID-b8d4f571-7a48-4ec7-8c20-9634050465c1&vmodl=1

6. Copy the modified version of the URL and paste it into a new browser window

7. When prompted for username, you will login as [email protected] and enter the proper password credientials

8. Go to the bottom section of the MOB screen and click on "destroy" and click on "Invoke Method"

9. You should see a VOID message returned

10. Return to the vcenter and refresh the screen where the hung task was visible. It should now be gone.