Also, sometimes a tape gets funny. I've had to relabel tapes before with
overwrite=yes in order to make them work at times. Something the first label
gets funky or something.
David N. Reiss
TSM Support Engineer
[EMAIL PROTECTED]
407-736-3912
-----Original Message-----
From: Williams, Tim P {PBSG} [mailto:[EMAIL PROTECTED]]
Sent: Friday, September 20, 2002 10:38 AM
To: [EMAIL PROTECTED]
Subject: Re: tapes getting marked PRIVATE
is the db backup from the dbbackuptrigger (based on log filling?)? check
device class
is this db backup from a command (check device class in use...
-----Original Message-----
From: Theresa Whitney [mailto:[EMAIL PROTECTED]]
Sent: Friday, September 20, 2002 8:45 AM
To: [EMAIL PROTECTED]
Subject: tapes getting marked PRIVATE
It looks to me that each time I run a db backup TSM will attempt to grab
a tape, think it finds an I/O error on the label read, then marks the
tape PRIVATE and then moves on to the next tape. That wouldn't be such
a problem except that it will do this to almost every tape in my
library.
I have had the drive hardware checked in the library and had both
drives replaced. Did not have the picker checked.
This problem does not seem to be happening during a regular data backup
- only during the DB backup.
Anyone seen this before or have any ideas.....?????
Theresa Whitney
Technical Systems Admin
Northside ISD
ph: (210) 706-8837
fax: (210) 706-8877
email: [EMAIL PROTECTED]
