cancel
Showing results for 
Search instead for 
Did you mean: 

Unable to determine robot type - drive is recognized as sdt_changer

mtimbol
Level 3
Certified

Master/Media Server - Server 2008

Netbackup ver - 7.5

We have this one media server that backs up to a HP StoreOnce device configured as a virtual tape library. It has been working for the last few months. A week ago, backups started failing.

 

The virtual change and 5 drives show up in the Windows device manager.

 

I deleted the robot and drives and tried to reconfigue it using the Device configuration wizard. The Robot shows up as "unconfigured". The 5 drives show up as Standalone drives. For some reason, one drive aside from being recognized as standalone, is also being recognized as an "unconfigured" robot.

I tried to update the device mappings, the robot is still unrecognized.

The changer and drives show up in the device manager without any exclamation point.

I've tried rebooting the Storeonce device.

Also tried restarting the netbackup services.

I encountered a similar issue once before - https://www-secure.symantec.com/connect/forums/virtual-tape-library-robot-not-detected-netbackup. Tried that and it did not work.

Scan and tpconfig output below.

 

C:\Program Files\Veritas\Volmgr\bin>scan
************************************************************
*********************** SDT_TAPE    ************************
*********************** SDT_CHANGER ************************
************************************************************
------------------------------------------------------------
Device Name  : "Tape0"
Passthru Name: "Tape0"
Volume Header: ""
Port: 5; Bus: 0; Target: 0; LUN: 0
Inquiry    : "HP      Ultrium 5-SCSI  ED51"
Vendor ID  : "HP      "
Product ID : "Ultrium 5-SCSI  "
Product Rev: "ED51"
Serial Number: "CZJ117081V"
WWN          : ""
WWN Id Type  : 0
Device Identifier: "HP      Ultrium 5-SCSI  CZJ117081V"
Device Type    : SDT_TAPE
NetBackup Drive Type: 10
Removable      : Yes
Device Supports: SCSI-3
Flags : 0x0
Reason: 0x0
------------------------------------------------------------
Device Name  : "Tape1"
Passthru Name: "Tape1"
Volume Header: ""
Port: 5; Bus: 0; Target: 1; LUN: 0
Inquiry    : "HP      Ultrium 5-SCSI  ED51"
Vendor ID  : "HP      "
Product ID : "Ultrium 5-SCSI  "
Product Rev: "ED51"
Serial Number: "CZJ117081W"
WWN          : ""
WWN Id Type  : 0
Device Identifier: "HP      Ultrium 5-SCSI  CZJ117081W"
Device Type    : SDT_TAPE
NetBackup Drive Type: 10
Removable      : Yes
Device Supports: SCSI-3
Flags : 0x0
Reason: 0x0
------------------------------------------------------------
Device Name  : "Tape2"
Passthru Name: "Tape2"
Volume Header: ""
Port: 5; Bus: 0; Target: 2; LUN: 0
Inquiry    : "HP      Ultrium 5-SCSI  ED51"
Vendor ID  : "HP      "
Product ID : "Ultrium 5-SCSI  "
Product Rev: "ED51"
Serial Number: "CZJ117081X"
WWN          : ""
WWN Id Type  : 0
Device Identifier: "HP      Ultrium 5-SCSI  CZJ117081X"
Device Type    : SDT_TAPE
NetBackup Drive Type: 10
Removable      : Yes
Device Supports: SCSI-3
Flags : 0x0
Reason: 0x0
------------------------------------------------------------
Device Name  : "Tape3"
Passthru Name: "Tape3"
Volume Header: ""
Port: 5; Bus: 0; Target: 3; LUN: 0
Inquiry    : "HP      Ultrium 5-SCSI  ED51"
Vendor ID  : "HP      "
Product ID : "Ultrium 5-SCSI  "
Product Rev: "ED51"
Serial Number: "CZJ117081Y"
WWN          : ""
WWN Id Type  : 0
Device Identifier: "HP      Ultrium 5-SCSI  CZJ117081Y"
Device Type    : SDT_TAPE
NetBackup Drive Type: 10
Removable      : Yes
Device Supports: SCSI-3
Flags : 0x0
Reason: 0x0
------------------------------------------------------------
Device Name  : "Tape4"
Passthru Name: "Tape4"
Volume Header: ""
Port: 5; Bus: 0; Target: 4; LUN: 0
Inquiry    : "HP      Ultrium 5-SCSI  ED51"
Vendor ID  : "HP      "
Product ID : "Ultrium 5-SCSI  "
Product Rev: "ED51"
Serial Number: "CZJ117081Z"
WWN          : ""
WWN Id Type  : 0
Device Identifier: "HP      Ultrium 5-SCSI  CZJ117081Z"
Device Type    : SDT_TAPE
NetBackup Drive Type: 10
Removable      : Yes
Device Supports: SCSI-3
Flags : 0x0
Reason: 0x0
------------------------------------------------------------
Device Name  : "Tape4"
Passthru Name: "Tape4"
Volume Header: ""
Port: 5; Bus: 0; Target: 5; LUN: 0
Inquiry    : "HP      Ultrium 5-SCSI  ED51"
Vendor ID  : "HP      "
Product ID : "Ultrium 5-SCSI  "
Product Rev: "ED51"
Serial Number: "CZJ117081Z"
WWN          : ""
WWN Id Type  : 0
Device Identifier: "HP      Ultrium 5-SCSI  CZJ117081Z"
Device Type    : SDT_CHANGER
NetBackup Robot Type: Not Found(5)
Removable      : Yes
Device Supports: SCSI-3
Number of Drives : 0
Number of Slots  : 0
Number of Media Access Ports: 0
Flags : 0x0
Reason: 0x0

C:\Program Files\Veritas\Volmgr\bin>tpconfig -d
Id  DriveName           Type   Residence
      SCSI coordinates/Path                                            Status
****************************************************************************

Currently defined robotics are:
  TLD(3)     SCSI coordinates = {5,0,5,0}
  TLD(5)     SCSI coordinates = MISSING_PATH:CZJ117083P

EMM Server = dmausbnecornb1.roche.com.au


C:\Program Files\Veritas\Volmgr\bin>

xxxxxxxxxxxx

It shows Tape4 twice.  As sdt_tape and sdt_changer. How do I delete it as sdt_changer? The robot does not show up.

I tried nbrbutil -dump. The MDS allocations do not show any orphaned drives from this media server.

 

 

 

 

 

 

 

 

 


 

 

9 REPLIES 9

SymTerry
Level 6
Employee Accredited

Hello,

Your robot seems to have a missing path.Try removing the robot and drives from NetBackup and then readding. If you have done this, then also try removing from the OS and and reinstall the drivers. 

While your removing the devices from the OS check for ghost devices: TECH93292

Marianne
Moderator
Moderator
Partner    VIP    Accredited Certified

I would first of all look at the StoreOnce config and ensure all is still fine there.

Have you also deleted devices (medium changer and tape drives) in Windows Device Manager?
Deleting and re-scanning will recreate device entries at OS level.

The output from 'scan' command is showing us what is returned from device SCSI Inquiry.Rescanning devices in NBU won't help - something seems to be wrong with device-level config.

mph999
Level 6
Employee Accredited
Hmm, odd ... My first thoughts are exactly as Mariannes - what is seen in scan is sent from the library/ drives, effectly scan asks, what are you (via an industry standard scsi command) and the device replies, I am a tape drive / I am a changer etc ... I second therefore the recommendation to remove everything completely from NBU and the OS, make sure there are no 'ghost' devices, then put it all back again and see how things look. Not sure whats caused this, as we always saw, issue like this don't just happen something changed - you havent suggested that NBU was changed before the issue, but likewise, you haven't mentioned any changes on the library either (you have to play fair and consider both sides ...).

mtimbol
Level 3
Certified

I see your point about the problem being from the library/drives. Come to think of it, this is the 3rd site we've had this kind of problem. All backing up to a storeonce device configured as VTL. In all 3 instances, we did not make any changes before the problem started.

There are no errors in the storeonce device but I'm thinking it might be an emulation problem.

I've just tried removing the changer and drives from the device manager and re-scanning. Scan results still show "Tape4" showing up twice.

I'll try to see if there is something I can do from the storeonce end.

 

mph999
Level 6
Employee Accredited

Can you configure the VTL to emulate something else ?

If you had a similar issue previously, what did you do to resolve / what area was the issue found to be in ?  

mtimbol
Level 3
Certified

The one we were having problems with was emulating an EML E Series library, LTO5 with 5 drives. I created another just like it but the robot still shows as unconfigured when I try to configure it using the Netbackup wizard.

I tried to create another library, this time emulating an MSL G3 Series (4x48) LTO 5. Same issue. The robot is unconfigured.

The first time I encountered a problem like this, I updated the device mappings.

The second time, is documented here  - https://www-secure.symantec.com/connect/forums/virtual-tape-library-robot-not-detected-netbackup

About reinstalling drivers, there was a time when Netbackup had its own drivers. Am I correct in understanding that for versions, 7.x, we have to use the vendor supplied drivers?

I'm not sure what drivers were installed on these servers as someone else set these up and turned it over to us already working.

Marianne
Moderator
Moderator
Partner    VIP    Accredited Certified

The 'medium changer' in Windows device manager must be left as 'unknown medium changer'. 
This is the Windows driver and is all that is required by NetBackup. No other driver must be installed for the robot.
NBU had 32-bit drivers for tape, but Symantec now recommends to install the vendor drivers.

Please have a look at the  'Virtual Tape Libraries/Drives - Considerations'  in the NBU HCL.
Especially 'Vendor support considerations' and 'Configuration considerations'.

As long as 'scan' reports incorrect robot info, forget about configuring devices in NBU. 

If we look at tpconfig output, it seems that the robot should have a serial number of CZJ117083P, but the scsi enquiry (scan) now shows the same serial number as for Tape4: CZJ117081Z and also 
Number of Drives : 0

Number of Slots  : 0

IMHO, this looks like a config issue on the VTL.

mtimbol
Level 3
Certified

Thanks Marianne. I was starting to think I had to install the drivers for the libraries that the d2d has emulating.

I haven't had time to try to make any changes to the d2d yet. Not much I can do from the web interface but it has a command line interface that I haven't explored yet.

In the meantime, I've directed the backups to go straight to a standalone physical tape drive. Better than nothing.

Marianne
Moderator
Moderator
Partner    VIP    Accredited Certified

More than a month later... 

Have you been able to fix the issue with the VTL?