Video Screencast Help

Solaris 10 Media Server cannot longer see the tape drives

Created: 14 Oct 2013 • Updated: 16 Oct 2013 | 7 comments
This issue has been solved. See solution.

Hi All,

We have an HP ESL322e  TapeLibrary with several media servers connected to it. Recently HP update the TL with the new firmware, somehow one media server cannot recognized the tapedrive anymore. This server is running Solaris 10 (BTW all master and media servers running NBU 7.5.0.4).

When I did the  the cfgadm-al | grep tape, it can see all the tape drives. I did some test put the tape direct to each of the 4 drives and did a tar test, running fine, but if I run the NBU utility "sgscan all" , I couldn't see the tape drives at all (see bellow). I believe because of the changes in the TL there could be a change it the drives mapping to the Solaris. How can I put it back so it can be recognized by sgscan?

Some about this server

We never did any change on the EBS6, before the firmware update  was running fine (ebs6 already in production for several month)

If I put the tape directly to to the drives (each of the 4 drives, drive 11 to drive 14) I can do the direct "tar" command to the drives    

There is a utility from symantec called sgscan, it doesn't see the drives     

The Test I did (we have a similar configuration media server called ebs12 as comparison)

root@ebs6-bck # cfgadm -al | grep tape

c8::201f001321443a6c           tape         connected    configured   unknown

c8::2022001321443a6c           tape         connected    configured   unknown

c15::2025001321443a6c          tape         connected    configured   unknown

c15::2028001321443a6c          tape         connected    configured   unknown

root@ebs6-bck #

root@ebs6-bck # /usr/openv/volmgr/bin/sgscan all

#

#WARNING: detected StorEdge Network Foundation connected devices not in

#         SG configuration file:

#

#    Device World Wide Port Name 201f001321443a6c

#    Device World Wide Port Name 2022001321443a6c

#    Device World Wide Port Name 2025001321443a6c

#    Device World Wide Port Name 2028001321443a6c

#

#    See /usr/openv/volmgr/NetBackup_DeviceConfig_Guide.txt chapter

#    "Special configuration for "Sun StorEdge Network Foundation" HBA/Driver"

#    for information on how to use sg.build and sg.install to

#    configure these devices

#

root@ebs6-bck #

root@ebs12-bck # /usr/openv/volmgr/bin/sgscan all

#

#WARNING: detected StorEdge Network Foundation connected devices not in

#         SG configuration file:

#

#    Device World Wide Port Name 50060e801034235b

#    Device World Wide Port Name 50060e8010342353

#

#    See /usr/openv/volmgr/NetBackup_DeviceConfig_Guide.txt chapter

#    "Special configuration for "Sun StorEdge Network Foundation" HBA/Driver"

#    for information on how to use sg.build and sg.install to

#    configure these devices

#

/dev/sg/c0tw50050840440cd10el0: Tape (/dev/rmt/0): "HP      Ultrium 5-SCSI"

/dev/sg/c0tw50050840440cd112l0: Tape (/dev/rmt/1): "HP      Ultrium 5-SCSI"

/dev/sg/c0tw50050840440cd116l0: Tape (/dev/rmt/2): "HP      Ultrium 5-SCSI"

/dev/sg/c0tw50060e8006d84502l0: Disk (???): "HITACHI OPEN-V      -SUN"

/dev/sg/c0tw50060e8006d84502l1: Disk (???): "HITACHI OPEN-V      -SUN"

/dev/sg/c0tw50060e8006d84512l0: Disk (???): "HITACHI OPEN-V      -SUN"

/dev/sg/c0tw50060e8006d84512l1: Disk (???): "HITACHI OPEN-V      -SUN"

/dev/sg/c1tw50050840440cd102l0: Tape (/dev/rmt/3): "HP      Ultrium 5-SCSI"

/dev/sg/c1tw50050840440cd106l0: Tape (/dev/rmt/4): "HP      Ultrium 5-SCSI"

/dev/sg/c1tw50050840440cd10al0: Tape (/dev/rmt/5): "HP      Ultrium 5-SCSI"

root@ebs12-bck #

Operating Systems:

Comments 7 CommentsJump to latest comment

Marianne's picture

It is possible that persistent binding was not done between hba and OS, causing device names to change when server is rebooted.

Do the following:

# cd /usr/openv/volmgr/bin/driver
# /usr/openv/volmgr/bin/sg.build all

Install the new sg driver configuration:

# /usr/bin/rm -f /kernel/drv/sg.conf
# /usr/openv/volmgr/bin/driver/sg.install

Check/verify config:

# /usr/openv/volmgr/bin/sgscan

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

SOLUTION
mph999's picture

On step 7 of the guide, do not use -ml and -m options.
Or just follow mariannes steps which should work fine.

Regards,  Martin
 
Setting Logs in NetBackup:
http://www.symantec.com/docs/TECH75805
 
Marianne's picture

Strange that we respond immediately after the post, and then.... no response from the OP!

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

Iwan Tamimi's picture

Hi Marianne, mph999, Efi G,

Thank you for the tip , I will try it today I will let you know the result.

I am sorry for my slow response because yeserday here was a public holiday.

Regards,

Iwan

Iwan Tamimi's picture

Hi Marianne, mph999, Efi G,

I successfully add back the drives. Thank you very much especially Marianne.

Regards,

Iwan Tamimi

Marianne's picture

Please find out make/model of hba in this server, then go to manufacturer's web site for persistent binding info. 

Without persistent binding between hba and OS, the same may happen next time the media server is rebooted.

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