Skip to main content

NetApp_Insight_2020.png 

NetApp Knowledgebase

NDB fails to backup by "Unable to get storage details" error when duplicate NFS IP addresses exist accross multiple SVMs

Views:
203
Visibility:
Public
Votes:
0
Category:
netapp-data-broker
Specialty:
snapx
Last Updated:

Applies to

  • NetApp Data Broker (NDB) 1.0.1
  • Duplicate NFS IP addresses exist across multiple storage virtual machine(SVM)s

Issue

  • NDB fails to backup by the following error.

Task 'Discovering Resources' failed with error: Unable to discover resources on SCV: Unable to get storage details for datastore <DATASTORE> with managed object reference <DATASTORE>. Storage system(s) may need to be added, also ensure that the associated host is in a connected state.

  • The message "Unable to get storage details" is shown in vmcontrol_<JOB_ID>.log as a result of SmDiscoverResourcesResponse.

DEBUG <HOST> --- [32374789-550211] c.n.a.m.DatastoreStorageDetailsCache     : Storage footprint not found
ERROR <HOST> --- [32374789-550211] c.n.a.d.VsphereDiscoveryManager          : Unable to get storage details for datastore <DATASTORE> with managed object reference <DATASTORE>. Storage system(s) may need to be added, also ensure that the associated host is in a connected state.
ERROR <HOST> --- [32374789-550211] c.n.a.s.p.DiscoverResourcesManager       : [JobId:<JOBID>] com.netapp.nvpf.api.model.ApiException: Unable to get storage details for datastore <DATASTORE> with managed object reference <DATASTORE>. Storage system(s) may need to be added, also ensure that the associated host is in a connected state.
DEBUG <HOST> --- [32374789-550211] c.n.a.s.p.DiscoverResourcesManager       : <?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<SmDiscoverResourcesResponse>
    <Result>
        <_message>Unable to get storage details for datastore <DATASTORE> with managed object reference <DATASTORE>. Storage system(s) may need to be added, also ensure that the associated host is in a connected state.</_message>
        <_errorCode>-1</_errorCode>
    </Result>
    <TotalCount>0</TotalCount>
    <DisplayCount>0</DisplayCount>
</SmDiscoverResourcesResponse>

  • Job-<JOB_ID>.log indicates that NDB finds wrong SVM information in GatherStorageSystemInfoForNfsExports and executes Get-NcFile against the SVM then "No such file or directory" error is returned.

[INF] Begin GatherStorageSystemInfoForNfsExports
..
[DBG] # of objectGraph:1, StorageSystem: Name : [<SVM>]
..
[INF] End GatherStorageSystemInfoForNfsExports

..

[INF] Begin RunCommand
[DBG] Running Command Get-NcFile controller name : <SVM>, vserver :
[ERR] Failed to run a command Get-NcFile
[DBG] ex.InnerException.Message : No such file or directory
[DBG] PS error string :no such file or directory, Sleeping for: 10000ms
[WRN] retrying the command

..

[DBG] No retry condition match found or max retry reached. Throwing error No such file or directory
[INF] End RunCommand
[INF] Begin CleanUpIfStale
[ERR] No such file or directory

 No such file or directory

[INF] End GetFileInfo
[ERR] Unable to determine file info for the path: <PATH>.
[ERR] Error in GetVolumesOptimized:GatherNfsExportVolumeDetails
Unable to determine file info for the path: <PATH>.
[INF] End GatherNfsExportVolumeDetails
[WRN] BuildNfsSharesToStorageSystemPathsMap: caught exception for vserver '<SVM>', Exception:Error in GetVolumesOptimized:GatherNfsExportVolumeDetails
Unable to determine file info for the path: <PATH>.

 

 

CUSTOMER EXCLUSIVE CONTENT

Registered NetApp customers get unlimited access to our dynamic Knowledge Base.

New authoritative content is published and updated each day by our team of experts.

Current Customer or Partner?

Sign In for unlimited access

New to NetApp?

Learn more about our award-winning Support