Hello Taylor-

The vault reports rely on both the "volume database" and the "media 
database" when reporting media information.  The information missing 
from your report snippet below comes out of the media database in 
particular.

What happens if you run a "bpmedialist -l | grep LL0137"?  I suspect 
you won't get any output at all, which is not normal for an assigned 
NetBackup tape that's not dedicated for use as a catalog backup tape.  
Similarly, I suspect that if you run the "available_media" command, it 
will report a status of "DBBACKUP" for this tape.

If my suspicions turn out to be accurate, then what you're seeing isn't 
a vault issue per se, but a media database issue.  In which case I'd 
suggest you call VRTS support to get some help figuring out why you 
have tape(s) missing from your media database.  (don't worry, this is 
probably not a data-threatening situation that you're in... ;-)

HTH
rob



On Apr 27, 2005, at 10:08 AM, Lewick, Taylor wrote:

> Hi all, we are using 4.5 FP 8.  For anyone out there using Vault, do 
> you
> notice occasional problems with your Vault produced Offsite reports?
>
> For instance, from time to time I see the following...
>
> MediaId  SLOT  ASSIGNED    EXPIRATION  #IMAGES      KBYTES
>
> LL0133  100237  04/26/2005  05/25/2005        3    15508207   
> LL0136  100238  04/26/2005  05/24/2005        4    25506898   
> LL0137  100239  N/A.        unassigned        0           0   
> LL0147  100240  04/26/2005  05/25/2005        8   228612790
>
> The one that concerns me is the N/A unassigned line.  I look at the 
> tape
> in question, and it has valid images on it, is in the correct pool, 
> etc.
> Just wondering why the vault offsite report does this, if it's a known
> bug, and if there is a fix.
>
> Thanks,
> Taylor
>
> _______________________________________________
> Veritas-bu maillist  -  Veritas-bu AT mailman.eng.auburn DOT edu
> http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
>