This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.
------_=_NextPart_001_01C3894C.0DD95E98
Content-Type: text/plain;
charset="iso-8859-1"
Hey Mark,
Not everyone might want this procedure. But I'm interested. Sent it to me?
Thanks a bunch.
Interesting..
Dav
-----Original Message-----
From: Taylor, Mark [mailto:MarkTaylor AT financial.wellsfargo DOT com]
Sent: Friday, October 03, 2003 4:06 AM
To: 'Pete Akre'; 'Darren Dunham'
Cc: 'veritas-bu AT mailman.eng.auburn DOT edu'
Subject: RE: [Veritas-bu] Netbackup Not Seeing My Tape Drive
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. >
_______________________________________________
Veritas-bu maillist - Veritas-bu AT mailman.eng.auburn DOT edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
------_=_NextPart_001_01C3894C.0DD95E98
Content-Type: text/html;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Diso-8859-1">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
5.5.2650.12">
<TITLE>RE: [Veritas-bu] Netbackup Not Seeing My Tape Drive</TITLE>
</HEAD>
<BODY>
<P><FONT SIZE=3D2>Hey Mark,</FONT>
</P>
<P><FONT SIZE=3D2>Not everyone might want this procedure. But I'm =
interested. Sent it to me? Thanks a bunch. </FONT>
<BR><FONT SIZE=3D2>Interesting.. </FONT>
</P>
<P><FONT SIZE=3D2>Dav</FONT>
</P>
<P><FONT SIZE=3D2>-----Original Message-----</FONT>
<BR><FONT SIZE=3D2>From: Taylor, Mark [<A =
HREF=3D"mailto:MarkTaylor AT financial.wellsfargo DOT com">mailto:MarkTaylor@fi=
nancial.wellsfargo.com</A>]</FONT>
<BR><FONT SIZE=3D2>Sent: Friday, October 03, 2003 4:06 AM</FONT>
<BR><FONT SIZE=3D2>To: 'Pete Akre'; 'Darren Dunham'</FONT>
<BR><FONT SIZE=3D2>Cc: 'veritas-bu AT mailman.eng.auburn DOT edu'</FONT>
<BR><FONT SIZE=3D2>Subject: RE: [Veritas-bu] Netbackup Not Seeing My =
Tape Drive</FONT>
</P>
<BR>
<P><FONT SIZE=3D2>You must be using the Sun branded Q-Logic cards. We =
had the exact same</FONT>
<BR><FONT SIZE=3D2>issue, and worked with Veritas support for about 2 =
weeks. Here is the</FONT>
<BR><FONT SIZE=3D2>procedure that we now use whenever setting up a =
Master or Media server on</FONT>
<BR><FONT SIZE=3D2>Solaris. Works every time now!!! I can provide the =
files if needed, but I</FONT>
<BR><FONT SIZE=3D2>did not want to attach them to this email. Tell me =
if that is proper or not</FONT>
<BR><FONT SIZE=3D2>for this group.</FONT>
</P>
<P><FONT SIZE=3D2>Mark Taylor</FONT>
<BR><FONT SIZE=3D2>Enterprise Storage and Backup Administration</FONT>
<BR><FONT SIZE=3D2>Wells Fargo Financial Information Services =
Group</FONT>
<BR><FONT SIZE=3D2>MAC: F4030-033</FONT>
<BR><FONT SIZE=3D2>Desk: 515.557.7083</FONT>
<BR><FONT SIZE=3D2>Pager: 515.849.4346</FONT>
<BR><FONT SIZE=3D2>marktaylor AT financial.wellsfargo DOT com</FONT>
</P>
<P><FONT =
SIZE=3D2>###############################################################=
#############</FONT>
<BR><FONT SIZE=3D2>###############</FONT>
<BR><FONT SIZE=3D2>NOTE: the remainder of the install procedure =
is specific for servers with</FONT>
<BR><FONT SIZE=3D2>the Qlogic HBAs installed. Other HBAs should =
be able to see the drives</FONT>
<BR><FONT SIZE=3D2>using their normal configuration procedures.</FONT>
</P>
<P><FONT SIZE=3D2>I. Install correct =
configuration files in /usr/openv/volmgr/bin/driver.</FONT>
<BR><FONT SIZE=3D2>These files are found in =
/apps/netbackup/netbkup_34_2_conf_files and are</FONT>
<BR><FONT SIZE=3D2>named driver_<filename></FONT>
<BR><FONT SIZE=3D2>A. st.conf</FONT>
<BR><FONT SIZE=3D2>B. sg.conf</FONT>
<BR><FONT SIZE=3D2>C. sg.links</FONT>
<BR><FONT SIZE=3D2>II. Install correct =
configuration files in /kernel/drv. These files are</FONT>
<BR><FONT SIZE=3D2>found in /apps/netbackup/netbkup_34_2_conf_files and =
are named</FONT>
<BR><FONT SIZE=3D2>kernel_drv_<filename></FONT>
<BR><FONT SIZE=3D2>A. st.conf</FONT>
<BR><FONT SIZE=3D2>III. Make the OS aware of the =
devices</FONT>
<BR><FONT SIZE=3D2>A. Run the command =
"devfsadm" to make the OS aware of the devices </FONT>
<BR><FONT SIZE=3D2>B. Run the command =
"cfgadm" to configure the devices </FONT>
<BR><FONT SIZE=3D2>IV. Install the sg =
driver.</FONT>
<BR><FONT SIZE=3D2>A. Remove the old sg =
driver by running the commands</FONT>
<BR><FONT SIZE=3D2>1. mv =
/kernel/drv/sg.conf /kernel/drv/sg.conf.<date></FONT>
<BR><FONT SIZE=3D2>2. rem_drv sg</FONT>
<BR><FONT SIZE=3D2>B. Install the new sg =
driver by running the script </FONT>
<BR><FONT SIZE=3D2>1. =
/usr/openv/volmgr/bin/driver/sg.install</FONT>
<BR><FONT SIZE=3D2>V. Verify the tape =
drives are visible by running the script </FONT>
<BR><FONT SIZE=3D2>(i) =
/usr/openv/volmgr/bin/sgscan tape</FONT>
<BR><FONT SIZE=3D2>NOTE: you should see ten tape drives</FONT>
<BR><FONT =
SIZE=3D2>###############################################################=
#############</FONT>
<BR><FONT SIZE=3D2>##############</FONT>
</P>
<BR>
<BR>
<BR>
<P><FONT SIZE=3D2>-----Original Message-----</FONT>
<BR><FONT SIZE=3D2>From: Pete Akre [<A =
HREF=3D"mailto:PAkre AT JNI DOT com">mailto:PAkre AT JNI DOT com</A>]</FONT>
<BR><FONT SIZE=3D2>Sent: Thursday, October 02, 2003 1:16 PM</FONT>
<BR><FONT SIZE=3D2>To: 'Darren Dunham'</FONT>
<BR><FONT SIZE=3D2>Cc: 'veritas-bu AT mailman.eng.auburn DOT edu'</FONT>
<BR><FONT SIZE=3D2>Subject: RE: [Veritas-bu] Netbackup Not Seeing My =
Tape Drive</FONT>
</P>
<BR>
<P><FONT SIZE=3D2>Thanks for the info, I sure am learning alot. But =
mine show as: 0cbn -></FONT>
<BR><FONT =
SIZE=3D2>../../devices/pci@1f,2000/SUNW,jfca@1,1/fp@0,0/st@w500507630061=
254d,0:cbn.</FONT>
<BR><FONT SIZE=3D2>So how would I setup my conf files to handle this =
weird number? Would I just</FONT>
<BR><FONT SIZE=3D2>make the target w500507630061254d? Is that even =
valid?</FONT>
</P>
<P><FONT SIZE=3D2>Thanks</FONT>
</P>
<P><FONT SIZE=3D2>Peter Akre</FONT>
</P>
<P><FONT SIZE=3D2>-----Original Message-----</FONT>
<BR><FONT SIZE=3D2>From: Darren Dunham [<A =
HREF=3D"mailto:ddunham AT taos DOT com">mailto:ddunham AT taos DOT
com</A>]</FONT>
<BR><FONT SIZE=3D2>Sent: Thursday, October 02, 2003 11:07 AM</FONT>
<BR><FONT SIZE=3D2>To: Pete Akre</FONT>
<BR><FONT SIZE=3D2>Subject: Re: [Veritas-bu] Netbackup Not Seeing My =
Tape Drive</FONT>
</P>
<BR>
<P><FONT SIZE=3D2>> </FONT>
<BR><FONT SIZE=3D2>> Here's another ignorant question. How do I know =
what target address to use</FONT>
<BR><FONT SIZE=3D2>> for this tape drive? I have arbitrarily created =
entries from 0-20 with no</FONT>
<BR><FONT SIZE=3D2>> effect.</FONT>
</P>
<P><FONT SIZE=3D2>That depends on your connection adapter and the =
driver.</FONT>
</P>
<P><FONT SIZE=3D2>For a scsi drive, the adapter will map the scsi =
target to the t# in the</FONT>
<BR><FONT SIZE=3D2>device path.</FONT>
</P>
<P><FONT SIZE=3D2>For a fiber adapter, the adapter has several choices, =
but generally it</FONT>
<BR><FONT SIZE=3D2>will map a single fiber WWPN to a target =
number. The driver can usually</FONT>
<BR><FONT SIZE=3D2>do it dynamically (pick a low number), or staticly =
(create an explicit</FONT>
<BR><FONT SIZE=3D2>mapping within the driver configuration =
file).</FONT>
</P>
<P><FONT SIZE=3D2>However, you say you already see (and can access) the =
devices via</FONT>
<BR><FONT SIZE=3D2>/dev/rmt/*. Just do an expansion of one of =
them..</FONT>
</P>
<P><FONT SIZE=3D2>lrwxrwxrwx 1 root =
root 45 Mar =
11 2003 /dev/rmt/8cbn -></FONT>
<BR><FONT SIZE=3D2>../../devices/pci@6,2000/JNI,FCE@1/st@2,0:cbn</FONT>
</P>
<P><FONT SIZE=3D2>The "@2" means that this particular drive =
is on target 2 for this</FONT>
<BR><FONT SIZE=3D2>adapter.</FONT>
</P>
<BR>
<P><FONT SIZE=3D2>-- </FONT>
<BR><FONT SIZE=3D2>Darren =
Dunham =
=
=
ddunham AT taos DOT com</FONT>
<BR><FONT SIZE=3D2>Unix System =
Administrator  =
; Taos - The =
SysAdmin Company</FONT>
<BR><FONT SIZE=3D2>Got some Dr =
Pepper?  =
;  =
; San Francisco, CA bay area</FONT>
<BR><FONT SIZE=3D2> =
< This line left intentionally blank to confuse you. ></FONT>
<BR><FONT =
SIZE=3D2>_______________________________________________</FONT>
<BR><FONT SIZE=3D2>Veritas-bu maillist - =
Veritas-bu AT mailman.eng.auburn DOT edu</FONT>
<BR><FONT SIZE=3D2><A =
HREF=3D"http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu"; =
TARGET=3D"_blank">http://mailman.eng.auburn.edu/mailman/listinfo/veritas=
-bu</A></FONT>
</P>
</BODY>
</HTML>
------_=_NextPart_001_01C3894C.0DD95E98--
|
