Unsolved

This post is more than 5 years old

585

October 7th, 2008 02:00

NML aborts for different databases

Hallo,

we use NML 3.0.1 with latest hotfix. Backup aborts for databases. It is random which database aborts the backup. Notes server is linux, backup server is
W2k3. Networker client and server is 7.2.2 with jumbo patch. NSR_SKIPDBERRORS=TRUE does not apply since it is a critical error. Unfortunately no debug is generated. Has anybody some suggestion to solve
this problem?

regards
Bernd

2 Intern

 • 

2K Posts

October 7th, 2008 04:00

How are you generating those debugs. Try your cfg file NSR_DEBUG_LEVEL & NSR_DEBUG_FILE parameters and run atleast a debug level 3 backup. Post the result here, we might be able to help.

Mostly debug level 3 generates sufficient errors and should be suitable to begin with.

6 Operator

 • 

14.4K Posts

 • 

56.2K Points

October 7th, 2008 14:00

Are there any network issue (check netstat stats). One thing I would try would be to install demo server on Notes box and have backup without network involved - just to rule out network as an issue.

However, if these aborts are caused out of blue without any ROC errors then I would focus on Domino side and have Domino running in debug (which Domino admin won't like for sure). If you see aborted message given to module it means Notes API has returned that.

October 9th, 2008 03:00

In the config file we specified NSR_DEBUG_LEVEL=5 and NSR_DEBUG_FILE
but not debug was generated.

regards
Berd

2 Intern

 • 

2K Posts

October 9th, 2008 09:00

You need to tell the file name Sir. Check this:

NSR_DEBUG_LEVEL = 3
NSR_DEBUG_FILE = "C:\bkp_log.txt"

This will generate c:\bkp_log.txt on the client.

0 events found

No Events found!

Top