[Veritas-bu] Media Write Error Problem

This is a multi-part message in MIME format.

------_=_NextPart_001_01C439FE.055E91E9
Content-Type: text/plain;
        charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

In our Windows environment (Win2k Master and media servers running NBU
5.0GA) we occasionally get jobs that fail with media write errors. The
problem is they are setup to retry. When they run the second time, they
try to use the same media id as the first run. This causes the whole job
to fail because that media is still bad. Is there a way in NetBackup to
force the retry job to go to a different tape? It seems pretty dumb to
retry a job that ended with a media write error to the same bad tape a
second time. Anyone have any ideas?

=20

=20

Thanks!

=20

Kris


------_=_NextPart_001_01C439FE.055E91E9
Content-Type: text/html;
        charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html>

<head>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Dus-ascii">


<meta name=3DGenerator content=3D"Microsoft Word 10 (filtered)">

<style>
<!--
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
        {margin:0in;
        margin-bottom:.0001pt;
        font-size:12.0pt;
        font-family:"Times New Roman";}
a:link, span.MsoHyperlink
        {color:blue;
        text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
        {color:purple;
        text-decoration:underline;}
p
        {margin-right:0in;
        margin-left:0in;
        font-size:12.0pt;
        font-family:"Times New Roman";}
span.EmailStyle17
        {font-family:Arial;
        color:windowtext;}
span.EmailStyle18
        {font-family:Arial;
        color:navy;}
@page Section1
        {size:8.5in 11.0in;
        margin:1.0in 1.25in 1.0in 1.25in;}
div.Section1
        {page:Section1;}
-->
</style>

</head>

<body lang=3DEN-US link=3Dblue vlink=3Dpurple>

<div class=3DSection1>

<p class=3DMsoNormal><font size=3D3 color=3Dnavy face=3D"Times New =
Roman"><span
style=3D'font-size:12.0pt;color:navy'>In our Windows environment (Win2k =
Master
and media servers running NBU 5.0GA) we occasionally get jobs that fail =
with
media write errors. The problem is they are setup to retry. When they =
run the
second time, they try to use the same media id as the first run. This =
causes
the whole job to fail because that media is still bad. Is there a way in
NetBackup to force the retry job to go to a different tape? It seems =
pretty
dumb to retry a job that ended with a media write error to the same bad =
tape a
second time. Anyone have any ideas?</span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>&nbsp;</span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>&nbsp;</span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>Thanks!</span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>&nbsp;</span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>Kris</span></font></p>

</div>

</body>

</html>

------_=_NextPart_001_01C439FE.055E91E9--