You haven't got some strange barcode rule have you or actually lack of a
barcode rule to put new tapes into scratch?
Just a thought.
In the past i've had new tapes come in and get assigned to Netbackup
pool which was reserved for catalogue backups. I'm not sure if this
froze them or not though
ritas-bu-boun...@mailman.eng.auburn.edu] *On Behalf Of *Leo Dream
> *Sent:* Saturday, April 10, 2010 3:49 PM
> *To:* Veritas-bu@mailman.eng.auburn.edu
> *Subject:* [Veritas-bu] New tapes are frozen
>
>
>
> Hi All
>
> Recently we are having some errors with the tapes. We add
Leo,
What type of tape library is it? There was a bug in the microcode for IBM
TS3200 libraries which caused every new tape to be frozen in NBU the first
time it was mounted. I can't find a reference to it now, and don't remember
the details. But out short term fix was to run bplabel manually on a
ng.auburn.edu
Subject: [Veritas-bu] New tapes are frozen
Hi All
Recently we are having some errors with the tapes. We add some new tapes
to the library and inventory successfully (with bar code). However when
we run backups, the tapes are frozen, following errors are shown in the
bptm log:
io_
Hi All
Recently we are having some errors with the tapes. We add some new tapes to
the library and inventory successfully (with bar code). However when we run
backups, the tapes are frozen, following errors are shown in the bptm log:
io_ioctl: ioctl (MTWEOF) failed on media id XX, drive index