This is a multipart message in MIME format.
--=_alternative 006B1BCA06256D6C_=
Content-Type: text/plain; charset="us-ascii"

Is the block_size on the tape drive you are sending the client backup to 
set to 0 (variable length)? I have found that AIX sets the tape drives 
automatically to 512 if setup using cfgmgr.  I do believe this can cause a 
174 error.

i.e.
/: > mt -f rmt0 status
rmt0 Available 10-70-00-6,0 Other SCSI Tape Drive
attribute      value description user_settable

mode           yes   Use DEVICE BUFFERS during writes          True
block_size     0     BLOCK size (0=variable length)            True
extfm          yes   Use EXTENDED file marks                   True
res_support    no    RESERVE/RELEASE support                   True
var_block_size 0     BLOCK SIZE for variable length support    True
density_set_1  0     DENSITY setting #1                        True
density_set_2  0     DENSITY setting #2                        True
delay          45    Set delay after a FAILED command          True
rwtimeout      144   Set timeout for the READ or WRITE command True
ret_error      no    RETURN error on tape change or reset      True

Lowell






"Daniel, Pam" <Pam.Daniel AT thomsonlearning DOT com>
Sent by: veritas-bu-admin AT mailman.eng.auburn DOT edu
2003-07-23 12:56 PM

 
        To:     <veritas-bu AT mailman.eng.auburn DOT edu>
        cc: 
        Subject:        [Veritas-bu] Media Manager - System Error occurred (174)


Has anyone seen this error when backing up a Redhat Linux 8 client to a 
Aix 4.3.3. running Netbackup datacenter 4.5 FP3?  The status indicates an 
error code of 174 - media manager system error occurred.  When you look in 
the detailed status it has the message, 'Critical bptm (pid=3344) 
attempted to write 0 gigabytes, 32860 bytes, it is not a multiple of 512. 
This is a new setup.
 
 


--=_alternative 006B1BCA06256D6C_=
Content-Type: text/html; charset="us-ascii"


<br><font size=2 face="sans-serif">Is the block_size on the tape drive you are 
sending the client backup to set to 0 (variable length)? I have found that AIX 
sets the tape drives automatically to 512 if setup using cfgmgr. &nbsp;I do 
believe this can cause a 174 error.</font>
<br>
<br><font size=2 face="sans-serif">i.e.</font>
<br><font size=2 face="sans-serif">/: &gt; mt -f rmt0 status</font>
<br><font size=2 face="sans-serif">rmt0 Available 10-70-00-6,0 Other SCSI Tape 
Drive</font>
<br><font size=2 face="sans-serif">attribute &nbsp; &nbsp; &nbsp;value 
description &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; user_settable</font>
<br>
<br><font size=2 face="sans-serif">mode &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; yes 
&nbsp; Use DEVICE BUFFERS during writes &nbsp; &nbsp; &nbsp; &nbsp; 
&nbsp;True</font>
<br><font size=2 face="sans-serif"><b>block_size &nbsp; &nbsp; 0</b> &nbsp; 
&nbsp; BLOCK size (0=variable length) &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 
&nbsp;True</font>
<br><font size=2 face="sans-serif">extfm &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;yes 
&nbsp; Use EXTENDED file marks &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 
&nbsp; &nbsp; True</font>
<br><font size=2 face="sans-serif">res_support &nbsp; &nbsp;no &nbsp; 
&nbsp;RESERVE/RELEASE support &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 
&nbsp; &nbsp; True</font>
<br><font size=2 face="sans-serif">var_block_size 0 &nbsp; &nbsp; BLOCK SIZE 
for variable length support &nbsp; &nbsp;True</font>
<br><font size=2 face="sans-serif">density_set_1 &nbsp;0 &nbsp; &nbsp; DENSITY 
setting #1 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 
&nbsp; &nbsp; &nbsp;True</font>
<br><font size=2 face="sans-serif">density_set_2 &nbsp;0 &nbsp; &nbsp; DENSITY 
setting #2 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 
&nbsp; &nbsp; &nbsp;True</font>
<br><font size=2 face="sans-serif">delay &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;45 
&nbsp; &nbsp;Set delay after a FAILED command &nbsp; &nbsp; &nbsp; &nbsp; 
&nbsp;True</font>
<br><font size=2 face="sans-serif">rwtimeout &nbsp; &nbsp; &nbsp;144 &nbsp; Set 
timeout for the READ or WRITE command True</font>
<br><font size=2 face="sans-serif">ret_error &nbsp; &nbsp; &nbsp;no &nbsp; 
&nbsp;RETURN error on tape change or reset &nbsp; &nbsp; &nbsp;True</font>
<br>
<br><font size=2 face="sans-serif">Lowell</font>
<br>
<br>
<br>
<br>
<br>
<table width=100%>
<tr valign=top>
<td>
<td><font size=1 face="sans-serif"><b>&quot;Daniel, Pam&quot; &lt;Pam.Daniel AT 
thomsonlearning DOT com&gt;</b></font>
<br><font size=1 face="sans-serif">Sent by: veritas-bu-admin AT 
mailman.eng.auburn DOT edu</font>
<p><font size=1 face="sans-serif">2003-07-23 12:56 PM</font>
<br>
<td><font size=1 face="Arial">&nbsp; &nbsp; &nbsp; &nbsp; </font>
<br><font size=1 face="sans-serif">&nbsp; &nbsp; &nbsp; &nbsp; To: &nbsp; 
&nbsp; &nbsp; &nbsp;&lt;veritas-bu AT mailman.eng.auburn DOT edu&gt;</font>
<br><font size=1 face="sans-serif">&nbsp; &nbsp; &nbsp; &nbsp; cc: &nbsp; 
&nbsp; &nbsp; &nbsp;</font>
<br><font size=1 face="sans-serif">&nbsp; &nbsp; &nbsp; &nbsp; Subject: &nbsp; 
&nbsp; &nbsp; &nbsp;[Veritas-bu] Media Manager - System Error occurred 
(174)</font></table>
<br>
<br>
<br><font size=2 face="Arial">Has anyone seen this error when backing up a 
Redhat Linux 8 client to a Aix 4.3.3. running Netbackup datacenter 4.5 FP3? 
&nbsp;The status indicates an error code of 174 - media manager system error 
occurred. &nbsp;When you look in the detailed status it has the message, 
'Critical bptm (pid=3344) attempted to write 0 gigabytes, 32860 bytes, it is 
not a multiple of 512. &nbsp;This is a new setup.</font>
<br><font size=3 face="Times New Roman">&nbsp;</font>
<br><font size=3 face="Times New Roman">&nbsp;</font>
<br>
<br>
--=_alternative 006B1BCA06256D6C_=--