How to troubleshoot the Datastore (VMWare) service

Last Modified

Mon Jun 08 09:39 GMT 2020

Description

  • This article provides some information regarding the Datastore (VMWare) service, and possible issues.

Environment

  • N-able N-central
  • ESXi 4.5 and later

Solution

  • The datastore service is mainly a Web Service request, meaning that it pulls its data over port 443 rather than the normal 5989
    • NOTE: Port 5989 is required for the initial discovery job.
  • Because of this you can validate most of the datastore service information from the managed object browser (mob) link.
  • To see this data we start by navigating to the mob link of the ESXi device from the probe that is monitoring it.

    • https://IP_FQDN_ESXi_HOST/mob/?moid/?moid=ha-folder-datastore

  • This link will provide a list of the datastores on the host. Depending on the version of ESXi it may provide a friendly name.
  • Once you have the list just click on one of the links, and there will be a provided name section saying which datastore it is.
  • From here you can click on the properties summary, and it will provide data like capacity and freeSpace.
  • More information on this service can be found here:
  • One example of an issue is that the freeSpace may become out sync, and so the service shows what is reported in the MOB link, but not what is in vSphere.
  • To correct this, please do the following:
    1. Click on the datastore with the problem from the image above
    2. Select the RefreshDatastoreStorageInfo method
    3. Select Invoke Method
  • For more information on this, please see the VMWare documentation below: