Veritas-bu

[Veritas-bu] Netbackup Not Seeing My Tape Drive

2003-10-02 16:06:18
Subject: [Veritas-bu] Netbackup Not Seeing My Tape Drive
From: MarkTaylor AT financial.wellsfargo DOT com (Taylor, Mark)
Date: Thu, 2 Oct 2003 15:06:18 -0500
You must be using the Sun branded Q-Logic cards. We had the exact same
issue, and worked with Veritas support for about 2 weeks. Here is the
procedure that we now use whenever setting up a Master or Media server on
Solaris. Works every time now!!! I can provide the files if needed, but I
did not want to attach them to this email. Tell me if that is proper or not
for this group.

Mark Taylor
Enterprise Storage and Backup Administration
Wells Fargo Financial Information Services Group
MAC: F4030-033
Desk: 515.557.7083
Pager: 515.849.4346
marktaylor AT financial.wellsfargo DOT com

############################################################################
###############
NOTE:  the remainder of the install procedure is specific for servers with
the Qlogic HBAs installed.  Other HBAs should be able to see the drives
using their normal configuration procedures.

I.      Install correct configuration files in /usr/openv/volmgr/bin/driver.
These files are found in /apps/netbackup/netbkup_34_2_conf_files and are
named driver_<filename>
A.      st.conf
B.      sg.conf
C.      sg.links
II.     Install correct configuration files in /kernel/drv.  These files are
found in /apps/netbackup/netbkup_34_2_conf_files and are named
kernel_drv_<filename>
A.      st.conf
III.    Make the OS aware of the devices
A.      Run the command "devfsadm" to make the OS aware of the devices 
B.      Run the command "cfgadm" to configure the devices 
IV.     Install the sg driver.
A.      Remove the old sg driver by running the commands
1.      mv /kernel/drv/sg.conf /kernel/drv/sg.conf.<date>
2.      rem_drv sg
B.      Install the new sg driver by running the script 
1.      /usr/openv/volmgr/bin/driver/sg.install
V.      Verify the tape drives are visible by running the script 
(i)     /usr/openv/volmgr/bin/sgscan tape
NOTE:  you should see ten tape drives
############################################################################
##############




-----Original Message-----
From: Pete Akre [mailto:PAkre AT JNI DOT com]
Sent: Thursday, October 02, 2003 1:16 PM
To: 'Darren Dunham'
Cc: 'veritas-bu AT mailman.eng.auburn DOT edu'
Subject: RE: [Veritas-bu] Netbackup Not Seeing My Tape Drive


Thanks for the info, I sure am learning alot. But mine show as: 0cbn ->
../../devices/pci@1f,2000/SUNW,jfca@1,1/fp@0,0/st@w500507630061254d,0:cbn.
So how would I setup my conf files to handle this weird number? Would I just
make the target w500507630061254d? Is that even valid?

Thanks

Peter Akre

-----Original Message-----
From: Darren Dunham [mailto:ddunham AT taos DOT com]
Sent: Thursday, October 02, 2003 11:07 AM
To: Pete Akre
Subject: Re: [Veritas-bu] Netbackup Not Seeing My Tape Drive


> 
> Here's another ignorant question. How do I know what target address to use
> for this tape drive? I have arbitrarily created entries from 0-20 with no
> effect.

That depends on your connection adapter and the driver.

For a scsi drive, the adapter will map the scsi target to the t# in the
device path.

For a fiber adapter, the adapter has several choices, but generally it
will map a single fiber WWPN to a target number.  The driver can usually
do it dynamically (pick a low number), or staticly (create an explicit
mapping within the driver configuration file).

However, you say you already see (and can access) the devices via
/dev/rmt/*.  Just do an expansion of one of them..

lrwxrwxrwx   1 root     root          45 Mar 11  2003 /dev/rmt/8cbn ->
../../devices/pci@6,2000/JNI,FCE@1/st@2,0:cbn

The "@2" means that this particular drive is on target 2 for this
adapter.


-- 
Darren Dunham                                           ddunham AT taos DOT com
Unix System Administrator                    Taos - The SysAdmin Company
Got some Dr Pepper?                           San Francisco, CA bay area
         < This line left intentionally blank to confuse you. >