NetBackup unable to detect Tape drive

[NikitaC]

Hi All ,

Netbackup is not able to detect tape drive , below is output of scan command :- 

But I am Able to see the tape drive and medium changer in device manager  , Please help to fix the issue .

Server :- windows 2008
Netbackup version :- 7.5

************************************************************
*********************** SDT_TAPE    ************************
*********************** SDT_CHANGER ************************
************************************************************
------------------------------------------------------------
Device Name  : "Changer0"
Passthru Name: "Changer0"
Volume Header: ""
Port: 1; Bus: 0; Target: 6; LUN: 1
Inquiry    : "DELL    PV-124T         0063"
Vendor ID  : "DELL    "
Product ID : "PV-124T         "
Product Rev: "0063"
Serial Number: "CK9HB30203"
WWN          : ""
WWN Id Type  : 0
Device Identifier: "DELL    PV-124T         CK9HB30203"
Device Type    : SDT_CHANGER
NetBackup Robot Type: 8
Removable      : Yes
Device Supports: SCSI-2
Number of Drives : 1
Number of Slots  : 8
Number of Media Access Ports: 0
Drive 1 Serial Number      : "1210411960"
Flags : 0x0
Reason: 0x0

[RiaanBadenhorst]

Device manager is known to show devices even if they're not there. try to reboot and then check again.

[sdo]

If FC, is the tape drive itself zoned to the server FC HBA WWPN?

Or is tape drive SAS, or SCSI?

If FC, have you tried 'resetting' the HBA card using the HBA tools which came with the vendor's HBA card?

Can the same HBA vendor management tool see the tape drive?

Does Windows Device Manager see the tape drive?

All of the above have to be in place before 'scan' will see the tape drive.

[NikitaC]

ATL is connected to server throguh scsi cable .  

I reboot the server also but didnt help .

[Marianne]

scan will show devices that respond to scsi_commands. How is tape drive showing up in Device Manager? Which drivers installed for tape drive?

[sdo]

Have you confirmed:

1) That the TL is supported for use with the SCSI HBA?

2) That the SCSI HBA is supported for use with the OS?

3) The the SCSI HBA BIOS is up to date - or at least at the highest version supported by the TL?

4) That the SCSI HBA firmware is up to date - or at least at the highest version supported by the TL?

5) The that SCSI HBA driver is up to date - or at least at the highest version supported by the TL?

.

SCSI is quite old.  Some older SCSI HBAs were quite specific to O/S version.

6) Are you trying to re-use some old kit?

7) Is your SCSI HBA self terminating?

8) Is the TL self SCSI terminating?

9) Got the right mix of LVD and HVD SCSI?

10) Got the right mix/combination of SCSI speeds?

11) Got the right mix/combination of SCSI 'bit-ness' aka 'bus-width' ?

12) Some SCSI HBAs reserve LUN 0 and/or LUN 7 and/or LUN 15 for their own internal addressing - and so if you add a tape drive with SCSI address 7, then it won't be seen by the O/S.   So, make sure that all of the 'devices' on teh SCSI chain/bus have unique LUN numbers - and in really old kit this was done with dip-switches or a rotary dial.

[Arshad_Khateeb]

- You might need to delete tape drives from devices, restart nbu and try re-running the Wizard.

- You can also try to delete the drives detected in Device Manager. Refresh Device Manager to find the drives attached to it. Come to NBU, delete any old entries for tape drives under devices, restart nbu and run the Wizard.

- Try using CLI to detect the tape drives for NBU.

[sdo]

One tape drive shows up in Windows Device Manager.

Show this again:

> scan -changer

> scan -tape

[NikitaC]

Until last week tape drive was working fine , 

when I checked in device manager the tape drive was showing in others , when tried to updated the drivers it said drivers are up to date .

then I
rebooted the tape library
rebooted  the server
uninstalled the tape drive and medium changer form device manager and re-scanned them , now I can see the tape drive under tape drives but unable to config in netbackup .

while running NetBackupTapeDeviceDriverInstall_273039 get error massage that install symantec product before you install drivers .

Tape drive drivers :- IBM corporation drivers

I have not checked SCSI related things yet , Should I check that also ?

[NikitaC]

We have only tape drive in autoloader

************************************************************
*********************** SDT_CHANGER ************************
************************************************************
------------------------------------------------------------
Device Name  : "Changer0"
Passthru Name: "Changer0"
Volume Header: ""
Port: 1; Bus: 0; Target: 6; LUN: 1
Inquiry    : "DELL    PV-124T         0063"
Vendor ID  : "DELL    "
Product ID : "PV-124T         "
Product Rev: "0063"
Serial Number: "CK9HB30203"
WWN          : ""
WWN Id Type  : 0
Device Identifier: "DELL    PV-124T         CK9HB30203"
Device Type    : SDT_CHANGER
NetBackup Robot Type: 8
Removable      : Yes
Device Supports: SCSI-2
Number of Drives : 1
Number of Slots  : 8
Number of Media Access Ports: 0
Drive 1 Serial Number      : "1210411960"
Flags : 0x0
Reason: 0x0
 
C:\Users\310156466>scan -tape
************************************************************
*********************** SDT_TAPE    ************************
************************************************************

[sdo]

Try this attached script to list tape drives, save as 'list-tape-drives.vbs', then run from a DOS/cmd box, using:

> cscript list-tape-drives.vbs

[mph999]

Odd - I'm wondering if the drive has developed a fault.

scan isn't really a NBU command, I know we (Symnatec) provide it, but all it does is 'scsi query' each drive detected by the OS.  It even works with NBU services stopped.

This means, to be blunt that there are no settings in NBU or anywhere else that can be adjusted, it should just work.

When it doesn't, it usually means that the OS can't see the drive, I appreciate in this case that is not the cause as the OS clearly sees the drive in Device Manager.

Other causes :

Firmware (had this the other day with a customer, all drive worked in scan apart from one, it was a firmware issue)

Tape driver

HBA issues (including firmware) or SCSI card in your case

Now, given yours was working, and now doesn't, it's unlikely to be firmware or driver as I don't think you mention that these had been changed between in working and not working - hence my thoughts that maybe a fault has develped somewhere.

I suspect that either the drive isn't responding to the scsi command that scan is sending, or it is responding, but the response isn't getting back to us.

You've made a good start, removing and reinstalling etc ... that often fixes things if something has got a bit confused somewhere.  Drivers and formware a worth trying, I don;t think that will be the cause, but it's easy enought to do, and sometimes despite opposition to the idea, it can be justified just to prove the point and rule it out as a possibe cause.  

Rule 1 of troubleshooting:

Anything is a possible cause until it is proven not to be (and proven doesn't mean thinking it can't be that so I'll not check it).

NBU does use scan to configure drives - once configured, we don't use it so ....

If you configure the drive manualy you may find that it works.  Ok, not perfect, but it gets things running for you and investigations can continue separately.

Martin

[mph999]

Also,  change the scsi terminator, if yu have done so, change it again (yes, I once replaced a faulty terminator with another faulty terminator ... ).

Have you power cycled the drive ?

M

[Marianne]

NBU device drivers are for 32-bit OS only.

For 64-bit OS, only the vendor drivers are supported.

[Michael_G_Ander]

Seems to me that you are missing the Tape Symbolic Name and Tape Driver Parameters tabs on the tape drive properties.

The tape drive driver might not be loaded correctly, it can some times be solved by Update Driver and then point to the drivers sys file under Windows\System32\Drivers. Have seen this on IBM 3580 LTO5 tape drives on Windows 2008.

Think Netbackup still uses the Symbolic Name (device file) under the covers

[sdo]

Good call.

I'm curious to see whether that script would have hightlighted the lack of a symbolic name.

[NikitaC]

here is output of the script  :-

C:\Users\310156466\Desktop>cscript list-tape-drives.vbs
Microsoft (R) Windows Script Host Version 5.8
Copyright (C) Microsoft Corporation. All rights reserved.
 
Port Number,Bus Number,Target Id,LUN,DeviceType,DeviceName,Identifier,SerialNumber
1,0,6,0,TapePeripheral,,IBM     ULTRIUM-TD3     85P8,1210411960

I delete the tape drive from NBU cmd and tried to configure it and got this

C:\Users\310156466>tpconfig -add -drive -type HCART3 -port 1 -bus 0 -target 6 -lun 0 -asciiname IBM.ULTRIUM-TD3.001 -index 1 -shared no -drstatus UP -
robot 0 -robtype HCART3 -robdrnum 1  -scsi_protection SR
No compatible device is registered at these SCSI coordinates

[sdo]

Noticed this in the script output:

1,0,6,0,TapePeripheral,,IBM     ULTRIUM-TD3     85P8,1210411960

...i.e. the ',,' - which shows that the script was unable to report a DeviceName.  So, it looks like Michael is on to something.

Have you checked Windows Device Manager entry for the tape tape drive to see if it has a 'Name'?

[NikitaC]

this Is what I got .  IBM ULTRIUM-TD3

there is no opetion reboot the tape drive , so we rebooted the library .

[sdo]

There should be a "Device Name" attribute too, or something like a "Windows Device / Symbolic Name" - sorry, but I don't have access to a system with a working drive to check right now.  Maybe later.  Unless someone else can step in?