Why Tape Hardware Device(s) are not recognized within Backup Exec for Windows Servers

Problem

Why Tape Hardware Device(s) are not recognized within Backup Exec for Windows Servers

Error Message

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

0003:0000:0001:0000  Device Name             ""
                    Secondary Name          "\\.\Changer0"
                    Primary Inquiry         "OVERLANDNEO Series      0429"
                    Serial Number           ""
                    Device Flags            KSCSI
                    Device State            1, Offline, ERROR = 0x0000007B (ERROR_INVALID_NAME)

0003:0000:0002:0000  Device Name             "\\.\Tape0"
                    Secondary Name          "\\?\scsi#sequential&ven_hp&prod_ultrium_1-scsi&rev_e37u#6&2de9619e&0&020#{53f5630b-b6bf-11d0-94f2-00a0c91efb8b}"
                    Primary Inquiry         "HP      Ultrium 1-SCSI  E37U"
                    Serial Number           "HP      Ultrium 1-SCSI  HUB4C03CNK"
                    Device Flags            KSCSI, SN(TYPE 1)
                    Device State            3, Online

                    Device IDs              1020, {D4891E8B-EE5A-4688-95F7-105908059A94}
                    Device Name             "HP 1"
                    Device Type             134283265, "LTO 64K (64K,10,0,E,HU)"
                    Device Features         0x000BFB7F: PB,SFB,SRB,WFM,SFF,SRM,PEOD,ES,EL,LU,E,SBS,DC,SDC,TA,HU,RR
                    Device Element          0, 0
 

Cause

In order for devices to be correctly identified by Backup Exec, the device(s) must first be visible in the Windows Device Manager.  It is also necessary for serialization (i.e.: Element Serialization) to be returned when an inquiry command is sent by Backup Exec to each attached device.  In the BEDiag ADAMM section example below, the tape device will show in Backup Exec as a standalone drive, as the library is not returning serialization, and therefore not recognized as an available device.
 

Solution


If the drivers/firmware are at the latest level and cabling, termination, etc... are confirmed to be connected properly, contact the tape hardware manufacturer to determine why serialization is not being returned.

 

Terms of use for this information are found in Legal Notices.

Search

Survey

Did this article answer your question or resolve your issue?

No
Yes

Did this article save you the trouble of contacting technical support?

No
Yes

How can we make this article more helpful?

Email Address (Optional)