NetWorker: How to check if the NetWorker client for Linux is using Client Direct
Summary: Customer would like to check if the NetWorker client for Linux is using the client direct option or not.
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
How to check if the NetWorker client for LINUX is using the client direct option or not.
If Client is using DFA:
The daemon.raw file on the NetWorker server shows the following message:
91787 <time stamp> nsrmmd NSR notice Save-set ID '4091251191' (<nsr_client>:/NetWorker) is using direct file save with Data Domain device 'dd4500.emc.com_<device name>'.
- Linux:
/nsr/logs/daemon.raw - Windows (Default):
C:\Program Files\EMC NetWorker\nsr\logs\daemon.raw - NetWorker: How to use nsr_render_log to render .raw log files
To review connection, run lsof command on the NetWorker client host to list the file information about files opened by processes.
[root@<nsr_client> ~]# lsof -i TCP | grep save save 9831 root 3u IPv4 111668 0t0 TCP <nsr_client>:23178-><nsr_server>:8985 (ESTABLISHED) save 9831 root 5u IPv4 111695 0t0 TCP <nsr_client>:19752-><nsr_server>:9417 (ESTABLISHED) save 9831 root 7u IPv4 111720 0t0 TCP <nsr_client>:31095-><nsr_server>:9035 (ESTABLISHED) save 9831 root 8u IPv4 111728 0t0 TCP <nsr_client>:12421-><nsr_server>:9653 (ESTABLISHED) save 9831 root 9u IPv4 111731 0t0 TCP <nsr_client>:33739->dd4500.emc.com:<dd_device> (ESTABLISHED) save 9831 root 10u IPv4 111736 0t0 TCP <nsr_client>:60278->dd4500.emc.com:<dd_device> (ESTABLISHED)
NOTE: Using below command, that there are open TCP connections from the client both to the NetWorker server and to the DD.
If you must know which processes exactly on the NetWorker server are connected to, you can cross-check with
If you must know which processes exactly on the NetWorker server are connected to, you can cross-check with
lsof on the server. The fourth column is the file descriptor being used. You can include the heading for the lsof output by using egrep like this:
lsof -i TCP | egrep "COMMAND|save"
Run netstat on the NetWorker client to check established connections.
[root@<nsr_client> ~]# netstat -anp | grep save tcp 3116 1437724 <Client IP>:23904 <DD IP>::2049 ESTABLISHED 10019/save tcp 0 0 <Client IP>:19780 <Server IP>::9417 ESTABLISHED 10019/save tcp 0 0 <Client IP>:40129 <Server IP>:9035 ESTABLISHED 10019/save tcp 0 0 <Client IP>:32526 <Server IP>:9653 ESTABLISHED 10019/save tcp 0 0 <Client IP>:50247 <Server IP>:8985 ESTABLISHED 10019/save tcp 0 0 <Client IP>:19438 <DD IP>::3008 ESTABLISHED 10019/save
NOTE: As seen here again that there are open TCP connections to both the Data Domain and the NetWorker server/SN.
To generate output with the headings also, you can use
The
To generate output with the headings also, you can use
egrep like this: netstat -anp | egrep "Proto|save".
The
netstat output has the advantage of also showing the Recv-Q and Send-Q so that we can confirm that there is data being transferred.
If Client is NOT using DFA:
The daemon.raw connects the NetWorker server shows the following message:
91797 <time stamp> nsrmmd NSR severe Unable to perform direct file save with Data Domain device '<DD device>'; setting up traditional save for save-set ID '4024143566' (<nsr_client>:/NetWorker)
NOTE:
If you must find out why it is not using DFA, start with the NetWorker Admin Guide's list of conditions that must be met for DFA to work.
Customers can increase the debug level of the nsrmmd with
The most common reasons would be that the client has no direct network access to the Data Domain from the NIC. It is using or that the version of NetWorker and or Data Domain is not supported versions.
grep for the word "traditional" in the daemon.log gives this output quickly.
If you must find out why it is not using DFA, start with the NetWorker Admin Guide's list of conditions that must be met for DFA to work.
Customers can increase the debug level of the nsrmmd with
dbgcommand -p <nsrmmd_PID> debug=5.
The most common reasons would be that the client has no direct network access to the Data Domain from the NIC. It is using or that the version of NetWorker and or Data Domain is not supported versions.
Affected Products
NetWorkerProducts
NetWorkerArticle Properties
Article Number: 000023593
Article Type: How To
Last Modified: 26 Aug 2025
Version: 5
Find answers to your questions from other Dell users
Support Services
Check if your device is covered by Support Services.