Not so weird ;-)

Configured "by the book", your automatic catalog backups alternate between two 
tapes (or a disk and tape).

One way to view/set your configuration is to start the "Configure the Catalog 
Backup" wizard on the "NetBackup Management" page of the GUI.

By the way, a catalog backup to tape starts writing at the beginning of tape 
media, overwriting any previous catalog backup on that tape.

So, NetBackup is trying to use tape DB0007 because that is what was configured. 
 Media Manager doesn't have the tape, so constructs a Pending Mount, which 
apparently/eventually times out.  To use a different tape, run the wizard or 
use the command line interface.  

cheers, wayne

Lewick, Taylor wrote:
> Hi all.  Haven't seen this one before...
> 
> We noticed recently that several of our Catalog Backups had been failing
> with status 52.  "time out waiting for media manager to mount volume".
> We then noticed that half of the Catalog backups were failing, and it
> was always with the same media, DB0007.  So I had an operator eject
> DB0007 and mark it as offsite via the GUI.  I wanted to examine the
> tape, see if it was damaged since it could never be loaded.
> 
> Well this morning the Catalog backup runs, and its now trying to mount
> DB0007.  Any idea why it is trying to mount a tape that is out of the
> library and is marked as being offsite?
> 
> Is the default behavior to keep using the same tape for a catalog backup
> until it is filled up?  If so, short of deleting this tape, how can I
> tell NetBackup to not use this piece of media for a catalog backup?
> Remove it from the volume pool?
> 
> Any response is appreciated.
> Thanks,
> Taylor 
> 
> _______________________________________________
> Veritas-bu maillist  -  Veritas-bu AT mailman.eng.auburn DOT edu
> http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu