MIssing PATH: for drives

Created: 15 Oct 2012 | Updated: 15 Oct 2012 | 6 comments

jounix

This issue has been solved. See solution.

I ahve a LINUX Media server, and the drive path when i run a tpconfig shows missing. How do I get NB to see the paths once again?

Enter option:
Id DriveName           Type   Residence
      Drive Path                                                       Status
****************************************************************************
1   Sep1-71              hcart2 TLD(3) DRIVE=71
      MISSING_PATH:4:0:0:2:SG11029122                                  DOWN
2   Sep1-70              hcart2 TLD(3) DRIVE=70
      MISSING_PATH:4:0:0:1:SG11029121                                  DOWN
3   Sep1-84              hcart2 TLD(3) DRIVE=84
      MISSING_PATH:2:0:0:3:SG11029135                                  UP
4   Sep1-83              hcart2 TLD(3) DRIVE=83
      MISSING_PATH:2:0:0:2:SG11029134                                  UP
5   Sep1-82              hcart2 TLD(3) DRIVE=82
      MISSING_PATH:2:0:0:1:SG11029133                                  DOWN
6   Sep1-69              hcart2 TLD(3) DRIVE=69
      MISSING_PATH:4:0:0:0:SG11029120                                  DOWN
7   Sep1-81              hcart2 TLD(3) DRIVE=81
      MISSING_PATH:2:0:0:0:SG11029132                                  DOWN

Currently defined robotics are:
TLD(3) robot control host = nbuf1a

EMM Server = nbuf1a

Discussion Filed Under:

Backup and Recovery, NetBackup - 7.1.x and Earlier, NetBackup, Backing Up, Basics, Best Practice, Compatibility, Configuring, Documentation, Error messages, Installing, Managing Backup Devices, Performance, Recovering, Tip/How to, Troubleshooting

Comments RSS Feed

Comments 6 Comments • Jump to latest comment

jounix

MIssing PATH: for drives - Comment:15 Oct 2012 : Link

Enter option:
frux0273:/usr/openv/volmgr/bin # /usr/openv/volmgr/bin/tpautoconf -report_disc
======================= Missing Device (Drive) =======================
Drive Name = Sep1-84
Drive Path = MISSING_PATH:2:0:0:3:SG11029135
Inquiry = "HP      Ultrium 4-SCSI R500"
Serial Number = SG11029135
TLD(3) definition Drive = 84
Hosts configured for this device:
Host = frux0273
======================= Missing Device (Drive) =======================
Drive Name = Sep1-83
Drive Path = MISSING_PATH:2:0:0:2:SG11029134
Inquiry = "HP      Ultrium 4-SCSI R500"
Serial Number = SG11029134
TLD(3) definition Drive = 83
Hosts configured for this device:
Host = frux0273
======================= Missing Device (Drive) =======================
Drive Name = Sep1-82
Drive Path = MISSING_PATH:2:0:0:1:SG11029133
Inquiry = "HP      Ultrium 4-SCSI R500"
Serial Number = SG11029133
TLD(3) definition Drive = 82
Hosts configured for this device:
Host = frux0273
======================= Missing Device (Drive) =======================
Drive Name = Sep1-81
Drive Path = MISSING_PATH:2:0:0:0:SG11029132
Inquiry = "HP      Ultrium 4-SCSI R500"
Serial Number = SG11029132
TLD(3) definition Drive = 81
Hosts configured for this device:
Host = frux0273
=========== Missing Device or no local control path (Robot) ===========
Defined as robotic TLD(3)
Inquiry = "ADIC    Scalar 10K      R210"
Serial Number = SG11029000
Robot Path = /dev/sg/c0t50l0
Robot Control Host = nbuf1a
Drive = 71, Drive Name = Sep1-71, Serial Number = SG11029122
Hosts configured for this device:
Host = frux0273
======================= New Device (Drive) =======================
Inquiry = "HP      Ultrium 4-SCSI R500"
Serial Number = SG11029123
Drive Path = /dev/nst3
frux0273:/usr/openv/volmgr/bin # ./tpautoconf -replace_drive HP      Ultrium 4-SCSI R500 -path
frux0273:/usr/openv/volmgr/bin #
frux0273:/usr/openv/volmgr/bin #

Marianne van den Berg Trusted Advisor Partner Accredited Certified

MIssing PATH: for drives - Comment:15 Oct 2012 : Link

You need to get the OS to see the 'missing' drives.

Check /var/log/messages for errors, then use this command to check OS connectivity:

# cat /proc/scsi/scsi

Verify NBU sees devices via OS:

# /usr/openv/volmgr/bin/scan

Supporting Storage Foundation and VCS on Unix and Windows as well as NetBackup on Unix and Windows
Handy NBU Links

jounix

MIssing PATH: for drives - Comment:15 Oct 2012 : Link

The OS sees the drives:

[2:0:0:0]    tape    HP       Ultrium 4-SCSI   R500 /dev/st4
[2:0:0:1]    tape    HP       Ultrium 4-SCSI   R500 /dev/st5
[2:0:0:2]    tape    HP       Ultrium 4-SCSI   R500 /dev/st6
[2:0:0:3]    tape    HP       Ultrium 4-SCSI   R500 /dev/st7

[4:0:0:0]    tape    HP       Ultrium 4-SCSI   R500 /dev/st0
[4:0:0:1]    tape    HP       Ultrium 4-SCSI   R500 /dev/st1
[4:0:0:2]    tape    HP       Ultrium 4-SCSI   R500 /dev/st2
[4:0:0:3]    tape    HP       Ultrium 4-SCSI   R500 /dev/st3

I ran the scan, It looks like it sees all 8 drives too:

frux0273:/usr/openv/volmgr/bin # ./scan
************************************************************
*********************** SDT_TAPE    ************************
*********************** SDT_CHANGER ************************
************************************************************
------------------------------------------------------------
Device Name : "/dev/nst7"
Passthru Name: "/dev/sg239"
Volume Header: ""
Port: -1; Bus: -1; Target: -1; LUN: -1
Inquiry    : "HP      Ultrium 4-SCSI R500"
Vendor ID : "HP      "
Product ID : "Ultrium 4-SCSI "
Product Rev: "R500"
Serial Number: "SG11029135"
WWN          : ""
WWN Id Type : 0
Device Identifier: "HP      Ultrium 4-SCSI SG11029135"
Device Type    : SDT_TAPE
NetBackup Drive Type: 3
Removable      : Yes
Device Supports: SCSI-3
Flags : 0x0
Reason: 0x0
------------------------------------------------------------
Device Name : "/dev/nst6"
Passthru Name: "/dev/sg238"
Volume Header: ""
Port: -1; Bus: -1; Target: -1; LUN: -1
Inquiry    : "HP      Ultrium 4-SCSI R500"
Vendor ID : "HP      "
Product ID : "Ultrium 4-SCSI "
Product Rev: "R500"
Serial Number: "SG11029134"
WWN          : ""
WWN Id Type : 0
Device Identifier: "HP      Ultrium 4-SCSI SG11029134"
Device Type    : SDT_TAPE
NetBackup Drive Type: 3
Removable      : Yes
Device Supports: SCSI-3
Flags : 0x0
Reason: 0x0
------------------------------------------------------------
Device Name : "/dev/nst5"
Passthru Name: "/dev/sg237"
Volume Header: ""
Port: -1; Bus: -1; Target: -1; LUN: -1
Inquiry    : "HP      Ultrium 4-SCSI R500"
Vendor ID : "HP      "
Product ID : "Ultrium 4-SCSI "
Product Rev: "R500"
Serial Number: "SG11029133"
WWN          : ""
WWN Id Type : 0
Device Identifier: "HP      Ultrium 4-SCSI SG11029133"
Device Type    : SDT_TAPE
NetBackup Drive Type: 3
Removable      : Yes
Device Supports: SCSI-3
Flags : 0x0
Reason: 0x0
------------------------------------------------------------
Device Name : "/dev/nst4"
Passthru Name: "/dev/sg236"
Volume Header: ""
Port: -1; Bus: -1; Target: -1; LUN: -1
Inquiry    : "HP      Ultrium 4-SCSI R500"
Vendor ID : "HP      "
Product ID : "Ultrium 4-SCSI "
Product Rev: "R500"
Serial Number: "SG11029132"
WWN          : ""
WWN Id Type : 0
Device Identifier: "HP      Ultrium 4-SCSI SG11029132"
Device Type    : SDT_TAPE
NetBackup Drive Type: 3
Removable      : Yes
Device Supports: SCSI-3
Flags : 0x0
Reason: 0x0
------------------------------------------------------------
Device Name : "/dev/nst3"
Passthru Name: "/dev/sg235"
Volume Header: ""
Port: -1; Bus: -1; Target: -1; LUN: -1
Inquiry    : "HP      Ultrium 4-SCSI R500"
Vendor ID : "HP      "
Product ID : "Ultrium 4-SCSI "
Product Rev: "R500"
Serial Number: "SG11029123"
WWN          : ""
WWN Id Type : 0
Device Identifier: "HP      Ultrium 4-SCSI SG11029123"
Device Type    : SDT_TAPE
NetBackup Drive Type: 3
Removable      : Yes
Device Supports: SCSI-3
Flags : 0x0
Reason: 0x0
------------------------------------------------------------
Device Name : "/dev/nst2"
Passthru Name: "/dev/sg234"
Volume Header: ""
Port: -1; Bus: -1; Target: -1; LUN: -1
Inquiry    : "HP      Ultrium 4-SCSI R500"
Vendor ID : "HP      "
Product ID : "Ultrium 4-SCSI "
Product Rev: "R500"
Serial Number: "SG11029122"
WWN          : ""
WWN Id Type : 0
Device Identifier: "HP      Ultrium 4-SCSI SG11029122"
Device Type    : SDT_TAPE
NetBackup Drive Type: 3
Removable      : Yes
Device Supports: SCSI-3
Flags : 0x0
Reason: 0x0
------------------------------------------------------------
Device Name : "/dev/nst1"
Passthru Name: "/dev/sg233"
Volume Header: ""
Port: -1; Bus: -1; Target: -1; LUN: -1
Inquiry    : "HP      Ultrium 4-SCSI R500"
Vendor ID : "HP      "
Product ID : "Ultrium 4-SCSI "
Product Rev: "R500"
Serial Number: "SG11029121"
WWN          : ""
WWN Id Type : 0
Device Identifier: "HP      Ultrium 4-SCSI SG11029121"
Device Type    : SDT_TAPE
NetBackup Drive Type: 3
Removable      : Yes
Device Supports: SCSI-3
Flags : 0x0
Reason: 0x0
------------------------------------------------------------
Device Name : "/dev/nst0"
Passthru Name: "/dev/sg232"
Volume Header: ""
Port: -1; Bus: -1; Target: -1; LUN: -1
Inquiry    : "HP      Ultrium 4-SCSI R500"
Vendor ID : "HP      "
Product ID : "Ultrium 4-SCSI "
Product Rev: "R500"
Serial Number: "SG11029120"
WWN          : ""
WWN Id Type : 0
Device Identifier: "HP      Ultrium 4-SCSI SG11029120"
Device Type    : SDT_TAPE
NetBackup Drive Type: 3
Removable      : Yes
Device Supports: SCSI-3
Flags : 0x0
Reason: 0x0
frux0273:/usr/openv/volmgr/bin #

mph999 Symantec Employee

MIssing PATH: for drives - Comment:15 Oct 2012 : Link

Remove the drives with the missing paths, readd with device wizard. Make sure when you select the media server, also select the robot control host if it is a separate server.

This will restart ltid on both servers, so ensure no jobs are running.

Martin

Regards, Martin

Setting Logs in NetBackup:

http://www.symantec.com/docs/TECH75805

SOLUTION

jounix

MIssing PATH: for drives - Comment:15 Oct 2012 : Link

I removed them all and then ran a tpcautoconf -a... they all showed back in and online. Thanks you so much.

mph999 Symantec Employee

MIssing PATH: for drives - Comment:15 Oct 2012 : Link

Excellent work.

With drive issue, esp missing paths, often easier just to remove them and readd.

Regards, Martin

Setting Logs in NetBackup:

http://www.symantec.com/docs/TECH75805

MIssing PATH: for drives

Comments 6 Comments • Jump to latest comment

Would you like to reply?

Links