[Update: Additional Info added thanks to anonymous feedback]
- In 5.0, this simply is the search/index function in the vSphere Client, previously handled by the Tomcat service. So going through the reset steps outlined here, should cause little to no grief.
- You could attempt the restore steps, but I don't really see a point in doing so in 5.0
- You usually need to go through the reset steps if the client's search begin to slow down and you get "Operation Timed Out Errors"
- This is where it's now important that you have backups because resetting the database effectively wipes out all your entered 'tags' from existence.
Things affected by resetting inventory service database:
o vCenter tags (version 5.1+ only)
o Storage Profiles
o Storage Capabilities
o Index of which VMs have which Storage Profile assigned
This particular service was introduced in vSphere 5.0.
In 5.1 one you are able to separate it from the vCenter server.
It becomes very important to begin backing up the Inventory Service database in 5.1. If you are using Storage Profiles in 5.0, then the Inventory Service is equally important for backups.