- VOX
- Data Protection
- NetBackup
- NetBackup unable to detect Tape drive
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Mute
- Printer Friendly Page
NetBackup unable to detect Tape drive
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-12-2017 12:42 PM
Hi guys,
After replacing a failed tape drive, we are unable to detect the new tape drive.
Env : Solaris10 Netbackup 7.5.0.4
Please find some outputs bellow :
bash-3.2# tpconfig -d
Id DriveName Type Residence
Drive Path Status
****************************************************************************
0 HP.ULTRIUM4-SCSI.000 hcart TLD(1) DRIVE=1
/dev/rmt/0cbn UP
Currently defined robotics are:
TLD(1) robotic path = /dev/sg/c0t4l1
EMM Server = mqbks1o
bash-3.2# /usr/openv/volmgr/bin/tpautoconf -report_disc
bash-3.2# /usr/openv/netbackup/bin/admincmd/bpstulist -U
Label: mqbks1o-hcart-robot-tld-0
Storage Unit Type: Media Manager
Host Connection: mqbks1o
Number of Drives: 2
On Demand Only: no
Max MPX/drive: 2
Density: hcart - 1/2 Inch Cartridge
Robot Type/Number: TLD / 0
Max Fragment Size: 1048575 MB
Label: mqbks1o-hcart-robot-tld-1
Storage Unit Type: Media Manager
Host Connection: mqbks1o
Number of Drives: 1
On Demand Only: no
Max MPX/drive: 1
Density: hcart - 1/2 Inch Cartridge
Robot Type/Number: TLD / 1
Max Fragment Size: 1048576 MB
Label: mqbks1o-hcart
Storage Unit Type: Media Manager
Host Connection: mqbks1o
Number of Drives: 1
On Demand Only: no
Max MPX/drive: 1
Density: hcart - 1/2 Inch Cartridge
Robot Type: (not robotic)
Max Fragment Size: 1048576 MB
bash-3.2# tpautoconf -report_disc
bash-3.2# tpautoconf -t
TPAC60 HP Ultrium 4-SCSI B56W HU194277DB -1 -1 -1 -1 /dev/rmt/0cbn - -
bash-3.2# tpautoconf -r
TPAC60 HP MSL G3 Series G.30 0743BR1102 -1 -1 -1 -1 /dev/sg/c0t4l1 - -
bash-3.2# scan
************************************************************
*********************** SDT_TAPE ************************
*********************** SDT_CHANGER ************************
************************************************************
------------------------------------------------------------
Device Name : "/dev/rmt/0cbn"
Passthru Name: "/dev/sg/c1t4l0"
Volume Header: ""
Port: -1; Bus: -1; Target: -1; LUN: -1
Inquiry : "HP Ultrium 4-SCSI B56W"
Vendor ID : "HP "
Product ID : "Ultrium 4-SCSI "
Product Rev: "B56W"
Serial Number: "HU194277DB"
WWN : ""
WWN Id Type : 0
Device Identifier: ""
Device Type : SDT_TAPE
NetBackup Drive Type: 3
Removable : Yes
Device Supports: SCSI-5
Flags : 0x0
Reason: 0x0
------------------------------------------------------------
Device Name : "/dev/sg/c0t4l1"
Passthru Name: "/dev/sg/c0t4l1"
Volume Header: ""
Port: -1; Bus: -1; Target: -1; LUN: -1
Inquiry : "HP MSL G3 Series G.30"
Vendor ID : "HP "
Product ID : "MSL G3 Series "
Product Rev: "G.30"
Serial Number: "0743BR1102"
WWN : ""
WWN Id Type : 0
Device Identifier: "HP MSL G3 Series 0743BR1102"
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 : "HU194277DB"
Drive 2 Serial Number : "HUE1203AGD"
Flags : 0x0
Reason: 0x0
bash-3.2# sgscan
/dev/sg/c0t0l0: Disk (/dev/rdsk/c0t0d0): "FUJITSU MBD2147RC"
/dev/sg/c0t1l0: Disk (/dev/rdsk/c0t1d0): "FUJITSU MBD2147RC"
/dev/sg/c0t2l0: Disk (/dev/rdsk/c0t2d0): "FUJITSU MBD2147RC"
/dev/sg/c0t3l0: Disk (/dev/rdsk/c0t3d0): "SEAGATE ST914603SSUN146G"
/dev/sg/c0t4l0: Cdrom: "MAT**bleep**ADVD-RAM UJ875AS"
/dev/sg/c0t4l1: Changer: "HP MSL G3 Series"
/dev/sg/c1t4l0: Tape (/dev/rmt/0): "HP Ultrium 4-SCSI"
bash-3.2#
bash-3.2#
bash-3.2# scan -changer
************************************************************
*********************** SDT_CHANGER ************************
************************************************************
------------------------------------------------------------
Device Name : "/dev/sg/c0t4l1"
Passthru Name: "/dev/sg/c0t4l1"
Volume Header: ""
Port: -1; Bus: -1; Target: -1; LUN: -1
Inquiry : "HP MSL G3 Series G.30"
Vendor ID : "HP "
Product ID : "MSL G3 Series "
Product Rev: "G.30"
Serial Number: "0743BR1102"
WWN : ""
WWN Id Type : 0
Device Identifier: "HP MSL G3 Series 0743BR1102"
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 : "HU194277DB"
Drive 2 Serial Number : "HUE1203AGD"
Flags : 0x0
Reason: 0x0
Any suggestion please ?
Thanks,
Jules
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-12-2017 01:21 PM
These all look like Netbackup commands. Do OS commands see the tape drive?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-12-2017 04:36 PM - edited 04-12-2017 04:38 PM
The only command you need is scan ….
It shows what the OS sees, by simply sending scsi commands to the devices seen by the OS and waiting for a reply.
We see one tape drive and one robot. The robot has two drives, the drive with serial number HUE1203AGD is not seen by the OS.
You therefore have an issue between the OS and the tape drive, nothing to do with NetBackup, and no NetBackup commands are going to fix this.
(I deleted a few scan lines just to make it smaller)
bash-3.2# scan
-----------------------------------------------------------
Device Name : "/dev/rmt/0cbn"
Passthru Name: "/dev/sg/c1t4l0"
Inquiry : "HP Ultrium 4-SCSI B56W"
Vendor ID : "HP "
Product ID : "Ultrium 4-SCSI "
Serial Number: "HU194277DB"
WWN : ""
WWN Id Type : 0
Device Identifier: ""
Device Type : SDT_TAPE
------------------------------------------------------------
Device Name : "/dev/sg/c0t4l1"
Passthru Name: "/dev/sg/c0t4l1"
Inquiry : "HP MSL G3 Series G.30"
Vendor ID : "HP "
Product ID : "MSL G3 Series "
Serial Number: "0743BR1102"
WWN : ""
WWN Id Type : 0
Device Identifier: "HP MSL G3 Series 0743BR1102"
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 : "HU194277DB"
Drive 2 Serial Number : "HUE1203AGD"
Flags : 0x0
Reason: 0x0
As a starting point, I'd suggest to check the zoning.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-12-2017 11:23 PM
You could also potentially use the HBA utility to check what is visible, either sansurfer or HBAnywhere depending on the HBA brand.
As it is Solaris, cfgadm -al -o show_FCP_dev is another way to see what is visible.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-13-2017 06:33 AM - edited 04-13-2017 06:36 AM
Many thanks for your reply, I appreciate.
Nevertheless, I am not sure but I think that it is a direct SAS connexion, I'll have to check on site. The replacement has been made by an external guy.
I'll keep you inform.
Thx.
bash-3.2# cfgadm -al
Ap_Id Type Receptacle Occupant Condition
SB0 System_Brd connected configured ok
SB0::cpu0 cpu connected configured ok
SB0::memory memory connected configured ok
SB0::pci0 io connected configured ok
SB0::pci1 io connected configured ok
SB0::pci8 io connected configured ok
c0 scsi-sas connected configured unknown
c0::dsk/c0t0d0 disk connected configured unknown
c0::dsk/c0t1d0 disk connected configured unknown
c0::dsk/c0t2d0 disk connected configured unknown
c0::dsk/c0t3d0 disk connected configured unknown
c0::dsk/c0t4d0 CD-ROM connected configured unknown
c0::sg/c0t0l0 unknown connected configured unknown
c0::sg/c0t1l0 unknown connected configured unknown
c0::sg/c0t2l0 unknown connected configured unknown
c0::sg/c0t3l0 unknown connected configured unknown
c0::sg/c0t4l0 unknown connected configured unknown
c1 scsi-bus connected configured unknown
c1::rmt/0 tape connected configured unknown
c1::scsi/changer/c1t4d1 med-changer connected configured unknown
c1::sg/c0t4l1 unknown connected configured unknown
c1::sg/c1t4l0 unknown connected configured unknown
c2 scsi-bus connected configured unknown
c2::sg8 unknown connected configured unknown
c2::st1 tape connected configured unknown
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-13-2017 06:59 AM
OK, that is a little less common these days, but still, the OS has to see the device correctly before NBU can do anything with it.
scan is a veritas command, but really is only sending scsi inquire commands to any device seen by the OS.
As an alternative, cfgadm, as mentioned before should still show devices, though you may need only cfgadm -al
It could be worth rebooting the server first, that often fixes issues such as this.
- Final error: 0xe00095a7 - The operation failed because the vCenter or ESX server reported that the in Backup Exec
- Error Backup Snapshot Vmware in NetBackup
- Unable to consolidate Virtual Machine Disks (4275) in NetBackup
- Unable to login, status: 537. Connection to the NetBackup database was not successful. in NetBackup
- Want to change old datadomain image ownership to new data domain system in Netbackup in NetBackup
