Reviewing hardware configuration on Backup Exec for Windows Media Servers using TILDBG.TXT
Server Name Is: // Servername is NOT logged
Todays Date Is: Sun Sep 21 10:45:56 2008 // Time drivers started up
Host Bus Adapters:
This sections lists all of the Host Bus Adapters detected by the system.
Adapter ( 1 ) Windows Manager
Adapter ( 2 ) Windows Manager
Adapter ( 3 ) Windows Manager
Adapter ( 4 ) Windows Manager
Adapter ( 5 ) Windows Manager
Adapter ( 6 ) Windows Manager
Adapter ( 7 ) Veritas VirtHBA
Devices In Host Bus Adapter Order:
These are the devices that were seen by the driver when it was loading. Devices show up here even if they are not eventually recognized by the drivers as being supported.
Also, they show up in the order that they were found on the system.
Drive/Robot ~ (Host, SCSI ID, LUN) ~ Vendor ~ Model ~ Firmware
----- Devices In Host Bus Adapter Order ------
Drive ( 00,00,00 ) 05 HP Ultrium 4-SCSI pf89
Robot ( 00,02,00 ) 04 HP D2DBS pf89
Drive ( 00,07,00 ) 07 HP Ultrium 4-SCSI H49W
Robot ( 00,07,01 ) 06 HP MSL G3 SERIEs 4.40
Devices In Application Order:
These are the devices that were recognized by the device drivers and are being presented to the application as available devices.
If a device is present above, but is not listed in Application Order, then there most likely is not a driver to load for this device. Verify that the device is supported on the hardware compatibility list.
----- Devices In Application Order -----
Robot ( 00,02,00 ) HP D2DBS pf89 UltrmLoader:443,299:0
Drive ( 00,00,00 ) HP ULTRIUM 4-SCSI pf89 UltrmLoader:240:0
Robot ( 00,07,00 ) HP MSL G3 SERIEs 4.40 UltrmLoader:368,368:1
Drive ( 00,07,00 ) HP ULTRIUM 4-SCSI H49W UltrmLoader:240:1
Serial numbers associated with the drives and robots.
If the driver can't get a serial number, it doesn't know how to match it up to the DTE in the library in the section below. This is indicative of a problem and will generate a "Missing" device, as the driver couldn't match it up because it was unable to get serial number information from the library for this drive (see section below):
----- Serial Numbers -----
Robot ( 00,02,00 ) Serial Number = 2UX8400TB5
Drive ( 00,00,00 ) Serial Number = 2UX8400T83
Robot ( 00,07,01 ) Serial Number = MXA84110EW
Drive ( 00,07,00 ) Serial Number = HU18393BNA
There will be a section for each medium changer named 'Robot Information' which contains detailed information retrieved from that particular robot. Note that during this process the driver is going to try to match up the DTE serial numbers here with the serial numbers it got from the drives in the previous section.
----- Robot Information -----
Robot ( 00,02,00 ) HP D2DBS pf89
Number of drives the changer recognizes (DTE = Data Transfer Element).
Number of slots the changer recognizes (SSE = Storage Element).
Number of media export portals the changer recognizes (IEE = Import\Export Element).
Number of Drives = 1 FirstDTE = 0001
Number of Slots = 23 FirstSSE = 03e9
Number of Portals = 1 FirstIEE = 0065
Robot serial number is the serial number of the changer itself.
The Robot DTE is the serial numbers of the drives that belong to the changer.
Robot Serial Number = MXA84110EW
Robot DTE_01 Serial Number = HU18393BNA
If the changer does not provide a serial number for the Robot DTE, this causes the driver to be unable to match the tape drive with its changer. Such an example would generate the following error:
Robot DTE_02 Serial Number = MISSING_DRV_IN_LDR_90
If the above library also contained the DTE_02 entry from above, yet physically only had 1 drive within the actual library, the the Backup Exec GUI would report this library contained 1 online tape drive and a MISSING1 drive. This would be due to the library reporting it had 2 drives when it only had a single drive.