NetWorker: NDMP Troubleshooting Guide

Summary: This article describes where to begin in identifying and troubleshooting NetWorker Data Management Protocol (NDMP) related issues.

This article applies to This article does not apply to This article is not tied to any specific product. Not all product versions are identified in this article.

Instructions

Gather the following information:

Step 1: Basic environment gathering:

About the NetWorker server:
  1. NetWorker server name.
  2. NetWorker version, and build number.
  3. NetWorker server host OS type and version.

See:

 
About the NDMP client:
  1. NDMP client name
  2. NAS filer OS type, and version
  3.  Is the configuration Direct-NDMP (backing up to SAN-attached NDMP tape drives directly from the NAS) or NDMP-DSA (backing up over a TCP/IP connection to a NetWorker server or remote storage node device)?
    1. If NDMP-DSA configuration is the backup device on the NetWorker server or on a NetWorker remote storage node?
    2. If NDMP-DSA configuration what is the backup device type (AFTD, DD Boost, Tape)?

Before troubleshooting any issue, check the NetWorker Compatibility Guide for any support conflicts: E-Lab Interoperability Navigator 2.0-HOME
Review the NetWorker version-specific Network Data Management Protocol User Guide: Support for NetWorker | Manuals & Documents 

NOTE: You must sign in with your Dell support account to access the above resources.

Step 2: Basic problem information:

  1. Is the issue a backup, recovery, or clone related failure?
  2. Is the issue related to performance?
  3. Is the problem persistent or intermittent?
  4. Is the problem occurring with a new NDMP client configuration, or is it an existing environment that was working previously but recently started to fail?
  5. List any recent changes in the environment leading up to the issue first being observed.

Step 3: Output and logs to review:

For backup related issues:
  1. The most useful NDMP backup related errors are found in the backup action log. You can get the backup action log either from the NMC user interface (in the Monitoring window, double-click the failed save set and click "Get Full Log"). Alternately collect the action logs for the workflow folder under /nsr/logs/policy/[policy_name]/[workflow_name]/*.* on the NetWorker server (collect all files and subfolders below the workflow named folder).
  2. To identify the relevant error for a particular failure, look for the first errors logged by 'nsrndmp_save' or 'nsrdsa_save' in the log. Most frequently, the first error is the relevant error and others logged later in the output are symptoms of the failure and not necessarily directly related. For example, the error below is typically logged with most failures, it is logged last, and almost always it is unrelated to the real failure and root cause of the problem:
88394:nsrndmp_save: Couldn't open NDMP file history directory C:\Program Files\EMC NetWorker\nsr\tmp\FileIndex3288118553, The system cannot find the file specified. (Win32 error 0x2)
  1. Review the backup action log output for any error messages, and compare with any known issues in Knowledge Base.

For recovery-related issues:

  1. NDMP recoveries are only logged in the output of the interface used for any particular restore. That includes the NMC Recovery, the NetWorker Windows User (winworkr.exe), and the 'recover' CLI,
  2. The NDMP recovery output is similar in format to that of the backup action log. The processes logging the error in the NDMP recovery output are 'nsrndmp_recover' and 'nsrdsa_recover'. As with the backup logs, look for the first errors logged by 'nsrndmp_recover' or 'nsrdsa_recover' and compare with any known issues in the Knowledge Base.

Step 4:  Additional log and configuration information gathering:

  1. NDMP backup and recovery failures are often caused by client resource or NDMP device configuration issues. Whenever possible, collect the 'nsrdb' resource database from the NetWorker server for review.
  1. NDMP backups can also be run from a terminal or command window on the NetWorker server by running the 'nsrndmp_save' command manually (with or without debug). The output of the command with -D5 debug added can be directed to a file for review using the example command syntax below:
nsrndmp_save -D5 -T dump -c [ndmp_client] -g [group_name] -l [level] [/save_set_name] > ndmpSaveOut.txt 2>&1
  1. NDMP recoveries can also be done manually from a command window on the NetWorker Server by running the 'nsrndmp_recover' command (with or without debug) as in the example that follows:
nsrndmp_recover -D5 -s [nw_server] -c [ndmp_client] -S [ssid] -v off -m [ndmp_client]::[/restore_target_path] [/backup_source_path] > ndmpRecoverOut.txt 2>&1
  1. Use the 'ndmpsup' utility to collect NDMP-specific version and support information from the NAS filer. The utility also serves as a troubleshooting tool because it requires connectivity to the NDMP host and authenticates using the NDMP username and password configured on the NAS. If 'ndmpsup' runs successfully, this confirms that NetWorker can resolve the NDMP client name and connect to it successfully and that the NDMP user credentials are valid. It also confirms that the NDMP service is enabled and running on the NAS. Run 'ndmpsup' from the NetWorker server and collect the utility output using the syntax below:
ndmpsup -c [ndmp_client] -o ndmpsup_out.txt
  1. NAS filer logs following an NDMP backup or restore failure to be collected vary by NAS filer type. The most common NAS filers are Celerra/VNX, Isilon, and NetApp. Collect the NAS logs from these filers as follows:

Celerra/VNX:
Using PuTTY or other SSH client, connect to the VNX Control Station and run the 'server_log' command for the data mover in question (example: server_2). Redirect the log output to a file and use FTP to get the output from the Control Station.

server_log server_2 -a -s > /nas/var/server_log.out

Isilon:
Using a web browser connect to the Isilon OneFS Storage Administration interface and go to the cluster node logs as follows:

OneFs Storage Administrator main view -> Data Protection -> Backup -> Logs (to display logs)

NetApp:
Before collecting the NDMP log (ndmpd.debug) from the NetApp it must first be enabled for logging. For NetApp OnTap version 8.1 and later, connect to the NetApp node in question and enable NDMP logging as follows:

options ndmpd.debug.enable on
options ndmpd.debug.filter all

After ndmpd.debug has been enabled, perform the NDMP backup or recovery from NetWorker. If a failure occurs collect the ndmpd log from the NetApp from the following locations:

7-mode filers: /etc/log/mlog/ndmpd.log
C-mode filers: /mroot/etc/log/mlog/ndmpd.log
 

Additional Information

Examples of typical output from common NDMP backup and recovery failures:


The following output shows a typical NDMP client backup error caused by an incorrect save set name specified in the client resource:
************************************************************************************************
42909:nsrndmp_save: Performing DAR Backup.. 
83563:nsrndmp_save: Performing full backup, BASE_DATE = 0
42794:nsrndmp_save: Performing backup to Non-NDMP type of device
42658:nsrdsa_save: DSA savetime = 1459402009
87976:nsrndmp_save: Checkpoint id 1459402009, backup sequence number 1, backup offset 0, checkpoint interval 104857600 bytes
85183:nsrndmp_save: DSA is listening for an NDMP data connection on: 10.8.67.221, port = 9595
42952:nsrndmp_save: isi-sim-720.plsupport.lab.emc.com:/ifs/data21 NDMP save running on 'oscar'
86724:nsrdsa_save: DSA listening at: host 'oscar', IP address '10.8.67.221', port '9595'.
42958:nsrdsa_save: Performing Immediate save
42619:nsrndmp_save: NDMP Service Error: FILESYSTEM /ifs/data21 is invalid - Unknown error: -1
42738:nsrndmp_save: Data server halted: Error during the backup.
85194:nsrmmd: Chunking ssid 3288118553 failed, because saveset was aborted

85194:nsrmmd: Chunking ssid 3288118553 failed, because saveset was aborted

87170:nsrndmp_save: nsrdsa_save was terminated by signal 22
42950:nsrdsa_save: Save failed
isi-sim-720.plsupport.lab.emc.com: /ifs/data21 level=full, 0 KB 00:00:16      0 file
42913:nsrndmp_save: Save session closed with NW server successfully

nsrndmp_2fh aborted.
88394:nsrndmp_save: Couldn't open NDMP file history directory C:\Program Files\EMC NetWorker\nsr\tmp\FileIndex3288118553, The system cannot find the file specified. (Win32 error 0x2)
Error removing temporary FH index directory: No such file or directory
backup failed.
************************************************************************************************

The following NMC Recover UI output shows a failed directed NDMP recovery caused by an invalid target path specified for the restore:
 
************************************************************************************************
Recovering 1 file from /data3/data3/restore-VAR/data3/users/george/testNotEmpty/ into /data4/george/restore
Total estimated disk space needed for recover is 2 KB.
Requesting 1 file(s), this may take a while...
52949:recover: Performing recover with directories included
03/30/16 23:01:06.573191 NDMP Service Debug: The process id for NDMP service is 0x475c2d40
42795:nsrndmp_recover: Performing recover from Non-NDMP type of device
03/30/16 23:01:06.838828 NDMP Service Debug: The process id for NDMP service is 0x475c2d40
85183:nsrndmp_recover: DSA is listening for an NDMP data connection on: 10.8.67.221, port = 9026
42689:nsrndmp_recover: Performing DAR Recovery..
86724:nsrdsa_recover: DSA listening at: host 'oscar', IP address '10.8.67.221', port '9026'.
91651:nsrdsa_recover: Successfully established AFTD DFA session for recovering save-set ID '3237787234'.
42938:nsrdsa_recover: Performing Direct File Access Restore
42940:nsrdsa_recover: Reading Data...
42619:nsrndmp_recover: NDMP Service Error: Permission denied to restore on Root fs

42617:nsrndmp_recover: NDMP Service Log: server_archive: emctar vol 1, 1 files, 262144 bytes read, 0 bytes written

42738:nsrndmp_recover: Data server halted: Error during the restore.
42856:nsrndmp_recover: NDMP data server has an internal error.
42871:nsrndmp_recover: Error during File NDMP Extraction.
nsrdsa_recover : Aborted
42840:nsrndmp_recover: NDMP recover failed.
42880:nsrndmp_recover: Error during NDMP recover
16279:recover: NDMP retrieval: child failed with status of 1
************************************************************************************************

Affected Products

NetWorker

Products

NetWorker Family
Article Properties
Article Number: 000014177
Article Type: How To
Last Modified: 28 Jan 2026
Version:  8
Find answers to your questions from other Dell users
Support Services
Check if your device is covered by Support Services.