Also you can check with this command:
bperror -media -hoursago 9999 |findstr FREEZ
for wintel and for unix based below
bperror -media -horusago 9999 |grep FREEZ
common issues are: drive number differs on NBU end and library; write protected media; misplaced media, robot inventory not up to date....
Have you checked if bptm log folder exists on media server(s)?
Please bear in mind that level 5 logging creates massive log files that are difficult to read.
I only enable level 5 logging when a Support is logged with Veritas.
Level 3 logs are sufficient in most circumstances.
You don't need to wait for another failure or freeze to run tape log report (or bperror command).
Event Viewer logs (System and Application) will only help if VERBOSE entry was added to vm.conf on media server(s) followed by restart of ltid (NBU Device Management service).
PLEASE KEEP IN MIND - TAPE FREEZING IS NOT ALWAYS ABOUT THE TAPES!
Especially when you have a lot of tapes freezing.
I see this when I have a tape stuck in a drive, NB tries to load a tape and the tape load fails, so NB blames the tape, and freezes it. Sometimes you have to manually check the drive, sometimes NB will request a tape unload, and never get the message that the tape is stuck!
Also, there have been issues with LTO firmware, so if a tape is labelled with one drive, it will not work with another.
I would review your logs, and do some testing - label some scratch tapes and verify each one loads and unloads cleanly.
My best operator contacted me yesterday, he had noticed that the leader pins on tapes coming back from Iron Mountain were not seated properly.(I have my operators manually check EVERY cart when they load to ensure the write tab is clear, and the leader pin is set - you have to actually open the little sliding access door on every tape!)
This would have caused tape load issues and these would all have frozen!
Time to get your junior detective hat out and use your deductive reasoning!
have you performed any checks on tape drives as tapes are always freezing it is something like drives might having the issue ?
try running diagnostics from library console and see how it comes out
have you setup the tapes with correct density levels ?