you can use the cli also to have better look into the output. If I understand correclty you are using the NW server as storage node to make the backup. We use a dedicated NW storage node (NW SN) for that to prevent having additional load on the NW server. However that also complicated things, as the NW server needs to be able to talk to both the NAS system, the NW SN, and as it will spawn an instance of nsrdsa_save locally on the NW SN, it has to be able to talk to both the NW server and the NAS it needs to backup. We were having issues as the NW server would be having issues communicating correctly with the NW SN that had multiple nics. It had one nic that the NW server could talk to, while another NIC was used for the NW SN to talk to the NAS. That didn't seem to work as the backup process is running on one nic and it needs to be able to talk from NW SN to both the NAS and the NW server on that nic. So in the end we had to get rid of one of those two nics (which simplified the setup anyways), so that only one nic would be used for backup traffic and communication form the NW SN to both the NW server and the NAS.But that doesn't seem to apply here, but as the process is using the wrong IP address, that might be due to how naming resolution is set up and it seems to determine that the 192.168.222.9 is the actual ip address of the NW server? You can check that by for example running nsrwatch, at the top right it will mention behind "Address:" what it's IP address is.   As said with CLI you might be easier able to find out things. Also you might need to use the -J option also, besides -P . Below is picked from KB article 157621 "Networker : ndmp - how to setup Networker ndmp-DSA type backups to move data though a remote storage node":  # nsrndmp_save -D9 -M -T dump -s -P -J -c -l full -b "pool_name" "saveset/name/here" > ndmpsave.out 2>&1 If it would have been a linux system, but based on your network output it seems to be a Windows based backup server, might wanna use nohup or screen or whatever if the backup might be running very long, to detach from the login session... The KB article describes how to use some NSR_DSA options that need to be put into the "Application Information" field of the NAS client. In your case that might be not required as you aren't using a remote NW SN. NSR_DSA_NODE=x.x.x.x NSR_DSA_REC=x.x.x.x NSR_DSA_SAVE=x.x.x.xAlso in the NAS client properties under "server network interface" you would want to put the interface for the NW server, in this case 10.32.18.3
  Hello, Our networker server has 3 NICs, one is normally the primary and two others that we use for Live migrations that aren't routed ( because it is also an hyper-v): Ethernet adapter vEthernet (AT_BRA_Switch): . . . .IPv4 Address. . . . . . . . . . . : 10.32.18.3(Preferred). . . . . .  Ethernet adapter vEthernet (AT_BRA_LM1): .....IPv4 Address. . . . . . . . . . . : 192.168.222.8(Preferred) . . . . . Ethernet adapter vEthernet (AT_LM2): .....IPv4 Address. . . . . . . . . . . : 192.168.222.9(Preferred). . .  NDMP backup fails and I see this line  nsrndmp_save: DAS is listening for an NDMP data connection on 192.168.222.9 port 8787. I specifed "nsrndmp_save -M -P 10.32.18.3 -T dump" but still fails. it only worked when we disabled those two NICs and let only the primary NIC. But it shouldn't stay that way. Is there a way to configure Networker to use that NIC for NDMP backup ?
NDMP backup failed