nbu new connect to FC tape library how to

[Home_224]

Hi 

My current version is 6.0 MP 4 , the original configuration connect to C4 storage with SCSI interface, now I insert the disk to another same model server to boot up it successful, I do this as I want to configure the netbackup to connect with the new FC IBM tape library, check the command by tar backup is working fine.  Next I want to use the nbu to connect to this library, but I can't export the Java console in different subnet, I would like to know if there is command to remove the old device and add new FC tape library for running backup.   Please advice. 

NBU 6.0 MP4 ,Solaris 9 64 BIT , IBM FC TS3100 

[Home_224]

I try to do below steps: Now time to build drivers. copy sg and st.conf file cd /usr/openv/volmgr/bin/drivers cp sg.conf sg.conf.old cp sg.links sg.links.old cp st.conf st.conf.old -Move kernal sg mv /kernel/drv/sg.conf /kernel/drv/sg.conf.old -remove rm /usr/openv/volmgr/bin/driver/sg.conf rm /usr/openv/volmgr/bin/driver/st.conf rm /usr/openv/volmgr/bin/driver/sg.links Go to /usr/openv/volmgr/bin sg.build all Install /usr/openv/volmgr/bin/driver/sg.install but run tpconfig -l not seem to by netbackup

[Marianne]

Rebuilding sg drivers is not the same as NBU device config.
It simply ensures that sgcan can see devices at OS-level before you do device config.

You can use tpconfig command to delete and add devices.
The command will bring up a text-based menu that is self-explanatory.

[Home_224]

Yes, I already delete the old drive and robot, now run sgscan but only see the internal disk , and can't see the robot.  

#WARNING: detected StorEdge Network Foundation connected devices not in
# SG configuration file:
#
# Device World Wide Port Name 2005000e111639db
# Device World Wide Port Name 2002000e111639db
#
# See /usr/openv/volmgr/MediaMgr_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/c0t0l0: Disk (/dev/rdsk/c1t0d0): "FUJITSU MAT3073N SUN72G"

I can see the c5 and c6 is connect to tape drvie 

root@imduarbak01 # cfgadm -al
Ap_Id Type Receptacle Occupant Condition
c0 scsi-bus connected configured unknown
c0::dsk/c0t0d0 CD-ROM connected configured unknown
c1 scsi-bus connected configured unknown
c1::dsk/c1t0d0 disk connected configured unknown
c1::sg/c0t0l0 unknown connected configured unknown
c1::sg/c0t0l1 unknown connected configured unknown
c1::sg/c0t1l0 unknown connected configured unknown
c1::sg/c0t1l1 unknown connected configured unknown
c1::sg/c0t2l0 unknown connected configured unknown
c1::sg/c0t2l1 unknown connected configured unknown
c1::sg/c0t3l0 unknown connected configured unknown
c1::sg/c0t3l1 unknown connected configured unknown
c1::sg/c0t4l0 unknown connected configured unknown
c1::sg/c0t4l1 unknown connected configured unknown
c1::sg/c0t5l0 unknown connected configured unknown
c1::sg/c0t5l1 unknown connected configured unknown
c1::sg/c0t6l0 unknown connected configured unknown
c1::sg/c0t6l1 unknown connected configured unknown
c2 scsi-bus connected configured unknown
c2::sg/c1t0l0 unknown connected configured unknown
c2::sg/c1t0l1 unknown connected configured unknown
c2::sg/c1t1l0 unknown connected configured unknown
c2::sg/c1t1l1 unknown connected configured unknown
c2::sg/c1t2l0 unknown connected configured unknown
c2::sg/c1t2l1 unknown connected configured unknown
c2::sg/c1t3l0 unknown connected configured unknown
c2::sg/c1t3l1 unknown connected configured unknown
c2::sg/c1t4l0 unknown connected configured unknown
c2::sg/c1t4l1 unknown connected configured unknown
c2::sg/c1t5l0 unknown connected configured unknown
c2::sg/c1t5l1 unknown connected configured unknown
c2::sg/c1t6l0 unknown connected configured unknown
c2::sg/c1t6l1 unknown connected configured unknown
c5 fc-private connected configured unknown
c5::2005000e111639db tape connected configured unknown
c6 fc-private connected configured unknown

[Marianne]

Have you checked that device entries have been created for tape drives in /dev/rmt?

Can you run 'mt -f /dev/rmt/#  status' to ensure that tape drives are operational at OS level?

Herewith 2 TNs on rebuiding sg driver: 

https://www.veritas.com/support/en_US/article.100021141

https://www.veritas.com/support/en_US/doc/23395442-127355766-0/id-SF860116535-127355766

Important to check contents of these files after sg.build:

• /usr/openv/volmgr/bin/driver/st.conf 
• /usr/openv/volmgr/bin/driver/sg.conf
• /usr/openv/volmgr/bin/driver/sg.links

No use carrying on with sg.install if these files have not been updated correctly. 

[Home_224]

Yes, I try to ls -l /dev/rmt/  the FC tape library located the WWN in /dev/rmt/5bn and /dev/rmt/6bn 

lrwxrwxrwx 1 root root 70 May 18 17:01 5b -> ../../devices/pci@1d,700000/SUNW,qlc@1/fp@0,0/st@w2005000e111639db,0:b
lrwxrwxrwx 1 root root 71 May 18 17:01 5bn -> ../../devices/pci@1d,700000/SUNW,qlc@1/fp@0,0/st@w2005000e111639db,0:bn

lrwxrwxrwx 1 root root 72 May 18 17:01 6b -> ../../devices/pci@1d,700000/SUNW,qlc@1,1/fp@0,0/st@w2002000e111639db,0:b
lrwxrwxrwx 1 root root 73 May 18 17:01 6bn -> ../../devices/pci@1d,700000/SUNW,qlc@1,1/fp@0,0/st@w2002000e111639db,0:bn

root@imduarbak01 # more sg.conf
#
# Configuration file for SCSA Generic.
#
name="sg" class="scsi" target=0 lun=0;
name="sg" class="scsi" target=0 lun=1;
name="sg" class="scsi" target=1 lun=0;
name="sg" class="scsi" target=1 lun=1;
name="sg" class="scsi" target=2 lun=0;
name="sg" class="scsi" target=2 lun=1;
name="sg" class="scsi" target=3 lun=0;
name="sg" class="scsi" target=3 lun=1;
name="sg" class="scsi" target=4 lun=0;
name="sg" class="scsi" target=4 lun=1;
name="sg" class="scsi" target=5 lun=0;
name="sg" class="scsi" target=5 lun=1;
name="sg" class="scsi" target=6 lun=0;
name="sg" class="scsi" target=6 lun=1;
root@imduarbak01 # pwd
/usr/openv/volmgr/bin/driver
root@imduarbak01 # more sg.links
# begin SCSA Generic devlinks file - creates nodes in /dev/sg
type=ddi_pseudo;name=sg;addr=0,0; sg/c\N0t0l0
type=ddi_pseudo;name=sg;addr=1,0; sg/c\N0t1l0
type=ddi_pseudo;name=sg;addr=2,0; sg/c\N0t2l0
type=ddi_pseudo;name=sg;addr=3,0; sg/c\N0t3l0
type=ddi_pseudo;name=sg;addr=4,0; sg/c\N0t4l0
type=ddi_pseudo;name=sg;addr=5,0; sg/c\N0t5l0
type=ddi_pseudo;name=sg;addr=6,0; sg/c\N0t6l0
type=ddi_pseudo;name=sg;addr=0,1; sg/c\N0t0l1
type=ddi_pseudo;name=sg;addr=1,1; sg/c\N0t1l1
type=ddi_pseudo;name=sg;addr=2,1; sg/c\N0t2l1
type=ddi_pseudo;name=sg;addr=3,1; sg/c\N0t3l1
type=ddi_pseudo;name=sg;addr=4,1; sg/c\N0t4l1
type=ddi_pseudo;name=sg;addr=5,1; sg/c\N0t5l1
type=ddi_pseudo;name=sg;addr=6,1; sg/c\N0t6l1

#OnStream = 1, 0x36, 0x8000, 0x21658, 4, 0x00, 0x00, 0x00, 0x00, 0;
#

name="st" class="scsi" target=0 lun=0;
name="st" class="scsi" target=1 lun=0;
name="st" class="scsi" target=2 lun=0;
name="st" class="scsi" target=3 lun=0;
name="st" class="scsi" target=4 lun=0;
name="st" class="scsi" target=5 lun=0;
name="st" class="scsi" target=6 lun=0;

#
#In case there are wide tape drives, one can use these targets
#
#name="st" class="scsi" target=8 lun=0;
#name="st" class="scsi" target=9 lun=0;
#name="st" class="scsi" target=10 lun=0;
#name="st" class="scsi" target=11 lun=0;
#name="st" class="scsi" target=12 lun=0;
#name="st" class="scsi" target=13 lun=0;
#name="st" class="scsi" target=14 lun=0;
#name="st" class="scsi" target=15 lun=0;

# This line adds support for Fibre Channel Tapes
name="st" parent="fp" target=0;
root@imduarbak01 # pwd
/kernel/drv

root@imduarbak01 # ../sg.build all
The file ./st.conf should be appended to /kernel/drv/st.conf.
A reboot may be necessary to create any new device files.
Created file ./sg.conf.
Created file ./sg.links.
root@imduarbak01 # scan
************************************************************
*********************** SDT_TAPE ************************
*********************** SDT_CHANGER ************************
*********************** SDT_OPTICAL ************************
************************************************************

After reboot the machine , i can see the sg.conf with update fc

root@imduarbak01 # more sg.conf
# Configuration file for SCSA Generic.
#
name="sg" class="scsi" target=0 lun=0;
name="sg" class="scsi" target=0 lun=1;
name="sg" class="scsi" target=1 lun=0;
name="sg" class="scsi" target=1 lun=1;
name="sg" class="scsi" target=2 lun=0;
name="sg" class="scsi" target=2 lun=1;
name="sg" class="scsi" target=3 lun=0;
name="sg" class="scsi" target=3 lun=1;
name="sg" class="scsi" target=4 lun=0;
name="sg" class="scsi" target=4 lun=1;
name="sg" class="scsi" target=5 lun=0;
name="sg" class="scsi" target=5 lun=1;
name="sg" class="scsi" target=6 lun=0;
name="sg" class="scsi" target=6 lun=1;
name="sg" parent="fp" target=0 lun=0 fc-port-wwn="2005000e111639db";
name="sg" parent="fp" target=0 lun=1 fc-port-wwn="2005000e111639db";
name="sg" parent="fp" target=0 lun=0 fc-port-wwn="2002000e111639db";
name="sg" parent="fp" target=0 lun=1 fc-port-wwn="2002000e111639db";

root@imduarbak01 # more sg.links
# begin SCSA Generic devlinks file - creates nodes in /dev/sg
type=ddi_pseudo;name=sg;addr=0,0; sg/c\N0t0l0
type=ddi_pseudo;name=sg;addr=0,1; sg/c\N0t0l1
type=ddi_pseudo;name=sg;addr=1,0; sg/c\N0t1l0
type=ddi_pseudo;name=sg;addr=1,1; sg/c\N0t1l1
type=ddi_pseudo;name=sg;addr=2,0; sg/c\N0t2l0
type=ddi_pseudo;name=sg;addr=2,1; sg/c\N0t2l1
type=ddi_pseudo;name=sg;addr=3,0; sg/c\N0t3l0
type=ddi_pseudo;name=sg;addr=3,1; sg/c\N0t3l1
type=ddi_pseudo;name=sg;addr=4,0; sg/c\N0t4l0
type=ddi_pseudo;name=sg;addr=4,1; sg/c\N0t4l1
type=ddi_pseudo;name=sg;addr=5,0; sg/c\N0t5l0
type=ddi_pseudo;name=sg;addr=5,1; sg/c\N0t5l1
type=ddi_pseudo;name=sg;addr=6,0; sg/c\N0t6l0
type=ddi_pseudo;name=sg;addr=6,1; sg/c\N0t6l1
type=ddi_pseudo;name=sg;addr=w2005000e111639db,0; sg/c\N0t\A1l0
type=ddi_pseudo;name=sg;addr=w2005000e111639db,1; sg/c\N0t\A1l1
type=ddi_pseudo;name=sg;addr=w2002000e111639db,0; sg/c\N0t\A1l0
type=ddi_pseudo;name=sg;addr=w2002000e111639db,1; sg/c\N0t\A1l1
# end SCSA devlinks

But I run those command , the NBU doesn't know the FC library.

root@imduarbak01 # sgscan -v
#
#WARNING: detected StorEdge Network Foundation connected devices not in
# SG configuration file:
#
# Device World Wide Port Name 2005000e111639db
# Device World Wide Port Name 2002000e111639db
#
# See /usr/openv/volmgr/MediaMgr_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/c0t0l0: Disk (/dev/rdsk/c1t0d0): "FUJITSU MAT3073N SUN72G 1703"
root@imduarbak01 # tpautoconf -t
root@imduarbak01 # scan -tape
************************************************************
*********************** SDT_TAPE ************************
************************************************************
root@imduarbak01 # stopltid
root@imduarbak01 # ltid -v
root@imduarbak01 # May 22 16:14:41 imduarbak01 vmd[1284]: terminating - another daemon already exists (89)

No Entries in the Drive Database
tpconfig -d
Id DriveName Type Residence
Drive Path Status
****************************************************************************

Currently defined robotics are:

EMM Server = imduarbak01

root@imduarbak01 # tpconfig -d
Id DriveName Type Residence
Drive Path Status
****************************************************************************

Currently defined robotics are:

EMM Server = imduarbak01

[Marianne]

So, we can see that sg.build created all the entries.

Did you remember to run sg.install after that? 

[Home_224]

root@imduarbak01 # mt -f /dev/rmt/6bn status
/dev/rmt/6bn: no tape loaded or drive offline
root@imduarbak01 # mt -f /dev/rmt/5bn status
IBM ULT3580-HH6 tape drive:
sense key(0x0)= No Additional Sense residual= 0 retries= 0
file no= 0 block no= 0
root@imduarbak01 #

root@imduarbak01 # more st.conf
name="st" class="scsi" target=0 lun=0;
name="st" class="scsi" target=0 lun=1;
name="st" class="scsi" target=1 lun=0;
name="st" class="scsi" target=1 lun=1;
name="st" class="scsi" target=2 lun=0;
name="st" class="scsi" target=2 lun=1;
name="st" class="scsi" target=3 lun=0;
name="st" class="scsi" target=3 lun=1;
name="st" class="scsi" target=4 lun=0;
name="st" class="scsi" target=4 lun=1;
name="st" class="scsi" target=5 lun=0;
name="st" class="scsi" target=5 lun=1;
name="st" class="scsi" target=6 lun=0;
name="st" class="scsi" target=6 lun=1;
root@imduarbak01 # pwd
/opt/openv/volmgr/bin/driver
root@imduarbak01 # ./sg.install

Copied files to /kernel/drv and to /kernel/drv/sparcv9.

Doing add_drv of the sg driver
May 22 16:27:19 imduarbak01 sg: VERITAS SCSA Generic Revision: 3.5c

Leaving existing sg configuration.
If you wish to update the configuration you need to
rm -f /kernel/drv/sg.conf
and rerun /usr/openv/volmgr/bin/driver/sg.install.

root@imduarbak01 # more st.conf
name="st" class="scsi" target=0 lun=0;
name="st" class="scsi" target=0 lun=1;
name="st" class="scsi" target=1 lun=0;
name="st" class="scsi" target=1 lun=1;
name="st" class="scsi" target=2 lun=0;
name="st" class="scsi" target=2 lun=1;
name="st" class="scsi" target=3 lun=0;
name="st" class="scsi" target=3 lun=1;
name="st" class="scsi" target=4 lun=0;
name="st" class="scsi" target=4 lun=1;
name="st" class="scsi" target=5 lun=0;
name="st" class="scsi" target=5 lun=1;
name="st" class="scsi" target=6 lun=0;
name="st" class="scsi" target=6 lun=1;

Do I need to remove sg.conf then sg.install

[Marianne · Accepted solution]

Did you remember to run sg.install after sg.build?

As long as sgscan is not seeing robot and tape, there is no point in trying to config NBU or looking at tpconfig output. 

[Home_224]

yes, i run the command right now 

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

Copied files to /kernel/drv and to /kernel/drv/sparcv9.

Doing add_drv of the sg driver
Removing old /dev/sg entries.
Editing /etc/devlink.tab...
Copying original /etc/devlink.tab to /etc/devlink.tab.05-22-18-16:36:41.
Added entry in /etc/devlink.tab file.
Made links in /dev/sg
root@imduarbak01 # pwd
/kernel/drv
root@imduarbak01 # cd /usr/openv/volmgr/bin/driver
root@imduarbak01 # more st.conf
name="st" class="scsi" target=0 lun=0;
name="st" class="scsi" target=0 lun=1;
name="st" class="scsi" target=1 lun=0;
name="st" class="scsi" target=1 lun=1;
name="st" class="scsi" target=2 lun=0;
name="st" class="scsi" target=2 lun=1;
name="st" class="scsi" target=3 lun=0;
name="st" class="scsi" target=3 lun=1;
name="st" class="scsi" target=4 lun=0;
name="st" class="scsi" target=4 lun=1;
name="st" class="scsi" target=5 lun=0;
name="st" class="scsi" target=5 lun=1;
name="st" class="scsi" target=6 lun=0;
name="st" class="scsi" target=6 lun=1;

[Home_224]

root@imduarbak01 # sgscan
/dev/sg/c0t0l0: Disk (/dev/rdsk/c1t0d0): "FUJITSU MAT3073N SUN72G"
/dev/sg/c0tw2002000e111639dbl0: Tape (/dev/rmt/6): "IBM ULT3580-HH6"
/dev/sg/c0tw2002000e111639dbl1: Changer: "IBM 3573-TL"
/dev/sg/c0tw2005000e111639dbl0: Tape (/dev/rmt/5): "IBM ULT3580-HH6"
root@imduarbak01 #

After that I can see the tape library on the NBU 

[Home_224]

To summaries the step to NBU know the FC devices.

1. I reboot the server with reboot -- -r 

2. /usr/openv/volmgr/bin/driver ;  more sg.conf  and sg.links  <<<<<<<<<< FC device appear 

3. netbackup stop and start the service 

4. sg.install to build add drv of the sg driver  

5.  rm -f /kernel/drv/sg.conf 

root@imduarbak01 # scan -tape
************************************************************
*********************** SDT_TAPE ************************
************************************************************
------------------------------------------------------------
Device Name : "/dev/rmt/5cbn"
Passthru Name: "/dev/sg/c0tw2005000e111639dbl0"
Volume Header: ""
Port: -1; Bus: -1; Target: -1; LUN: -1
Inquiry : "IBM ULT3580-HH6 H991"
Vendor ID : "IBM "
Product ID : "ULT3580-HH6 "
Product Rev: "H991"
Serial Number: "10WT127994"
WWN : ""
WWN Id Type : 0
Device Identifier: "IBM ULT3580-HH6 10WT127994"
Device Type : SDT_TAPE
NetBackup Drive Type: Not Found(5)
Removable : Yes
Device Supports: SCSI-6
Flags : 0x0
Reason: 0x0
------------------------------------------------------------
Device Name : "/dev/rmt/6cbn"
Passthru Name: "/dev/sg/c0tw2002000e111639dbl0"
Volume Header: ""
Port: -1; Bus: -1; Target: -1; LUN: -1
Inquiry : "IBM ULT3580-HH6 H991"
Vendor ID : "IBM "
Product ID : "ULT3580-HH6 "
Product Rev: "H991"
Serial Number: "10WT130808"
WWN : ""
WWN Id Type : 0
Device Identifier: "IBM ULT3580-HH6 10WT130808"
Device Type : SDT_TAPE
NetBackup Drive Type: Not Found(5)
Removable : Yes
Device Supports: SCSI-6
Flags : 0x0
Reason: 0x0

6. /usr/openv/volmgr/bin/driver/sg.install

7. sgscan <<<<<<<<<<<<<<< able to see the tape library 

8.   sgscan conf -v
Tape device types enabled in the Solaris tape driver, st(7D), configuration file:

All devices recognized by the SCSI Generic (sg) driver:
/dev/sg/c0t0l0: Disk (/dev/rdsk/c1t0d0): "FUJITSU MAT3073N SUN72G 1703"
/dev/sg/c0tw2002000e111639dbl0: Tape (/dev/rmt/6): "IBM ULT3580-HH6 H991" : NOT-IN-ST-CONFIG-FILE
/dev/sg/c0tw2002000e111639dbl1: Changer: "IBM 3573-TL E.60"
/dev/sg/c0tw2005000e111639dbl0: Tape (/dev/rmt/5): "IBM ULT3580-HH6 H991" : NOT-IN-ST-CONFIG-FILE
root@imduarbak01 # tpautoconf -t
TPAC60 IBM ULT3580-HH6 H991 10WT127994 -1 -1 -1 -1 /dev/rmt/5cbn - -
TPAC60 IBM ULT3580-HH6 H991 10WT130808 -1 -1 -1 -1 /dev/rmt/6cbn - -

but the tpconfig -l not show to the information

root@imduarbak01 # tpconfig -l
Device Robot Drive Robot Drive Device Second
Type Num Index Type DrNum Status Comment Name Path Device Path
root@imduarbak01 # tpconfig -d
Id DriveName Type Residence
Drive Path Status
****************************************************************************

Currently defined robotics are:

EMM Server = imduarbak01

[Home_224]

My current version of NBU 6.0 , can I use the 6.5.6 admin console to connect to server. It is easy to manage to the device