Storage Boards Cleanup
To make it easier to find information about HPE Storage products and solutions, we are doing spring cleaning. This includes consolidation of some older boards, and a simpler structure that more accurately reflects how people use HPE Storage.
Tape Libraries and Drives
cancel
Showing results for 
Search instead for 
Did you mean: 

MSL2024 Veritas 10d

Renos Andreou
Occasional Contributor

MSL2024 Veritas 10d

Setting up An MSL2024 G3 (firmware 3.10) with ultrium 3-scsi (Firmware G54W), using Veritas 10d on a DL380G4 running Win2003 server standard. I can see the Library in HP StorageWorks Library and tape tools, as well as in the windows device manager. Veritas only regognize the drive as stand alone. I cannot see the library. Can anyone help? Thanks!
2 REPLIES
Wei Jung
Trusted Contributor

Re: MSL2024 Veritas 10d

Hi Renos, there are 2 posibilities from the sypmtoms you are describing.

1- MSL2024 tape library uses a single SCSI ID and dual LUNs to control the tape drive (LUN 0) and library robotic (LUN 1). The library requires an HBA that supports LUN scanning. If it is not enabled, your host system scan beyond LUN 0 fails to discover the library. It just sees the tape drive. Make sure you are not using the Smart Array Controller, but a SCSI controller. SA doesn't support LUN scanning, and therefore you will see the drive as a standalone.

2- The other must be that the MSL2024 has to be in Random mode, in order for the picker to be recognized. In Random mode, the library does not automatically load tapes into
the drive; it waits for commands from the software. Your backup software must support robotics.

Also since you are using Veritas, you must use Backupexec drivers for the MSL library to work properly.
Curtis Ballard
Honored Contributor

Re: MSL2024 Veritas 10d

Since you can see the library in windows device manager and L&TT the problem is very likely to be the particular Veritas driver pack that you are using.

HP recommends use of a driver pack dated October of 06 or newer. Any driver pack dated older than October of 05 won't recognize the library at all which sounds like what you are seeing.