cancel
Showing results for 
Search instead for 
Did you mean: 

BackupExec 2014 not seeing HP MSL 2024 SCSI tape library

stonek
Level 2
Partner

Hi, I cannot force BackupExec 2014 to see my robotic library HP MSL 2024 with one Ultrium-3 drive. BE sees the Ultrium-3 drive only, not the library. Reinstallation of whole BackupExec 2014 did not work. OS is Widnows Server 2012 R2. Discover.exe utility is able to detect the library:

c:\Program Files\Symantec\Backup Exec>discover.exe

System Page Size: 4096

ByName: Tape

ByName: MediumChanger

ByName: Changer

03:00:04:01 08 -- \\.\Changer0
INQ 00 "HP MSL G3 Series 6.10"
INQ cc "HP MSL 2024 6.10"
INQ dc ""
INQ 83 "HP MSL G3 Series DEC110083X"
INQ 80 "DEC110083X"
TUR 00 00000
RES 00 00 00000
REL 00 00 00000
MTE 0000 1
STE 03e9 24
IEE 0065 0
DTE 0001 2
0 "HP Ultrium 3-SCSI HU1091375R"
1 "HP Ultrium 2-SCSI HUE065124R"
BUS SCSI(1)
MAX controller bytes 0xffffff pages 0x101

ByPort: Scsi

02:00:00:00 1f -- \\.\Scsi2:
INQ 00 "COMPAQ SCSI COMMUNICATECIS2"
INQ cc "COMPAQ SCSI COMMUNICATECIS2"
INQ dc "COMPAQ SCSI COMMUNICATECIS2"
INQ 80 ""

ByGuid: Tape

03:00:04:00 01 2147483646 \\?\scsi#sequential&ven_hp&prod_ultrium_3-scsi#8&894
225b&0&000400#{53f5630b-b6bf-11d0-94f2-00a0c91efb8b}
INQ 00 "HP Ultrium 3-SCSI D24W"
INQ cc "HP ULTRIUM920 DRV D24W"
INQ dc ""
INQ 83 "HP Ultrium 3-SCSI HU1091375R"
INQ 80 "HU1091375R"
TUR 00 23a00
RES 00 00 00000
REL 00 00 00000
MAX drive bytes 0xffffff
MIN drive bytes 0x1
BUS SCSI(1)
MAX controller bytes 0xffffff pages 0x101

ByGuid: Changer

03:00:04:01 08 00 \\?\scsi#changer&ven_hp&prod_msl_g3_series#8&894225b&0&00040
1#{53f56310-b6bf-11d0-94f2-00a0c91efb8b}

ByGuid: ChangerIomega

ByGuid: CDRom

c:\Program Files\Symantec\Backup Exec>

Drivers and firmware for the SCSI card, tape drive and tape library are the latest.

Licenses:

lic.PNG

Any suggestions?

Thank you.



 

1 ACCEPTED SOLUTION

Accepted Solutions

Larry_Fine
Moderator
Moderator
   VIP   

03:00:04:00 01 2147483646 \\?\scsi#sequential&ven_hp&prod_ultrium_3-scsi#8&894
225b&0&000400#{53f5630b-b6bf-11d0-94f2-00a0c91efb8b}

I think this is the key to your issue.  BE doesn't like that huge tape handle number.

I would suggest deleting the keys HKey_Local_Machine\System\CurrentControlSet\Control\Tape\Persistence and HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\MChgr\Persistence (or set them to 0), then reboot the server.  BE should be happy with low \TapeX, \ChangerX and/or \scsiX numbers.

View solution in original post

7 REPLIES 7

CraigV
Moderator
Moderator
Partner    VIP    Accredited

Hi,

 

What Windows sees, BE sees...also make sure that the robotics shows as "Unknown Medium Changer" in Device Manager if Windows sees the robotics.

Thanks!

stonek
Level 2
Partner

Hi, thaks for the reply.

In my case not - look at the screenshots:

tape.PNG

Device manager:

device.PNG

 


 

CraigV
Moderator
Moderator
Partner    VIP    Accredited

...try removing the library from within Windows and BE before disconnecting it from the media server.

restart the media server and confirm the library doesn't show up in Windows. then shut down the server, reconnect the library and start it up. Once initialized, start up the media server and run tapeinst.exe to install the drivers for the drive, and check to see if this fixes it.

Thanks!

Larry_Fine
Moderator
Moderator
   VIP   

03:00:04:00 01 2147483646 \\?\scsi#sequential&ven_hp&prod_ultrium_3-scsi#8&894
225b&0&000400#{53f5630b-b6bf-11d0-94f2-00a0c91efb8b}

I think this is the key to your issue.  BE doesn't like that huge tape handle number.

I would suggest deleting the keys HKey_Local_Machine\System\CurrentControlSet\Control\Tape\Persistence and HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\MChgr\Persistence (or set them to 0), then reboot the server.  BE should be happy with low \TapeX, \ChangerX and/or \scsiX numbers.

stonek
Level 2
Partner

That did the trick! Thank you very much Larry.
 

Steve-Young
Level 6
Employee

This has been resolved in Backup Exec 2014 Hotfix 217591

http://www.symantec.com/docs/TECH217591 

 

SuperBrain
Moderator
Moderator
Employee Accredited

Hi stonek,

What Larry mentioned with the registry modification suggestions could be a workaround to your problem. I recommend you follow what Steve mentioned below and install BE2014 Hotfix 217591.