Unsolved
This post is more than 5 years old
10 Posts
0
4056
Backup errors using NMDA
We are using NMDA for Lotus Notes which is a windows 2003 server. Its unable to backup the "NOTES:_browselist" saveset. We are on networker version 7.6.2.5 and NMDA 1.1. It gives the following error:
1 retry attempted
No full backups of this save set were found in the media database; performing a full backup
Running Domino version Release 8.5.2FP2 March 22, 2011 .
39078:nsrdasv: RPC error: RPC send operation failed. A network connection could not be established with the host.
System error: XBSA-1.0.1 LNMs_2010.Build.231 8252 Tue Nov 29 15:14:33 2011 _nwbsa_close_create_object_session: System detected error due to: savefile_fini() failure, typically caused by bad network hardware (NICs, routers, etc). Operation aborted
Unable to transfer directory index to xdr stream
31257:nsrdasv: Unable to transfer directory index to xdr stream
Child process 8252 returned with failure -256.
82353:nsrdasv: Child process 8252 returned with failure -256.
ble1
14.3K Posts
0
November 30th, 2011 01:00
Is this sporadic error or does it fails always on this saveset only? I believe browselist is usually saved last so there might be 3 possible outcomes:
a) you have some network error indeed (in case that is sporadic)
b) there is a bug (in case it fails always for this saveset)
c) module might use control session which if idle too much is killed by tpctimeout parameter. In that case tweaking keepalive parameter should help (in case it fails always...)
dramjass
151 Posts
0
November 30th, 2011 05:00
In order to determine what really occurred here, you will have to enable NMDA debugging in the configuration file used for the backup. Or, if you created the client via the wizard, these parameters can be added there.
NSR_DEBUG_LEVEL=9
NSR_DPRINTF=TRUE (This parameter will show communication based logging)
The above may generate extraordinarily large logs so you may have to re-direct them to an alternate location using NSR_DIAGNOSTIC_DEST=
There will be n+2 log depending on the parallelism of the client. The 2nd smallest is the parent process responsible for backing up the _browselist.
However, for an easy fix, you may want to ensure the following:
- The Group Inactivity Timeout is set to a value that is larger than the backup window for the client. Therefore, if the group take 6 hours to complete, set the value to something larger than 360.
- Ensure you are using the latest build of NMDA (nsrdasv) which is 304. The RTM release from PowerLink is build 261.
- Ensure there are enough devices for the Domino client to write to.
Keep me posted.
Duncan