Knowledge Base

The VMware Knowledge Base provides support solutions, error messages and troubleshooting guides
Search the VMware Knowledge Base (KB)   View by Article ID

VMware vSphere Data Protection 5.1.x fails to start backup jobs (2037003)


  • vSphere Data Protection (VDP) deploys and configures successfully, but fails to start backup jobs
  • You do not see any errors
  • Agent logs indicate that no jobs are being picked up
  • In the mcserver.log file, located at /usr/local/avamar/var/mc/server_log/, you see the error: WARNING: No hosts found for datastore null

  • In the vdrserver.log file, located at /usr/local/avamar/var/vdr/server_logs/, you see errors similar to:

    INFO [Timer_general]-service.ServiceInstance: ServiceInstanceMoref desc=Service Id: urn:uuid:F50C98B481FF3D6F231360520789100 name=ur n:uuid:F50C98B481FF3D6F231360520789100 value=SERVICE
    ERROR [Timer_general]-schedule.DatastoreHandler: com.emc.vdr.schedule.DatastoreHandler.unable to fill datastores to proxies: java.lang.NullPointerException at java.util.Arrays$ArrayList.<init>(Unknown Source) at java.util.Arrays.asList(Unknown Source) at com.emc.avamar.mcsdk.adapter.model.VmwareDataStore.dump( at com.emc.avamar.mcsdk.adapter.service.ManagedEntityAuxiliary.toString( at java.lang.String.valueOf(Unknown Source) at java.lang.StringBuilder.append(Unknown Source) at java.util.AbstractCollection.toString(Unknown Source) at java.lang.String.valueOf(Unknown Source) at java.lang.StringBuilder.append(Unknown Source) at com.emc.vdr.schedule.DatastoreHandler.fillProxiesWithDatastores( at at java.util.TimerThread.mainLoop(Unknown Source) at Source)


This issue occurs if there are datastores listed in vCenter Server that are not associated with any hosts. In this case, VDP does not display the devices when vCenter Server is queried for datastore information. Datastore entries which are not associated with a host can be listed in vCenter Server for several reasons, including CD/ROM mappings to datastores that are no longer present, templates registered to old locations that are no longer valid, or virtual machines that are registered to datastores that no longer exist.

To test the query, run this command from the VDP command line:

echo "select * from proxy_datastore_mapping" | psql mcdb -p 5555 -U admin

This command should result in approximately 8 entries for each datastore reported by vCenter Server. Failure to display this expected result indicates that there is a datastore with no associated host.


 To verify and ensure that all datastores have associated hosts in vCenter Server:

  1. Log in to vCenter Server using the vSphere Client.
  2. In the Home view, click the Datastores and Datastore Clusters icon.
  3. Expand vCenter Server > Datacenter to list datastores. 
  4. Select a datastore and then click the Hosts tab in the right pane. You see a list of hosts associated with that datastore.
  5. If no hosts are listed on any datastore, click the Virtual Machine tab and locate the virtual machines that are associated with the datastore.
  6. Unmap any unused CD/ROM mappings or remove the invalid virtual machines or templates from the vCenter Server inventory. 

    When all objects are removed, the datastore should no longer appear in the datastore view.

  7. Repeat Steps 4 to 6 for all datastores, as required.

    VDP should now be able to get valid host associations for all datastores and should schedule and run jobs normally.

Note: Ensure to check all datastores from all datacenters in vCenter Server.

Update History

02/07/2013 - Added the location of MCS log file

Request a Product Feature

To request a new product feature or to provide feedback on a VMware product, please visit the Request a Product Feature page.


  • 20 Ratings

Did this article help you?
This article resolved my issue.
This article did not resolve my issue.
This article helped but additional information was required to resolve my issue.
What can we do to improve this information? (4000 or fewer characters)
  • 20 Ratings