I think it's just the way NetBackup (and "frozen") works.  While we're
quoting, here's a snippet from the v5.1 Commands for Unix manual:

If the date is set to zero, bpexpdate immediately expires backups from the
image catalog or media from the media catalog. When a media ID is removed
from the NetBackup media catalog, it is also deassigned in the Media Manager
volume database, regardless of the media's prior state (FROZEN, SUSPENDED,
and so on).

cheers, wayne

On 9/5/06, Bob Stump <stumpb at michigan.gov> wrote:
>
>  NetBackup 6.0 MP3. I had a frozen tape that I ran
> *bpexpdate -m V01504 -d 0*
> I found the tape was placed into the scratch pool for re-use.
> The question is* why is it acting like a suspended tape instead of a
> frozen tape*?
>
> FROZEN = remains unwritable and in the frozen condition until manually
> unfrozen with bpmedia command
> SUSPENDED = remains unwritable until it expires and then it is
> automatically placed back into the scratch pool for re-use.
>
> *Then*,
> I ran a bpmedialist -summary and noticed an entry for a different tape
> that was frozen and the images expired naturally.
> Number of NON-ACTIVE media that:
>        1 - are currently EXPIRED
>             E00007 expired 09/01/2006 15:09 (FROZEN)
> So is his *just an anomaly for bpexpdate*??
>
>
>
>
>
>
> _______________________________________________
> Veritas-bu maillist  -  Veritas-bu at mailman.eng.auburn.edu
> http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: 
http://mailman.eng.auburn.edu/pipermail/veritas-bu/attachments/20060905/f7b9daa4/attachment.html