Veritas-bu

[Veritas-bu] (13) file read failure

2002-01-18 12:38:22
Subject: [Veritas-bu] (13) file read failure
From: SJACOBSO AT novell DOT com (Scott Jacobson)
Date: Fri, 18 Jan 2002 10:38:22 -0700
This is a MIME message. If you are reading this text, you may want to 
consider changing to a mail reader or gateway that understands how to 
properly handle MIME multipart messages.

--=_CC91B58D.43226FB3
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit

Yes, David is again probably right.
 
I had this issue and found on our switch log numerous "Vlan Down" and
"Vlan Up" entries.  I our case we disabled flow control and
auto-negotiation (or sense) and duplexing to FULL on our Gig cards and
the problem went away.  It might apply to the client NIC's as well.
 
 
Scott Jacobson
NetBackup Systems Administration
Data Retention and Storage Management
I. S. & T. Provo Operations
sjacobso AT novell DOT com
Desk Direct:   801-861-7668
Toll Free:        800-453-1267 Ext. 1-7668
Cell:                801-560-6891
Novell, Inc., the leading provider of Net services software
www.novell.com

>>> "David A. Chapa" <david AT xbpadm-commands DOT com> 01/18/02 07:16AM >>>
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 


--=_CC91B58D.43226FB3
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=Content-Type content="text/html; charset=iso-8859-1">
<META content="MSHTML 5.50.4807.2300" name=GENERATOR></HEAD>
<BODY style="MARGIN-TOP: 2px; FONT: 8pt MS Sans Serif; MARGIN-LEFT: 2px">
<DIV><FONT size=2>Yes, David is again probably right.</FONT></DIV>
<DIV><FONT size=2></FONT>&nbsp;</DIV>
<DIV><FONT size=2>I had this issue and found on our switch log numerous "Vlan 
Down" and "Vlan Up" entries.&nbsp; I our case we disabled flow control 
and&nbsp;auto-negotiation (or sense) and duplexing to FULL on our Gig cards and 
the problem went away.&nbsp; It might apply to the client NIC's as 
well.</FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV>&nbsp;</DIV>
<DIV>Scott Jacobson<BR>NetBackup Systems Administration<BR>Data Retention and 
Storage Management<BR>I. S. &amp; T. Provo Operations<BR><A 
href="mailto:sjacobso AT novell DOT com">sjacobso AT novell DOT com</A><BR>Desk 
Direct:&nbsp;&nbsp; 801-861-7668<BR>Toll 
Free:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 800-453-1267 Ext. 
1-7668<BR>Cell:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
 
801-560-6891<BR>Novell, Inc., the leading provider of Net services 
software<BR><A 
href="http://www.novell.com";>www.novell.com</A><BR><BR>&gt;&gt;&gt; "David A. 
Chapa" &lt;david AT xbpadm-commands DOT com&gt; 01/18/02 07:16AM 
&gt;&gt;&gt;<BR>Eric:<BR><BR>This may not be the answer you are looking for, 
but 
more than likely it is a<BR>Network problem.&nbsp; Error 13 and 14 with regard 
to NT more commonly are caused<BR>by a connection reset somewhere along the 
way.&nbsp; If you create bpbkar logs on<BR>the client along with bptm logs on 
the media server its backing up to and<BR>bpdbm logs on the Master you should 
be 
able to see where there are network<BR>related issues.<BR><BR>I had this same 
problem with several NT machines at a client site.&nbsp; I got<BR>Veritas 
involved since I was pulled to another project and the result they<BR>came up 
with were several of these connection resets in the 
logs.<BR><BR>David<BR><BR>&lt;&gt;&lt;&gt;&lt;&gt;&lt;&gt;&lt;&gt;&lt;&gt;&lt;&gt;&lt;&gt;&lt;&gt;&lt;&gt;&lt;&gt;&lt;&gt;&lt;&gt;&lt;&gt;&lt;&gt;&lt;&gt;&lt;&gt;&lt;&gt;&lt;&gt;&lt;&gt;<BR>David
 
A. Chapa<BR>NetBackup Consultant<BR>DataStaff, Inc.<BR><A 
href="http://www.consulting.datastaff.com/";>http://www.consulting.datastaff.com</A><BR>847
 
413 1144<BR>---------------------------------------<BR>NBU-LSERV AT datastaff 
DOT com - 
Adv. Scripting<BR><A 
href="http://www.xbpadm-commands.com/";>http://www.xbpadm-commands.com</A><BR><BR>-----Original
 
Message-----<BR>From: veritas-bu-admin AT mailman.eng.auburn DOT edu<BR>[<A 
href="mailto:veritas-bu-admin AT mailman.eng.auburn DOT 
edu]On">mailto:veritas-bu-admin AT mailman.eng.auburn DOT edu]On</A> 
Behalf Of Porter,<BR>Eric<BR>Sent: Friday, January 18, 2002 7:04 AM<BR>To: 
'veritas-bu AT mailman.eng.auburn DOT edu'<BR>Subject: [Veritas-bu] (13) file 
read 
failure<BR><BR><BR>Hi,<BR><BR>Does anyone have some insight into what would be 
causing a "(13) file read<BR>failure"&nbsp; we are seeing this while backing up 
multiple NT servers.&nbsp;&nbsp; We get<BR>this error part way through the 
backup and it 
fails.<BR><BR>Thanks<BR><BR>Eric<BR><BR>_________________________<BR>Eric 
Porter<BR>Technical Services Open Systems<BR>Marriott International<BR>(301) 
696-2782<BR>eric.porter AT marriott DOT com &lt;<A 
href="mailto:eric.porter AT marriott DOT com">mailto:eric.porter AT marriott 
DOT 
com</A>&gt;<BR><BR>_______________________________________________<BR>Veritas-bu
 
maillist&nbsp; -&nbsp; Veritas-bu AT mailman.eng.auburn DOT edu<BR><A 
href="http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu";>http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu</A><BR><BR>_______________________________________________<BR>Veritas-bu
 
maillist&nbsp; -&nbsp; Veritas-bu AT mailman.eng.auburn DOT edu<BR><A 
href="http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu";>http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu</A><BR></DIV></BODY></HTML>

--=_CC91B58D.43226FB3--

<Prev in Thread] Current Thread [Next in Thread>