Tape Library Problems and SCSI Tool Request?

Question

Current configuration: Networker 7.4.4 with 2 SCSI connected Quantum i2k libraries connected at different sites. Each library contains 5 x LTO2 SCSI-connected tape drives and is supported by Compaq DL380 Rack-mtd Server running Win2K SP4. Each server contains 3 SCSI cards: LSI Ultra 320 Dual port - each port connected to two daisy-chained LTO2 drives Adaptec 39160 Ultra 160 Dual port - 1 port in use connected to 1 LTO2 drive Adaptec 29160 Ultra 160 Single port - connected to Library Robotics This problem occurs on all drives, on both libraries at random, but this has happened more regularly following an upgrade of library firmware to i6.5. When a tape becomes full during a Networker backup, sometimes the server loses connection with the associated drive. Sometimes this gets recorded in the event logs, sometimes it doesn't. I am able to get Library snapshots but am never able to do a drive dump because the device will always disappear from the SCSI devices table within the LTO-TDX Tape Drive Tool. We have had Quantum look at this and even they cannot get drive dumps until the drive is power cycled. NetWorker shows that the drive is still occupied but is unable to unmount the tape until the affected drive has been Power Cycled from the Quantum LMC. Then NetWorker is usually able to unmount the tape. I accept that this could be a device driver issue, but it's hard to source these IBM LT02 drivers. There are no problems loading tapes that are already full into the drives, the drives never disappear from the Quantum library web interface they disappear from the LTO-TDX tape drive tool table of SCSI devices. The firmware upgrade was applied to correct other problems with the web interface console not updating itself after tickets are cleared etc. Quantum are now asking if there is a tool provided by EMC to capture the SCSI trace of the SCSI command that the software issues to the library so that they can do further testing? Does such a tool exist? Thanks.

ble1 · Answer

NW is using SJI standard for tape removal when talking to library - I believe this is where it breaks. You might have an issue with CDI when using IBM so try to disable CDI first (unless that has been done before). I'm not sure how it is on Windows, but on UNIX with IBM drivers you can raise debug log and you get to see quite a lot.

ble1 · Answer

OK, it's possible. Check the document called IBM Tape Device Drivers Installation and User's Guide. There is section for Windows which gives steps for debugging.

NetWorker

Was this post helpful?