[Veritas-bu] Netbackup 3.4/Solaris 2.6/STK L700 LTO

2001-12-13 13:38:47
Subject: [Veritas-bu] Netbackup 3.4/Solaris 2.6/STK L700 LTO
From: rplace AT uslec DOT com (Place, Richard)
Date: Thu, 13 Dec 2001 13:38:47 -0500
ACS or ACSLS is an application from StorageTek that does library and tape
drive management.  It is most applicable to environments with more than one
backup platform, i.e. Veritas and Legato, or Veritas and AS400, etc.  In an
evironment where only one backup management software exists it is not
needed. STK will tell you differently but it will just be one more component
added into your backup model.  What it actually does is take requests from
many software packages and controls the library.  NetBackup will do this for

Hope this helps,
Rick Place 
Sr. Unix Systems Administrator
US LEC of North Carolina
Phone (704) 319-8649
Pager (888) 642-6071

-----Original Message-----
From: anthony.guzzi AT storability DOT com
[mailto:anthony.guzzi AT storability DOT com]
Sent: Thursday, December 13, 2001 10:52 AM
To: donna.nadimi AT lucasfilm DOT com
Cc: veritas-bu AT mailman.eng.auburn DOT edu
Subject: Re: [Veritas-bu] Netbackup 3.4/Solaris 2.6/STK L700 LTO


   First, if you have two SCSI drives per SCSI-FC bridge (e.g. a 
Crossroads), then one drive will show up a LUN 0 and the other should show 
up as LUN 1.  Each bridge should be showing up as a separate SCSI target 
on the same controller.  This means that the first thing you'll need to 
edit is the /kernel/drv/st.conf file.   To start with, the 'st.conf' file 
will need lines in it like the following (assuming the bridges are getting 
SCSI targets 1-5 [I'm reserving 0 for other purposes]):

        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;

The exact lines will need to match the SCSI targets being assigned to the 
bridges on your system.  You'll need similar lines in the 'sg.conf' file 
to see the drives in an 'sgscan'.  Review the Media Manager Device 
Configuration Guide (or is it the install guide?) on how to configure the 
SG driver.  You'll need to specify a  value of at least 1 to the '-ml' 
(max LUN) parameter to the '' command.  You also need to pay 
careful attention to what SCSI targets the bridges are getting.

   Also in the 'st.conf' file, you'll need to add a 'tape-config-list=' 
line (if you haven't done so already) and corresponding data property 
line.  Unfortunately, I don't have those lines.   Unless someone else on 
this list have them, I'm guessing you'll need to contact STK for them.

   Second, are you running things through a fabric or are you making 
direct connections from fiber HBA to the SCSI-FC bridge?  If you're using 
a fabric, then you'll need to review the info provided by QLogics on 
persistent binding.  You'll need to bind each bridge to a specific SCSI 
target.  Unfortunately, there is no way to guarantee that when the system 
boots, each bridge will get the same SCSI target each time.  Persistent 
binding assures this.  You'll need this because NBU is *very* sensitive to 
the ordering of tapes drivers.  I've got a number of L-700's with STK-9840 
fiber-based drivers and have learned this all too well.  For the binding, 
you'll need to edit the 'qla2200.conf' file.

   As far as other changes to the 'qla2200.conf' file goes, most of the 
default values should be okay.  If memory serves me right, any values set 
to 'hba0' will be treated as defaults for all other HBAs so there's no 
need to duplicate them for each HBA in the system.  I've used the STK-3200 
SCSI-FC bridge (which is a Crossroads 4200 with [as a STK tech told me] "a 
different paint job) and DLT-7000's connected to a Brocade 2800 fibre 
switch with a Sun220R and QLA2200's also connected the switch and I used 
just the default values.  Things worked fine with me.  But since you're 
using LTO's,

   As for ACS, I believe that's a StorageTek application, so your STK 
sales rep and/or presales engineer should be able to help you there.  I 
personally haven't had an opportunity to work with the LTO drives but one 
of the other engineers here is involved in installing a L-700 with LTO 
drives at one of our customer sites and he says (and the STK guys will 
hate me saying this) ACS is not needed.  They're just treating the drives 
as they would a DLT or a 9840 drive.  They tell me it works.

-- Tony Guzzi
Sr. Solutions Engineer, AssuredRestore team
Storability, Inc.
Southborough, MA 01772
The Leading Provider of Automated Storage Assurance for the Enterprise


Message: 2
From: Donna Nadimi <donna.nadimi AT lucasfilm DOT com>
To: veritas-bu AT mailman.eng.auburn DOT edu
Date: Wed, 12 Dec 2001 10:34:38 -0800
Subject: [Veritas-bu] Netbackup 3.4/Solaris 2.6/STK L700 LTO

Please help!

I'm out of my depth here.  I'm trying to hook up a STK L700 with 10 LTO
drives to my Sun E450 using QLogic 2200F HBA's.  (2 scsi drives per fiber)

I have a couple of questions:

1.  What configuration files do I need to edit?  What info do I put in 
sd.conf?  st.conf?  qla2200.conf?

2.  What is ACS?  Where do I get it?  What does it do?

If anyone knows the answer to these questions, or has some sort of
documentation telling me what to do, I'd really appreciate you sending it

I've gotten to the point where sgscan can see the changer and 1 drive.
However, I'm not sure which config parameter is making it work.

Thanks in advance.

Your friend in need, 


<banging head on keyboard/>


Donna L. Nadimi
UNIX Systems Engineer
Lucasfilm Ltd.
donna.nadimi AT lucasfilm DOT com

"UNIX is user friendly.  It's just picky about who its friends are."

Veritas-bu maillist  -  Veritas-bu AT mailman.eng.auburn DOT edu