Backup Exec 12.5 cannot identify HP LTO 1/8 Ultrium-3 Auto G2

[Olympia69]

Hi guys,

I just changed the cable from 1/8 LTO Ultrium-2 (HP2) to 1/8 LTO Ultrium-3 G2 (HP3), using the same server and Backup Exec 12.5. The NT Device Manager indicates the HP3, as it used to indicate HP2, previously. I haven't touched the terminators of both machines. Everything is fine till this moment. Then I stopped and started the BE services. However, under section "Devices" of BE, there is no any indication of Robotic Libraries (it has to show the HP3).

Can you tell me, please, what should I do, in order to recognize HP3 by the BE 12.5? Step by step instructions, please. I guess I need some drivers.

Thank you in advance.

[Ken_Putnam]

Run the device wizard to detect the new hardware

[pkh]

Make sure that in the Windows Device Manager the library is listed as an Unknown Medium Changer with a Microsoft driver and the tape drive is listed as a HP tape drive.

Once this is done, you can use the tapinst.exe to install the tape library and tape drive.  Make sure that you delete all previous entries of the library and tape drive.  tapeinst.exe can be found in the BE installation directory.

[CraigV]

...if you swopped out the device and Windows detects it after a device rescan, but BE doesn't, you need to restart the services first. The Device Configuration Wizard won't detect the autoloader until BE sees it...

[Olympia69]

Thank you for your advices. Unfortunately, the issue still persists. Here is what I did:

1. Opened "Device Configuration Wizard" and installing through it the "tapeinst.exe" by following the instructions, as shown on http://www.symantec.com/business/support/index?page=content&id=TECH6098
The only difference is that I ticked ALSO the option "Delete entries for the tape devices that are unavailable, removed, or turned off" (http://www.symantec.com/business/support/library/BUSINESS/ATLAS/images_v1/199881/6.jpg).
2. Turned off the server. Turned on the server.
3. Stopped the BE services. Started the Be services. Logged in.
4. Refresh on "Storage Devices" -> No any difference.
5. Started "Initialize Library" job -> immediate error: "Final error: 0xe0008113 - Physical Volume Library Robot not found. Final error category: Backup Device Errors".

Any further ideas, please?

[Striker_303]

Medium changer (Robotic arm) is missing in Windows device manager

make sure robotic library is properly connected  to server, do a powercycle,

If issue still persist contact hardware vendor.

Have you reffered this article yet:  http://www.symantec.com/docs/TECH24414

[Olympia69]

@Striker 303, yes, it is properly connected to the server and I did a powercycle, of course.

[CraigV]

...also check the SCSI ID of the changer and the drive and make sure they aren't clashing, and that a terminator is securely connected to the correct port on the back of the autoloader.

Furthermore, make sure it isn't connected to a RAID controller...this isn't an HP-supported configuration, and it must be connected to a SCSI card!

[Striker_303]

Medium changer in device manager should look like this:

If Library is already connected to proper port ..then you may also need to check internal jumper \cabling within Robitic library

[Olympia69]

Here it is what it is at my NT server 2003:

I've downloaded and installed the "HP Library and Tape Tools", in order to upgrade the firmware (an exe file that I got from the same page). Unfortunately, the  "HP Library and Tape Tools" cannot recognize any tape device, in order to start verification process.

[Olympia69]

https://www-secure.symantec.com/connect/sites/default/files/images/hp_ltt.jpg

[Olympia69]

https://www-secure.symantec.com/connect/sites/default/files/images/hp_ltt2.JPG

[Olympia69]

I stopped the services of BE and the drive was available for actions with HP L&TT.

https://www-secure.symantec.com/connect/sites/default/files/images/hp_ltt3.jpg

[Olympia69]

Ridiculous! There are tapes in both of the magazines of the Autoloader.

https://www-secure.symantec.com/connect/sites/default/files/images/hp_ltt4.jpg

[teiva-boy]

So you have a configuration issue in hardware and or the OS at issue here if HP's own diagnostic tools cannot report back correctly.

Once that is handled, and Windows detects everything correctly, then BackupExec (after restarting servces) will typically work like a charm.

[Olympia69]

Thanks. Do you have any particular advices on how should I proceed?

[pkh]

You should contact HP.and get them to make sure that the tape library passes all the LT&T tests.  You should make sure you do a write test.

[CraigV]

...for some of these tests you need to manually load the tape into the drive.

For the SCSI ID, you can consider changing it...

http://www.symantec.com/business/support/index?page=content&id=TECH36673

here are also some TNs to read for interest's sake:

http://www.symantec.com/business/support/index?page=content&id=TECH42823

http://www.symantec.com/business/support/index?page=content&id=TECH14891

[Olympia69]

CraigV, thanks for those links.  

On the Device Manager SCSI stays on ID4. I read that the rest of the SCSI IDs I have to add through Operator Control Panel (OCP) or Remote Management Interface (RMI). Can anyone explain how can this happen? I tried CraigV's steps but it didn't work (scroll to the middle of the page).

From the MSL Command View I can choose only one drive, that by default was chosen to be "4". It seems I cannot add more than one drive from the MSL Command View.

Because it is only one SCSI ID (that is chosen to be "4" by default) I think this is the reason the Backup Exec (BE) to identify the Autoloader as a standalone device and nothing appears under the "Robotic Libraries" ("Devices" section) in BE. When all eight drives are added (from "0" to "7"), then they should appear under "Robotic Libraries" in BE.

Upgrade Drive Firmware
Drive Firmware Revision	D24W

Currently Installed Autoloader Firmware

3.00

[CraigV]

...that's a 1U G2 autoloader and it doesn't have capacity for 8 drives. What exactly do you mean by that? I suspect you mean SCSI ID...in which case 1 device per SCSI ID only.

Try changing the SCSI ID of the robotics to 1, and the SCSI ID of the drive to 0. Reset and restart the server if necessary.

You never mentioned what card the autoloader is connected to either.