Monday, April 30, 2007
Audit Library Issue
I had something crazy happen this weekend with our STK L700. It somehow ended up needing an audit of the library, but when we would run the audit it would fail. Failure of a command I can live with but there was no supporting messages to explain the cause of the failure. The library was rebooted multiple times, but the audit still was failing. Finally my resourceful manager Steve ran an audit library with the PVR and MMS flags and the audit completed successfully. The one thing it could have been was from a stuck tape in a tape drive, but why no context message to explain the failure? We had deleted the drive and the path and the tape should have been removed on the first audit since it could no longer be seen.
Subscribe to:
Post Comments (Atom)
I have seen the close to the same thing. The audit library has failed with any of the following issues present:
ReplyDelete1.Tape stuck in drive (Like yours)
2.Tape drive failure
3.Fibre Card failure on server that drives a tape drive.
The drive failure does not always result in a audit failure.
The strange thing is we deleted the paths and drive definition from TSM and still the audit only ran successfully after tracing was turned on and those two flags added.
ReplyDeleteI have seen this before, but in a different light; I would run a AUDIT LIBR (with the CHECKL=B), and the audit would run successfully. Then, I would run the same command, but with the CHECKL=y,...and it would fail.
ReplyDeleteI updated my Atape.driver, and life was good
JMT