Veritas recommends some OTM settings at the client level. I had the same
issue. If you have an app running on the client that is memory intensive OTM
settings can help.
Here are the registry key settings that I added/modified on our NT clients:

OTM_Cache_Size_Init: 0
OTM_Cache_Size_Max: 0


Added OTM_Error_Control: 1
0 = Abort on error
1 = Disable OTM
2 = Retry OTM

These settings cured our Status 11 problems.

Thanks,

Craig Everett
Intuit Inc,
San Diego Data Center

-----Original Message-----
From: Kate Benson [mailto:KBenson AT outpost DOT com]
Sent: Wednesday, July 12, 2000 10:09 AM
To: 'veritas-bu AT Eng.Auburn DOT EDU'
Subject: [Veritas-bu] Help with NT client returning 11 error!


Hi!
I'm hoping maybe someone out there might be able to offer some advice on
this situation that I are encountering with somewhat frequency in my
environment.

I'm running NetBackup v3.2 on a Solaris Master/Media server and this issue
pertains specifically to various Windows NT 4.0 client.

I have attempted to get an answer in regard to this issue on multiple
occasions with NO LUCK! 

Here is the situation:
The NT client will give all impression of having run a complete backup of
the partition it's attempting to back up.
Here is the info from the "job monitor":
07/10/00 01:37:40 - connecting
07/10/00 01:37:40 - connected; connect time: 000:00:00
07/10/00 01:37:40 - mounting CII229
07/10/00 01:41:10 - mounted; mount time: 000:03:31
07/10/00 01:41:10 - positioning to file 4
07/10/00 01:43:30 - positioned; position time: 000:02:15
07/10/00 01:43:30 - begin writing
07/10/00 02:53:10 - mounting CII206  
07/10/00 02:53:20 - mounting CII270
07/10/00 02:53:10 - mounting CLN494
07/10/00 02:54:30 - mounted; mount time: 000:01:08
07/10/00 02:54:30 - positioning to file 1
07/10/00 02:54:30 - positioned: position time: 000:00:09
07/10/00 02:56:50 - end writing; write time: 001:13:20
(11) system call failed
*******************
If I check the problem report for the client, it returns an error in regard
to the tapes it was mounting being in DOWN drives. ALL drives are and were
in an UP state when this occurred.

This happened after it appears to have completed the backup!  It wrote
12266144 kb of data and has an end time. If there is anyway that someone out
there might be able to help me figure out WHY this is happening?  It has
happened on different clients in our environment. All of them Windows NT 4
w/ SP 5 installed.

Any help or guidance you might be able to offer would be greatly
appreciated.

~Kate Benson

Kate Benson
Network Engineer
Outpost.com
(860) 927-8234
kbenson AT outpost DOT com

"I made some studies, and reality is the leading cause of stress amongst
those in touch with it. I can take it in small doses, but as a lifestyle
I've found it too confining."
        
~Jane Wagner




 



_______________________________________________
Veritas-bu maillist  -  Veritas-bu AT mailman.eng.auburn DOT edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu