Unsolved
This post is more than 5 years old
2 Posts
0
2179
August 2nd, 2012 02:00
Networker Issues backing up Lotus Domino Servers
Over the past few days I seem to be getting the following error:
savegrp: suppressed 2 lines of verbose output
System error: XBSA-1.0.1 LNMs_2010.Build.299 4144 Thu Aug 02 07:57:28 2012 _nwbsa_is_retryable_error: received a retryable network error (Severity 0 Number -13): retry needed
One or more backup streams have failed.
76971:nsrdasv: One or more backup streams have failed.
Child process 5252 (returned pid = 5252) returned with failure -256.
84109:nsrdasv: Child process 5252 (returned pid = 5252) returned with failure -256.
Now the servers that are trying to be backed up are available on the network and can be seen by the networker management server.
Can anyone point me in the right direction?
ble1
6 Operator
•
14.4K Posts
•
56.2K Points
1
August 2nd, 2012 04:00
I would lie if I would say I haven't see this before, but there are so many different causes to this. Most likely in your case, given no other change has been done, is that there is indeed an issue with path from Dominor server to backup server or media server which is causing dropped packages and failed backups. I'm not sure how much I would truct XBSA logs and I would rather check module logs and server side logs for the time when error occured (including system logs just to make sure something else didn't happen at that time).
I recently updated NMDA to version 1.2 which run ok, but I observed few time outs to occur during the same time window once I updated client side NW version. At the moment I do not updated server so I accept the fact that certain things may occur when client version is higher than server one (and in my case that is the case for 90% of landscape) so I won't jump with a gun, but yeah - I have seen it occuring in my env too after NW client has been updated (and funny enough, it occurs during period which is not so busy).
ottov
63 Posts
1
August 2nd, 2012 04:00
Hi
Has anything been changed, I would say in the Network area?
Check the daemon.raw log for rpc errors. this smells of Network problems.
I would also check the NIC settings on the server and the switch port it connects to ensure both are set to FULL dup.
PM011
2 Posts
0
August 2nd, 2012 05:00
Thanks for your advice chaps. I am going to check the zoning and go down that route.