Backup Exec not recognising HP autoloader as Robotic lib

[Mynor Aguilar]

Curtis is on the right track, Do not connect this kind of library on the scsi port of the array controller, there's some issue with LUN scanning. I had the same problem a while ago with a 1/8 ultrium 448 autoloader, checking on the quickspecs for my server they recommended 374654-B21 for my 1/8 autoloader, it didnt work cause it didnt support ultra 160,
if you have 1/8 ultrium 960, 374654-b21 (ultra 320 HBA) should work fine, otherwise if you have a 1/8 ultrium 448 or 232, find an HBA that supports ultra160. I think that 284688-b21 is compatible with 448 and 232, but I'm not 100% sure

regards,
Mynor Aguilar

[Jaclyn Rothe]

Just quick steps to check

1) Using BUE needs BUE drivers installed in Windows Device manager...
2) SCSI card has to have raid disabled, or the LUN will not be recognized byt hte controller card
3) Always avoid generic microsoft or HP drivers for LSI or Adaptec SCSI cards, and for tape drives using other then HP branded software (Arcserve, BUE etc)
4) Make sure that 'Unknown Medium changer' shows in Device manager and also an entry under Tape Drives.
5) Firmware needs to be at latest revision because BUE has issues detecting a certain version of frimware.

[Jaclyn Rothe]

I seem to have missed what kind of server this is... but here is the HP compatibility page... clcik the checkmark beside the drive type and server type to get the compatible controllers:

http://www.hp.com/products1/storage/compatibility/tapebackup/ISS/index.html


If non-HP server here are the only option for HBA compatibility:

http://www.hp.com/products1/storage/compatibility/tapebackup/ThirdParty/index.html#HBA

[Jaclyn Rothe]

And to add RSM causes detection issues in Windows 2003... you need to run this document as well:


http://support.microsoft.com/kb/842411

[Heshmat]

So if its seen in the OS then the library is good, and settings too, it seems like a application issue, check this out.

http://seer.support.veritas.com/docs/251561.htm

I have seen this issue fix by running tapeinst.exe and selecting the option to use veritas drivers for all tape devices after updating BUE to the latest. to locate tapeins.exe just run a search, it should be somewhere under the installation folder for veritas.

[Jaclyn Rothe]

yes... those are the direct steps for my response above
" 1) Using BUE needs BUE drivers installed in Windows Device manager..."