Veritas-bu

[Veritas-bu] Error(174) - Anyone ever get these errors?

2006-02-06 07:06:49
Subject: [Veritas-bu] Error(174) - Anyone ever get these errors?
From: jpiszcz.backup AT gmail DOT com (Justin Piszcz)
Date: Mon, 6 Feb 2006 07:06:49 -0500
------=_Part_13265_21623715.1139227609737
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

Looking in the NetBackup troubleshooter, it suggests that the tape drives
are not configured correctly.

In the log, I see:

Critical bptm (pid=3D15574) attempted to write 0 gigabytes, 5636182 byte, i=
t
is not a multiple of 512.

Then the backup process exits with status(174).

The troubleshooter mentions if it occurs on a Sequent platform and such--
this does not apply to me, I am trying to backup a Linux filesystem.
Furthermore, in the troubleshooter, it talks about restores for #1 and #2.
On #3 it mentions if the client binaries are correct, especially for bpcd.
What is most likely the culprit?  An incorrectly configured tape drive OR
the client binaries?

Has anyone gotten this error before, if so, how did he or she resolve the
issue?


Try the following:

1.  Check the NetBackup Problems report to see if it shows the cause of the
problem. If you see a Problems report message similar to
  "attempted to write 32767 bytes, not a multiple of 512"
   save all logs and call VERITAS customer support.
2.  On UNIX, if this occurs during a restore, it may be that the tape drive
is incorrectly configured to write in fixed length mode when it should writ=
e
in variable length mode.
   Verify your drive's configuration, comparing it to what is recommended i=
n
the Media Manager Device Configuration Guide (also see step 7 of this
procedure).
   If your configuration incorrectly specifies fixed length mode, change th=
e
configuration to specify variable length mode and suspend media that were
written on that device. The images written to those media may be restorable
(this is platform dependent), but single file restores are almost guarantee=
d
to fail.
3.  If you see the problem with only one client, verify that the client
binaries are correct, especially those for bpcd.
4.  Can you read or write any other images on this media?
   If so, check the following reports for clues:
   *  Images on Media report
   *  Media Contents report
5.  Verify the following:
   *  The media by using the NetBackup image verify option.
   *  That you are using the correct media type for the device.
6.  Check the system or console log for errors (on UNIX) or the Event Viewe=
r
Application log (on Windows).
7.  For detailed debug information, create a debug log directory for either
bptm or bpdm (whichever applies) and retry the operation. Check the
resulting debug log.
   On UNIX systems, if the bptm debug log shows an error similar to
00:58:54 [2304] <16> write_data: write of 32768 bytes
indicated only 29696 bytes were written, errno =3D 0
   it may be that the tape drive is configured to write in fixed length mod=
e
rather than variable length mode, and the image being written encountered
the end-of-media.
   Take the corrective action suggested in step 2.

------=_Part_13265_21623715.1139227609737
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

<div>Looking in the NetBackup troubleshooter, it suggests that the tape dri=
ves are not configured correctly.</div>
<div>&nbsp;</div>
<div>In the log, I see:</div>
<div>&nbsp;</div>
<div>Critical bptm (pid=3D15574) attempted to write 0 gigabytes, 5636182 by=
te, it is not a multiple of 512.</div>
<div>&nbsp;</div>
<div>Then the backup process exits with status(174).</div>
<div>&nbsp;</div>
<div>The troubleshooter mentions if it occurs on a Sequent platform and suc=
h-- this does not apply to me, I am trying to backup a Linux filesystem.&nb=
sp; Furthermore, in the troubleshooter, it talks about restores for #1 and =
#2.&nbsp; On #3 it mentions if the client binaries are correct, especially =
for bpcd.&nbsp; What is most likely the culprit?&nbsp; An incorrectly confi=
gured tape drive OR the client binaries?
</div>
<div>&nbsp;</div>
<div>Has anyone gotten this error before, if so, how did he or she resolve =
the issue?</div>
<div>&nbsp;</div>
<div>
<p>Try the following:</p>
<p>1.&nbsp; Check the NetBackup Problems report to see if it shows the caus=
e of the problem. If you see a Problems report message similar to<br>&nbsp;=
 &quot;attempted to write 32767 bytes, not a multiple of 512&quot;<br>&nbsp=
;&nbsp; save all logs and call VERITAS customer support.
<br>2.&nbsp; On UNIX, if this occurs during a restore, it may be that the t=
ape drive is incorrectly configured to write in fixed length mode when it s=
hould write in variable length mode.<br>&nbsp;&nbsp; Verify your drive's co=
nfiguration, comparing it to what is recommended in the Media Manager Devic=
e Configuration Guide (also see step 7 of this procedure).
<br>&nbsp;&nbsp; If your configuration incorrectly specifies fixed length m=
ode, change the configuration to specify variable length mode and suspend m=
edia that were written on that device. The images written to those media ma=
y be restorable (this is platform dependent), but single file restores are =
almost guaranteed to fail.
<br>3.&nbsp; If you see the problem with only one client, verify that the c=
lient binaries are correct, especially those for bpcd.<br>4.&nbsp; Can you =
read or write any other images on this media?<br>&nbsp;&nbsp; If so, check =
the following reports for clues:
<br>&nbsp;&nbsp; *&nbsp; Images on Media report<br>&nbsp;&nbsp; *&nbsp; Med=
ia Contents report<br>5.&nbsp; Verify the following:<br>&nbsp;&nbsp; *&nbsp=
; The media by using the NetBackup image verify option.<br>&nbsp;&nbsp; *&n=
bsp; That you are using the correct media type for the device.
<br>6.&nbsp; Check the system or console log for errors (on UNIX) or the Ev=
ent Viewer Application log (on Windows).<br>7.&nbsp; For detailed debug inf=
ormation, create a debug log directory for either bptm or bpdm (whichever a=
pplies) and retry the operation. Check the resulting debug log.
<br>&nbsp;&nbsp; On UNIX systems, if the bptm debug log shows an error simi=
lar to<br>00:58:54 [2304] &lt;16&gt; write_data: write of 32768 bytes<br>in=
dicated only 29696 bytes were written, errno =3D 0<br>&nbsp;&nbsp; it may b=
e that the tape drive is configured to write in fixed length mode rather th=
an variable length mode, and the image being written encountered the end-of=
-media.
<br>&nbsp;&nbsp; Take the corrective action suggested in step 2.<br></p></d=
iv>

------=_Part_13265_21623715.1139227609737--

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