Backup from Networker server fails but works from client

Question

Hi,

I'm wondering about the networker functionality. One of my client server backup fails when i run both scheduled and manual backup from server using group. However the manual backup from client works. When we executed the backup it ran and save set (C:\) saved in default. I have tried re-creating the client. But no improvement.

Below is the log from /nsr/logs/daemon.raw file

0 1257537319 2 0 0 4024 4032 0 msqaex07cas2.store.lowes.qa nsrexecd 2 %s 1 0 9 NetWorker
0 1257537319 2 0 0 4024 4032 0 msqaex07cas2.store.lowes.qa nsrexecd 2 %s 1 0 15 7.5.1.Build.269
0 1257537319 2 0 0 4024 4032 0 msqaex07cas2.store.lowes.qa nsrexecd 2 %s 1 0 3 269
0 1257537319 2 0 0 4024 4032 0 msqaex07cas2.store.lowes.qa nsrexecd 2 %s 1 0 24 Fri Mar 20 23:30:27 2009
0 1257537319 2 0 0 4024 4032 0 msqaex07cas2.store.lowes.qa nsrexecd 2 %s 1 0 19 Build arch.: ntx64
0 1257537319 2 0 0 4024 4032 0 msqaex07cas2.store.lowes.qa nsrexecd 2 %s 1 0 10 DBG=0,OPT=

Is there any free tool available to view logs more described? I like to understand what means each numbers represents.

pheikens · Answer

Hi,to view the raw logfiles, use: 'nsr_render_log -mycepta -l /nsr/logs/daemon.raw'Perhaps you'll have tor pipe the output to less: 'nsr_render_log -mycepta -l /nsr/logs/daemon.raw | less'The reason for the failure of group backups may be a missing entry in the servers file of the client.Edit the /nsr/res/servers on the client and put a line with the name of your backup server in there.After that, you must restart the NetWorker service on the client.If that does not work for you, provide us with more infomation.Peter

IKP1 · Answer

Hi,Try creating a single group containing just this client.Then from the NetWorker server command window initiate the group with verbose logging, you may want to redirect the output to make reading easier.For example crate a group called fred containing only this client.Then from the NetWorker server command window 'savegrp -vvv fred'Issue the command without the quotations and the syntax is three v's i.e. very very verbose.This should let you see the error message if any that is being created or what NetWorker is reporting.HtHIKP

ArchuPeri · Answer

FYI all servers owns two separate group on the server name. One is FULL and another one is INCR. And recently i noticed one more thing when backup started from client nsrexecd on the client dies.

ble1 · Answer

If I understood correctly, now both server initiated and client initiated backups have problem, right?  Can you check dr. watson log on that machine?  Does it match your crashes?  Also, what Windows version and NW version do you use?

ArchuPeri · Answer

The problem on our AIX6100-ML4. Initially EMC was telling that is the default security settings on AIX6100-ML4. Later, when we proved this is on Networker we got some patch from EMC that didn't fixed. According to EMC i changed nsrauth and that fixed problem. Our chansing behind AIX6100-ML4 default security configuration almost got fixed. Since yesterday backups are in good state

1) Ensure the daemon is running on server à ps -ef|grep -i nsr à if not, try restarting

2) Execute command à nsradmin -p nsrexec

3) You will get prompt as “nsradmin>”

4) Execute command à print type: nsrla

5) If the authentication method value shows as à auth methods: "0.0.0.0/0,nsrauth/oldauth";

6) Update the authentication method executing command à update auth methods: "0.0.0.0/0,oldauth"

7) Press “y” to accept question “Update?”

8) Ensure the change took effective executing à print type: nsrla

The authentication value should be like à auth methods: "0.0.0.0/0,oldauth";

9) Then “quit”

10) Start the daemon

NetWorker

Backup from Networker server fails but works from client

Was this post helpful?