
Attachment uploads are currently disabled. This is a temporary situation and will resume as normal in the coming days.
UNSOLVED
DMZ client backup error
Hi,
I am trying to run a manual backup using savegrp for a DMZ client and I get the following error:
client nsrclient01 exited with return code 127
77562:savegrp: job (67437) host: nsrclient01 savepoint: nsrclient01:Probe had SEVERE indication(s) at completion
77569:savegrp: Warning: savefs job (67437) output log file is empty
7341:savegrp: nsrclient01:Probe abandoned.
Now, if I run the savegrp command right after doing the below stunt, probe and backup works fine.
nsradmin -s nsrclient01 -p nsrexecd
NetWorker administration program.
Use the "help" command for help, "visual" for full-screen mode.
nsradmin> q
Help please!
Responses (6)
Solutions (0)
CarlosRojas
1 Rookie
•
1693 Posts
1290
0
Posted November 12th, 2013 06:00
Hi there,
Have you checked the ports? Are port 7937 to 9936 opened?
What is the output of the following commands?:
On NW server:
rpcinfo -p client_name
On Client:
rpcinfo -p NW_SERVER
Also try to run nsradmin -s xxxx -p nsrexecd on server to client and on client to server.
Thank you,
Carlos
Reply CarlosRojas
1 Rookie
•
1693 Posts
1290
0
Posted November 14th, 2013 06:00
Forgot...redirect the output to a file for further analysis.
Thank you,
Carlos
Reply Hi Carlos,
The ports are open from 7937 to 9936. Here are the outputs. Infact, the backup works as soon as I run it after doing 'nsradmin -s client -p nsrexecd' from backup server.
Outout of nsrports -s client:
Service ports: 7937-9936
Connection ports: 0-0
from NW server: rpcinfo -p client
program vers proto port service
100000 2 tcp 7938 rpcbind
100000 2 udp 7938 rpcbind
390436 1 tcp 8737
390435 1 tcp 9216
390113 1 tcp 7937 nsrexec
From client: rpcinfo -p NW_server
program vers proto port
100000 4 tcp 111
100000 3 tcp 111
100000 2 tcp 111
100000 4 udp 111
100000 3 udp 111
100000 2 udp 111
100024 1 udp 32772
100024 1 tcp 32771
100133 1 udp 32772
100133 1 tcp 32771
100021 1 udp 4045
100021 2 udp 4045
100021 3 udp 4045
100021 4 udp 4045
100021 1 tcp 4045
100021 2 tcp 4045
100021 3 tcp 4045
100021 4 tcp 4045
100229 1 tcp 32773
100229 2 tcp 32773
100001 2 udp 32782
100001 3 udp 32782
100001 4 udp 32782
100011 1 udp 32783
100068 2 udp 32784
100068 3 udp 32784
100068 4 udp 32784
100068 5 udp 32784
100083 1 tcp 32774
1073741824 1 tcp 60130
39010411605 tcp 9617
39010414405 tcp 8211
390436 1 tcp 8992
390113 1 tcp 7937
390103 2 tcp 8311
390109 2 tcp 8311
390110 1 tcp 8311
390120 1 tcp 8311
390109 2 udp 9774
390105 5 tcp 8890
390105 6 tcp 8890
390433 1 tcp 8583
390107 5 tcp 8186
390107 6 tcp 8186
39010413605 tcp 8577
39010410705 tcp 9167
390430 1 tcp 8023
390429 101 tcp 8092
I dont see anything that I can catch.
Reply CarlosRojas
1 Rookie
•
1693 Posts
1290
0
Posted November 14th, 2013 06:00
Hi,
Have you tried a manual backup from client?:
save -D3vvv -s NW_SERVER -b pool -N "SAVESET"
where SAVESET would be for example "C:\tmp" for Windows or "/etc/hosts" for Unix.
Thank you,
Carlos
Reply

narohna
8 Posts
1290
0
Posted November 12th, 2013 05:00
Hmm, I dont think so cause it was working fine till the end of last week. Its a windows client.