Information on your tape doesn't expire until December 4th, so *NO*, do 
not reformat it until then ... the media *may* be OK.

Most tape errors are shown in file 
"/usr/openv/netbackup/db/media/errors".   Whenever I see a new entry 
there (and I have time), I record the event in a journal, including 
related messages in the "All log entries".  I find that almost all media 
(mine are LTO-1) are really OK. 

If I find one of my tapes is involved in an event, I don't wait for 
NetBackup to freeze it, but freeze it manually, asap.  I look at the 
"All log entries" in the Admin Console to see what happened.  If on a 
backup, and it's an important backup ... rerun.  If it's on a 
duplication, rerun the duplication to verify that the backup file is 
OK.  On early MPs of v5.1, I had some files that couldn't be duplicated, 
which made them useless for restore and thus action was needed.

Once a tape has been frozen, I wait for its data to expire.  Once 
expired, it will still be assigned (and frozen), but have no data. The 
Admin Console will show these in the Media Summary report (verbose).   
My procedure is to expire the media with "bpexpdate -d 0 -m mediaid", 
move it to my "maybe this is a bad tape" volume pool, and quick and long 
erase the tape if it hasn't been involved with "too many" other events.

What you do may be vastly different, but correct for your organization!

Cheers, wayne

Krzys wrote, in part,  on 11/22/2006 10:39 AM:
> When I do run ./bpmedialist I see the following entry:
> GK5510   1     39   09/28/2006 23:59  11/20/2006 21:05  hcart3  1106192064    
>  1
>                 15   12/04/2006 21:05  11/16/2006 19:26    FROZEN
>
> Does it mean that this tape is bad? Can I reformat it? Reuse it? Or do I need 
> to 
> replace this frozen tape?
>