Video Screencast Help

Lotus notes .nsf file getting missed in the daily backups

Created: 15 Sep 2011 • Updated: 20 Sep 2011 | 6 comments
This issue has been solved. See solution.

On daily basis, a particular file is getting missed in LotusNotes Backup. Backup completes with status 1.

Sep 14, 2011 11:43:34 PM - begin writing
Sep 14, 2011 11:56:40 PM - Error bpbrm (pid=13649) from client de01mdapp200-bu: ERR - failure reading file: Lotus Notes:\D:\Lotus\Domino\Data\SARLab\SARTESTPLANNING_TPL.nsf (WIN32 1: Incorrect function. )
Sep 14, 2011 11:57:14 PM - end writing; write time: 0:13:40
the requested operation was partially successful  (1)

Please suggest . This is a very important file for us.

Comments 6 CommentsJump to latest comment

Andy Welburn's picture

NetBackup for Lotus Notes database agent backup finished with Status Code 1; error "WIN32 1: Incorrect function" is seen in the Job Details
http://www.symantec.com/business/support/index?pag...

Not sure how relevant it is you your environment (& the environment "show all" within the T/N itself shows nothing!), but there is a warning:

"There exists a potential danger that disabling the timeout will result in Domino resources being consumed to the extent that the Domino server could crash during the backup."

SOLUTION
Pratique's picture

Well, couldn't really switch to that option as the implications might lead to dreadful outcomes. Can there be anything else?

Pratique's picture

Yep, configuring the Backup timeout setting in notes.ini worked. The backups for the Lotus notes are now completing with status 0.

Thanks

Pratique's picture

The domino server crashed 6 time during the weekend after changes were made to the notes.ini file. A report from the vendor (IBM) looks like this:

Domino is crashing on your backup application.  Here is the fatal stack: 

############################################################ 
### FATAL THREAD 1/3 [bpbkar32:  1650:  1774
### FP=0x0012dbe4, PC=0x7c36ccc1, SP=0x0012db58 
### stkbase=00130000, total stksize=69632, used stksize=9384 
### EAX=0x1cd46000, EBX=0xffff0053, ECX=0x00000030, EDX=0x7fffffff 
### ESI=0x7c37a4d8, EDI=0x00000002, CS=0x0000001b, SS=0x00000023 
### DS=0x00000023, ES=0x00000023, FS=0x0000003b, GS=0x00000000 Flags=0x00010297 
Exception code: c0000005 (ACCESS_VIOLATION) 
############################################################ 
 [ 1] 0x7c36ccc1 MSVCR71.wscanf+979 (153f80,12dc10,12ac,12db68) 

This issue appears to be related to the backup app . I would recommend getting in touch with Symantec support.

Please suggest as we are facing escalations.

Andy Welburn's picture

to solve the "skipped" file have very possibly resulted in the further issues you are now experiencing, per the warning I highlighted earlier

"There exists a potential danger that disabling the timeout will result in Domino resources being consumed to the extent that the Domino server could crash during the backup."

I have no other ideas, that was all I managed to find on the KnowledgeBase.

I would revert the changes you made to prevent your Domino server from crashing & place a support call to try & get a solution for the "skipped" nsf.