Veritas-bu

[Veritas-bu] Exit status 13/14 and TCP error 10053 and 10054

2002-04-19 11:03:46
Subject: [Veritas-bu] Exit status 13/14 and TCP error 10053 and 10054
From: david AT xbpadm-commands DOT com (David A. Chapa)
Date: Fri, 19 Apr 2002 10:03:46 -0500
Here's a response I posted back in January regarding this topic to Eric
Porter who posted the question.

I hope this helps your troubleshooting.

Here's the links to some of the other comments on this subject
http://mailman.eng.auburn.edu/pipermail/veritas-bu/2002-January/007463.html
http://mailman.eng.auburn.edu/pipermail/veritas-bu/2002-January/007659.html
http://mailman.eng.auburn.edu/pipermail/veritas-bu/2002-February/007956.html

David

-----Original Message-----
From: veritas-bu-admin AT mailman.eng.auburn DOT edu
[mailto:veritas-bu-admin AT mailman.eng.auburn DOT edu]On Behalf Of David A.
Chapa
Sent: Friday, January 18, 2002 8:16 AM
To: Porter, Eric; veritas-bu AT mailman.eng.auburn DOT edu
Subject: RE: [Veritas-bu] (13) file read failure


Eric:

This may not be the answer you are looking for, but more than likely it is a
Network problem.  Error 13 and 14 with regard to NT more commonly are caused
by a connection reset somewhere along the way.  If you create bpbkar logs on
the client along with bptm logs on the media server its backing up to and
bpdbm logs on the Master you should be able to see where there are network
related issues.

I had this same problem with several NT machines at a client site.  I got
Veritas involved since I was pulled to another project and the result they
came up with were several of these connection resets in the logs.

David

<><><><><><><><><><><><><><><><><><><><>
David A. Chapa
NetBackup Consultant
DataStaff, Inc.
http://www.consulting.datastaff.com
847 413 1144
---------------------------------------
NBU-LSERV AT datastaff DOT com - Adv. Scripting
http://www.xbpadm-commands.com

-----Original Message-----
From: veritas-bu-admin AT mailman.eng.auburn DOT edu
[mailto:veritas-bu-admin AT mailman.eng.auburn DOT edu]On Behalf Of Porter,
Eric
Sent: Friday, January 18, 2002 7:04 AM
To: 'veritas-bu AT mailman.eng.auburn DOT edu'
Subject: [Veritas-bu] (13) file read failure


Hi,

Does anyone have some insight into what would be causing a "(13) file read
failure"  we are seeing this while backing up multiple NT servers.   We get
this error part way through the backup and it fails.

Thanks

Eric

_________________________
Eric Porter
Technical Services Open Systems
Marriott International
(301) 696-2782
eric.porter AT marriott DOT com <mailto:eric.porter AT marriott DOT com>

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

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

<><><><><><><><><><><><><><><><><><><><>
David A. Chapa
NetBackup Consultant
DataStaff, Inc.
http://www.consulting.datastaff.com
847 413 1144
---------------------------------------
NBU-LSERV AT datastaff DOT com - Adv. Scripting
http://www.xbpadm-commands.com

-----Original Message-----
From: veritas-bu-admin AT mailman.eng.auburn DOT edu
[mailto:veritas-bu-admin AT mailman.eng.auburn DOT edu]On Behalf Of Ballowe,
Charles
Sent: Thursday, April 18, 2002 11:27 AM
To: 'David Hassler'; veritas-bu AT mailman.eng.auburn DOT edu
Subject: RE: [Veritas-bu] Exit status 13/14 and TCP error 10053 and
10054


turn on loging of bpbrm (Backup and Recovery Manager) for more details
on why things are dying. I'm running into the status 13 stuff with
a Win2K environment here and that is where things lead me. I haven't
solved the problem yet - the most telling message in the error logs is
something about OTM not being enabled. I'm don't have admin on that
lab network so I'm waiting for somebody with admin to ship the logs to
me so I can take a closer look.

-Charlie

> -----Original Message-----
> From: David Hassler [mailto:dhassler AT dhassler DOT com]
> Sent: Wednesday, April 17, 2002 4:45 PM
> To: veritas-bu AT mailman.eng.auburn DOT edu
> Subject: [Veritas-bu] Exit status 13/14 and TCP error 10053 and 10054
>
>
> Greetings,
>
> I've got a few troublesome clients that keep exiting either with
> status code 13 or 14.  They are Win2K clients with SP2, running
> NBU Datacenter 3.4, with Solaris 8 master and media servers.
>
> There are a large number of TCP 10053 and 10054 errors in the
> bpbkar logs, and I can't find the reason why.  There are several
> other clients on the TAN that experience the same errors, but on
> a much more random basis.  There are quite a few hosts that
> work fine on a consistent bases (the Unix ones *cough cough*).
>
> I've done the following:
>   - Verified that the interfaces and switch are running at 1000Mb
>     full duplex, auto-negotiate off
>   - Disabled OTM, enabled OTM, adjusted OTM cache parameters
>   - Turned off the archive bit setting
>   - Checked for client-side apps that could interfere, such as
>     Norton AV
>
> Veritas support says that it's a Microsoft issue that should be
> taken up with them.
>
> Does anybody have some insight into what might be causing these
> errors?  I'm approaching insanity trying to figure this out...
>
> Thanks,
> David
>
>
> --
> David Hassler
> dhassler AT dhassler DOT com
> http://dhassler.com
> "Why am I in this handbasket?"
> _______________________________________________
> Veritas-bu maillist  -  Veritas-bu AT mailman.eng.auburn DOT edu
> http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
>
_______________________________________________
Veritas-bu maillist  -  Veritas-bu AT mailman.eng.auburn DOT edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu