Sometimes, jobs will fail with media read/write errors during the first 
backup attempt, but succeed during subsequent attempts. We set these 
tapes aside when we discover them and it wound up reducing the number of 
backup failures related to media write errors.

I do have a script which will associate each media error with the job 
that was writing to/reading from it. I'm away on business right now, but 
I will try to remember to share this when I get a chance.

Austin Murphy wrote:
> On 5/2/07, Hindle, Greg <Greg.Hindle at constellation.com> wrote:
>   
>> nb 5.0 mp7 Solaris 9
>>
>> does anyone have a script that scans the logs for tapes that are getting
>> read / write errors? I had a bunch of drives go offline the other night and
>> it could be due to a bad tape or tapes and was wondering if anyone had a
>> script that they run to scan for this condition.
>> Thanks
>>     
>
>  cat /usr/openv/netbackup/db/media/errors
>
> Works for me in 5.1MP6, Solaris9.
>
> Austin
> _______________________________________________
> Veritas-bu maillist  -  Veritas-bu at mailman.eng.auburn.edu
> http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
>   


-- 
===================================

   Steven L. Sesar
   Lead Operating Systems Programmer/Analyst
   UNIX Application Services R101
   The MITRE Corporation
   202 Burlington Road - MS K101
   Bedford, MA 01730
   tel: (781) 271-7702
   fax: (781) 271-2600
   mobile: (617) 519-8933
   email: ssesar at mitre.org

=================================== 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: 
http://mailman.eng.auburn.edu/pipermail/veritas-bu/attachments/20070502/f6364737/attachment.html