Take a look at the Netbackup Troubleshooting Guide, if you haven't
already.  It explains that error 11 is the catch-all for anything that
doesn't return a known error code.  So, there are a lot of things that
it could be...running out of Virtual Memory, filesystems being full,
semaphore problems, shared memory problems.  The one cause that it
mentions that seemed interesting is for NT clients using Open Transaction
Manager (OTM) for open file management.  It is possible for the OTM
cache file being full to cause an error 11.  You can verify this by
looking at the bpbkar logs on the NT client and searching for lines like:

04/28/99 11:27:56 AM: [216]: ERR - OTM Error:0xe0001005
04/28/99 11:27:59 AM: [216]: INF - OTM Terminate - disabled for all processes
04/28/99 11:27:59 AM: [216]: FTL - Backup operation aborted!

If you still haven't found anything...

The first step is to make sure you're logging as much as possible so
you can track down the problem.

First, put 'VERBOSE = 9' in your bp.conf on your client and server.

Second, make the following directories:
    server: /usr/openv/netbackup/logs/{bpbrm,bpcd,bpdbm,bprd,bptm}
    PC client: C:\VERITAS\NetBackup\Logs\{bpinetd,bpbkar,bpcd,bpmount,tar}
    Unix client: /usr/openv/netbackup/logs/{bpbkar,bpcd,tar}

Then, when you run your backup and it fails, you should be able to
trace which process is the one that actually failed.  Most of the time,
it seems to be that one process will fail, and return an error code to
it's parent process, and going through about 3 or 4 process before it
gets to the activity logs.

Depending on how many files you are backing up, one suggestion I'd make
is to make sure you have the latest Jumbo Patch.  It includes a bugfix
for the issue where NetBackup can't create .f files greater than 2GB.
I belive two Jumbo Patches ago is when the fix was finally incorportated.
This would be on the server.

Other than that, I'd say dive into all of the logs and go from there.
Sometimes it takes a lot of digging, but the logs can be rather verbose,
so you should be able to find the problem.

Oh, and make sure you have enough space for the logs...they can get
rather big.

Good luck.

Todd

On Wed, Jul 12, 2000 at 01:08:57PM -0400, Kate Benson wrote:
> 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