TSM Scratch Tape problem

[Billyt]

Got a problem that is totally confusing me.

We have a TSM client server environment running on AIX and in the last week we have been getting problems with our scratch tapes being changed from scratch to private because we are getting messages that the volumes are write protected, even though they are not physically write protected on tapes!!

We have relabelled the tapes and manually made them scratch volumes again but when thyey are selected for use they are again put into a private status to prevent re-access.

The following are the codes we are getting ANR8463E and ANR8778W

Any Ideas?

Regards,

Billy.

PS. TSM version is 4.1.5

 

[LED888]

Billy,

If the tapes are not write protected, but for some odd reason the TSM Server thinks that the tapes are write protected.

In the TSM actlog, do you see any I/O error message or VCR error message? If you do see such message there is a possiblity there is a problem with the tape library.

I've encounter this with a 3494 tape library.
It turn out to be a problem with the tape drive.

Good Luck,
Sias

 

[Billyt]

No there is no indication of any I/O errors on the tapes or the tape drives. We are in the process of running a full iventory of the library as I speak. We shall have to see what the outcome of that action is.

 

[LED888]

Billy,

You didn't mention how many drives in library and if all drives do this, but if you've checked the tapes then it can be a drive.

Drive has to "sense" somehow the write protect tabe of the tape.
It's just another sensor that can fail like any component.

Take all the drive off line from TSM.
Update drive <drive> online=no <- May want to check the syntax.

Take all the drives off line except for one.
Checkout a tape then checkin the tape, did we get the ANR error messages?

No, then take this drive off line and put another drive on line. Checkout and checkin the tape. No, error then on to the next drive.

If all the drives pass.

I would try powering off library/drive, then halt the TSM application. Power on the library/drive, wait for this to complete then start up the TSM Server and see if it clears problem. Encounter strange issue solved just by doing this.

If not run diags or call for service on the tape library.

Good Luck,
Sias