Clean Removal of vSphere Data Protection

There is lots of information available out in the web and blogsphere about how to deploy, configure and manage VMware’s new vSphere Data Protection (VDP) appliance. All well and good if you’re just starting out on your journey with VDP, but what if you’ve got a corrupted or failed instance that cannot be rolled-back and needs re-deploying? Usually, just removing the failed VDP instance from the vSphere Inventory is sufficient to remove the failed instance, but this doesn’t always work (i.e. the instance is still registered in vSphere Web Client so still has hooks into the system somewhere.

I’ve found a good way to cleanly remove a corrupted appliance, this is the process I followed:

  1. (Assuming your appliance is running) – power-off the guest OS and shutdown the appliance.
  2. Remove from Inventory and delete the appliance.
  3. Switch to vSphere Object Browser (‘https://<vc-ip>/mob’).
  4. Login with vCenter credentials.
  5. Select Content > ExtensionManager.
  6. Search for extension with name: ‘com.vmware.vdp’ (or similar name). Note the name down.
  7. Click UnregisterExtension method, and enter the extension name noted above.
  8. Click Invoke method.
  9. Log-out and close vCenter Object Browser.
  10. On your vCenter server, restart the vSphere Web Client service.

Once this process is completed, you should no longer see the VDP extension lingering in your vCenter instance – you can now proceed to a clean installation of a new VDP instance.

Jeremy loves all things technology! Has been in IT for years, loves Macs (but doesn't preach to others about their virtues), loves virtualization (and does shout about it's virtues), and sometimes skis, bikes and directs amateur plays!


  1. Yasir says

    If I have two VDP appliances in my setup and I only need to remove one of them, is there a way to do that?
    Thank you.

  2. tat says

    What can I do when after these steps I have got the error in vSphere Web Client:


    An internal error has occurred – Error #1009.

    Reloading the client is recommended, so as to clear any problems left by this error.

    Click Yes to reload the vSphere Web Client?”

Leave a Reply

Your email address will not be published. Required fields are marked *