HP 1/8 Ultrium 448 autoloader can't detect with Veritas 9.1

[Kuekul_Jutiviwa]

Dear Sir/Madam

I use Veritas 9.1 and use "HP 1/8 Ultrium 448 autoloader" But I can't use autoloader mode. Veritas Detect Hardware on standalone Drive and I attach file Diag for you solve

************************* Diag *************************

6024] 10/01/05 09:14:30 Adamm Log Started! ("TPL2", 1000, {14F57FA4-855E-4D28-95D0-4933470CA84E})

Adamm Info: Version 9.1, Build 4691

OS Info: Windows NT 5.2, Build 3790, Service Pack 1

Database Driver Info: SQLSRV32.DLL, 03.86.1830
Database Server Info: Server Name = "TPL2", Active Node = ""
Database Connection String: "DRIVER=SQL Server;SERVER=TPL2\BkupExec;DATABASE=BEDB"

Shared Storage Authorization: No
TSM Authorization: No
Library Expansion Options: 1
Evaluation Days Remaining: 59

10/01/05 09:14:30 Device Registry:

Scsi Address
Prt :Bus :Tar :Lun Attributes
------------------- ---------------------------------------------------

0000:0000:0000:0000 "atapi", (Port Driver)

------------------- ---------------------------------------------------

0001:0000:0000:0000 "atapi", (Port Driver)

------------------- ---------------------------------------------------

0002:0000:0000:0000 "adpu160m", (Port Driver)

------------------- ---------------------------------------------------

0003:0000:0000:0000 "adpu160m", (Port Driver)

------------------- ---------------------------------------------------

0004:0000:0000:0000 "cpqcissm", (Port Driver)

------------------- ---------------------------------------------------

0005:0000:0000:0000 "symmpi", (Port Driver)

0005:0000:0005:0000 "HP Ultrium 2-SCSI S38W", (Tape Device), "\\.\Tape0"

0005:0000:0005:0001 "HP 1x8 autoloader 1.40", (Changer Device), ""

------------------- ---------------------------------------------------
0006:0000:0000:0000 "symmpi", (Port Driver)

------------------- ---------------------------------------------------

10/01/05 09:16:30 Device Discovery:

Scsi Address
Prt :Bus :Tar :Lun Attributes
------------------- ---------------------------------------------------

0005:0000:0005:0000 Device Name "\\.\Tape0"
Primary Inquiry "HP Ultrium 2-SCSI S38W"
Serial Number "HP Ultrium 2-SCSI HU1052402V"
Device Flags SCSI, SN(TYPE 1)
Device State 3, Online

Device IDs 1002, {38D51685-6577-40BD-B8BD-23DA787A5585}
Device Name "HP 1"
Device Type 134283265, "LTO 64K (64K,10,0,E,HU)"
Device Features 0x00021000
Device Element 0, 0

0005:0000:0005:0001 Device Name ""
Primary Inquiry "HP 1x8 autoloader 1.40"
Serial Number ""
Device Flags SCSI
Device State 1, Offline, ERROR = 0x0000007B (ERROR_INVALID_NAME)

------------------- ---------------------------------------------------

10/01/05 09:16:30 Device Discovery End:

10/01/05 17:05:12 Adamm Log Stopped!
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

More Infomation

- I've install SP3 for BE 9.1
- BE4691RHF54_278467.EXE implemented
- IDR_PREP_278553.ZIP implemented

Many Thanks in Advance

Kuekul JutiviwatMessage was edited by:
Kuekul Jutiviwat

[Milouse]

Hi,

You could try this:


* First make sure the robotic library option is installed

* Delete drive in BEWS devices tab

* Check its SCSI id (3 would be perfect)

* Make sure the Autoloader is set to 3, with correct HP drivers loaded (it should be seen correctly in Windows device manager, not as "unknown medium changer")

* Disable Removable Storage service

* Make sure your device is not connected to a RAID controller card but on the Adaptec 160

* Shut down media server

* Shut down the library

* Power on the library

* Power on media server after full device initialization

* Launch \Backup Exec\NT\\Tapeinst.exe to load the Veritas drivers and delete old drives entries (leave the rest blank)

* Launch the Device Config Wizard in BEWS

* If you still don't see the autoloader, uninstall the Robotic library option, delete the SCSI Changer Reg key, and reinstall the otpion
http://support.veritas.com/docs/242235

Hope this helps :)

Sam

[Rucha_Abhyankar]

Hello,

Please let us know if you have tried out the steps provided in the earlier reply.

========================


NOTE : If we do not receive your reply within two business days, this post would be marked assumed answered and would be moved toanswered questions pool.

[Kuekul_Jutiviwa]

Dear Sir
I can't detect HP in autoloader, I detect it in standalone again
Veritas 9.1 have driver of HP 1/8 Ultrium 448 autoloader ?

Thank you very much

[Amruta_Purandar]

Hello,

These are the latest drivers available.
VERITAS Backup Exec (tm) 9.1 - Device Driver Installer (20050115) - Includes Tape Driver Release (20041231) and Robotic Library Release (45) (Intel Only)
http://support.veritas.com/docs/273853

However please let us know if you have checked all the parameters mentioned in the previous reply. Also did you apply the technote provided by Mr. Abed?


NOTE : If we do not receive your reply within two business days, this post would be marked assumed answered and would be moved to answered questions pool.

[Erik_van_Kruise]

I have the same issue with the same hardware and Backup Exec version.
tried all above mentioned solutions. even tried OEM drivers.
This library is just not recognized.
Is there something else I could try, I really need this to work soon.

thanks in advance

Regards,
Erik

[Erik_van_Kruise]

I have found the problem.. now to get to a solution.

Issue:
Tapedrive is found as a standalone drive.
Library is only found in windows.. if you enable removable storage you can see the device as it should be.

Cause:
This HP 1/8 Ultrium 448 autoloader uses 2 LUN's LUN0 for the tapedrive and LUN1 for the library.

Solution: ???? Veritas Support???

Regards,
Erik

[Hugo_Westerlow]

Just adviced one of our clients to buy this Autoloader to find out that BackupExec 9.1 doesn't work with this. Same problem, in Windows everything is ok. With RSM disabled reinstalled BackupExec 9.1 with all updates (drivers ect..) Still same problem. Then I installed a trial of BackupExec 10.0 still the same problem. Installed the latest drivers for 10.0 the drives and all the slots are seen, everything works fine. This means BackupExec 9.1 with latest drivers doesn't see this Autoloader, just the Drive.

I know this drive uses de driver BNCHMRK2.VSD so when I installed the trial of BackupExec 9.1 I coppied this file to a temp dir. after reinstalling 9.1 I renamed c:\windows\system32\drivers\BNCHMRK2.VSD and coppied the driver from 10.0 to c:\windows\system32\drivers\
After I restarted the server the Autoloader was recognised and working. I know that maybe this is not a good solution but hope Veritas (Symantec) will come with a new driver update for BackupExec 9.1 because at the moment an upgrade to 10.0 or 10.1 is not an option.