07-06-2011 01:52 AM
Hi,
Recently we purchased an “Overland NEO 400s“ library as a replacement for a HP library and I’m trying to access it with Veritas Netbackup Enterprise 6.5.6.
I downloaded the newest external_types.txt (1.96) which contains the following entry:
[LIBRARY:Overland NEO Series] INQUIRY=OVERLANDNEO Series ROBOT=TLD - Tape Library DLT LIBRARY_SERIALIZATION=3 BARCODE_DETECTION=550 COMPATIBILITY_TAG=4259841 UNKNOWN_BARCODE_SENSE=8309
I checked if this version is loaded into the device manager database:
veritas02:/usr/openv/volmgr/bin # ./tpext -get_dev_mappings_ver device mappings version in the EMM database is 1.96 device mappings version from the local file is 1.96 Local device mappings file is up-to-date
The drive and robotic device are recognized by Netbackup as HP devices (robotic device: HP MSL G3 Series G33 / drive: HP Ultrium 5-SCSI Y32W) – is this a normal behavior?
Unfortunately regarding to Netbackup's device wizard only the drive is usable but not the robotic device.
I already checked the output of a few commands on the bash:
veritas02:/usr/openv/volmgr/bin # ./tpautoconf -t TPAC60 HP Ultrium 5-SCSI Y32W HU1115G3DC -1 -1 -1 -1 /dev/nst0 - - veritas02:/usr/openv/volmgr/bin # ./scan -changer ************************************************************ *********************** SDT_CHANGER ************************ ************************************************************ ------------------------------------------------------------ Device Name : "/dev/sg1" Passthru Name: "/dev/sg1" Volume Header: "" Port: -1; Bus: -1; Target: -1; LUN: -1 Inquiry : "HP MSL G3 Series G.33" Vendor ID : "HP " Product ID : "MSL G3 Series " Product Rev: "G.33" Serial Number: "MXA118Z0D3" WWN : "" WWN Id Type : 0 Device Identifier: "HP MSL G3 Series MXA118Z0D3" Device Type : SDT_CHANGER NetBackup Robot Type: 8 Removable : Yes Device Supports: SCSI-5 Number of Drives : 2 Number of Slots : 48 Number of Media Access Ports: 0 Drive 1 Serial Number : "HU1115G3DC" Drive 2 Serial Number : "HU1115G3DC" Flags : 0x0 Reason: 0x0 veritas02:/usr/openv/volmgr/bin # ./scan -tape ************************************************************ *********************** SDT_TAPE ************************ ************************************************************ ------------------------------------------------------------ Device Name : "/dev/nst0" Passthru Name: "/dev/sg0" Volume Header: "" Port: -1; Bus: -1; Target: -1; LUN: -1 Inquiry : "HP Ultrium 5-SCSI Y32W" Vendor ID : "HP " Product ID : "Ultrium 5-SCSI " Product Rev: "Y32W" Serial Number: "HU1115G3DC" WWN : "" WWN Id Type : 0 Device Identifier: "" Device Type : SDT_TAPE NetBackup Drive Type: 10 Removable : Yes Device Supports: SCSI-6 Flags : 0x0 Reason: 0x0 veritas02:/usr/openv/volmgr/bin # lsscsi -g [0:0:0:0] tape HP Ultrium 5-SCSI Y32W /dev/st0 /dev/sg0 [0:0:0:1] mediumx HP MSL G3 Series G.33 - /dev/sg1 [0:0:1:0] disk SUN CSM200_R 0619 /dev/sda /dev/sg2 [0:0:1:1] disk SUN CSM200_R 0619 /dev/sdb /dev/sg3 [0:0:1:2] disk SUN CSM200_R 0619 /dev/sdc /dev/sg4 [0:0:1:3] disk SUN CSM200_R 0619 /dev/sdd /dev/sg5 [0:0:1:4] disk SUN CSM200_R 0619 /dev/sde /dev/sg6 [0:0:1:5] disk SUN CSM200_R 0619 /dev/sdf /dev/sg7
I already rescaned the SCSI/HBA interfaces and also rebooted the server.
Am I missing something? I'm really out of ideas at the moment.
Thanks,
Matthias Bodsch
07-06-2011 02:51 AM
Before detecting new Tape library, old library devices should be deleted from netbackup. All the drives and robots from the old library should be deleted and check if globDB is updated. Then try to detect the new drives and rebuild sgdrivers and finally try to configure in netbackup.
--Praveen
07-06-2011 03:23 AM
Any more info when you click on 'Properties'?
The devices recognized as 'HP' is certainly normal - have a look at the Hardware Compatibility Guide:
http://www.symantec.com/docs/TECH48687
Inquiry string from the device is reporting " HP MSL G3 Series" . G.33 is the firmware version.
What I find strange is that the robot itself reports 2 tape drives, but with the same serial number?
Number of Drives : 2 Number of Slots : 48 Number of Media Access Ports: 0 Drive 1 Serial Number : "HU1115G3DC" Drive 2 Serial Number : "HU1115G3DC"
Something 'strange' about robot config? Maybe that is why reports the robot as 'unusable'?
Ask your hardware support team about this?
07-06-2011 03:38 AM
Following on from Mariannes excellent post ....
If I understood correctly, you have x1 robot and x1 tape drive ...
*********************** SDT_CHANGER ************************ ************************************************************ ------------------------------------------------------------ Device Name : "/dev/sg1" Passthru Name: "/dev/sg1" Volume Header: "" Port: -1; Bus: -1; Target: -1; LUN: -1 Inquiry : "HP MSL G3 Series G.33" Vendor ID : "HP " Product ID : "MSL G3 Series " Product Rev: "G.33" Serial Number: "MXA118Z0D3" WWN : "" WWN Id Type : 0 Device Identifier: "HP MSL G3 Series MXA118Z0D3" Device Type : SDT_CHANGER NetBackup Robot Type: 8 Removable : Yes Device Supports: SCSI-5 Number of Drives : 2 Number of Slots : 48 Number of Media Access Ports: 0 Drive 1 Serial Number : "HU1115G3DC" Drive 2 Serial Number : "HU1115G3DC" Flags : 0x0 Reason: 0x0 veritas02:/usr/openv/volmgr/bin # ./scan -tape ************************************************************ *********************** SDT_TAPE ************************ ************************************************************ ------------------------------------------------------------ Device Name : "/dev/nst0" Passthru Name: "/dev/sg0" Volume Header: "" Port: -1; Bus: -1; Target: -1; LUN: -1 Inquiry : "HP Ultrium 5-SCSI Y32W" Vendor ID : "HP " Product ID : "Ultrium 5-SCSI " Product Rev: "Y32W" Serial Number: "HU1115G3DC" WWN : "" WWN Id Type : 0 Device Identifier: "" Device Type : SDT_TAPE NetBackup Drive Type: 10 Removable : Yes Device Supports: SCSI-6 Flags : 0x0 Reason: 0x0
The changer is not only reporting a duplicate serial number, but also an extra drive, that I think does not exist. That is, you really have one physical drive, but the library seems to think it has two ...
I'm with Marianne, looks like a library config issue, at least at the moment ...
Martin
07-06-2011 07:40 AM
Thanks a lot for your very professional help so far. I really appreciate it.
You're both right, of course, and I feel a bit sheepish that I didn't see the second drive in the output I posted above.
The library is indeed able to use a second drive, but the model we've ordered has only one drive built in.
I'll take a closer look at the configuration of the library tomorrow - it's a bit hectical today - and let you know if I was able to prevent the library of reporting the not available second drive to the operating system.
I'm very confident, that this is the root of the problem.
Thanks,
Matthias
07-06-2011 11:26 AM
This part :
Device Type : SDT_CHANGER
NetBackup Robot Type: 8
Removable : Yes
Device Supports: SCSI-5
Number of Drives : 2
Number of Slots : 48
Number of Media Access Ports: 0
Drive 1 Serial Number : "HU1115G3DC"
Drive 2 Serial Number : "HU1115G3DC"
Flags : 0x0
Reason: 0x0
from the changer section, is for certain reported by the library not NBU - so in a nutshell, this is not a NBU issue ... ;o)
Let us know how you get on.
Martin