Networker

Re: [Networker] Storage Nodes on same Library?

2008-06-19 14:37:14
Subject: Re: [Networker] Storage Nodes on same Library?
From: "Allison, Jim" <Jim.Allison AT ASURION DOT COM>
To: NETWORKER AT LISTSERV.TEMPLE DOT EDU
Date: Thu, 19 Jun 2008 13:25:01 -0500
Thanks guys,
We do have all the DDS and SN licenses we need. I am painfully aware of
the issues surrounding DDS and dedicated Storage Nodes. I had to script
cron jobs around the backup times of lanless clients to put the base
drive into service mode at my last job. 

I configured the SN by zoning only the drives, but got an error
indicating "no handler" for media, so I assumed that to mean a lib
control port. Can we zone the control port using a different lun? I know
we can logically split the lib with ACSLS (ACS for Spectra). I had
thought that the SN would just pass requests to the master server for
tape operations, but it seems that it needs to control the media
devices. We are using persistent binding also. Should the SN work by
only presenting the  drives? I understand that the library should only
be controlled by the master server. An EMC consultant had the SN's
configured on the same lib before I got here and I am curious if it was
a valid (standard) configuration they had. 

-----Original Message-----
From: EMC NetWorker discussion [mailto:NETWORKER AT LISTSERV.TEMPLE DOT EDU] On
Behalf Of Bruce Breidall
Sent: Thursday, June 19, 2008 12:51 PM
To: NETWORKER AT LISTSERV.TEMPLE DOT EDU
Subject: Re: [Networker] Storage Nodes on same Library?

Also, you have to decide whether or not you want the SNs to be dedicated
to themselves or not. To be non-dedicated requires another (more
expensive) license.

You get prompted for that choice when you use jbconfig. As Fazil
mentioned, only one server can see the jukebox lun. I have found that
sharing the drives works great (I am at 7.3.2.jumbo - moving to 7.3.4
soon), but it does require the DDS licenses. I think the biggest factor
in deciding whether or not to share the drives (besides the DDS license)
is whether or not you have enough of them to dedicate to your SNs, and
still get the work done. Sharing the drives removes the need to decide
that.

-----Original Message-----
From: EMC NetWorker discussion [mailto:NETWORKER AT LISTSERV.TEMPLE DOT EDU] On
Behalf Of Fazil Saiyed
Sent: Thursday, June 19, 2008 12:10 PM
To: NETWORKER AT LISTSERV.TEMPLE DOT EDU
Subject: Re: [Networker] Storage Nodes on same Library?

Hello,
The usual way of sharing the lib is actually via sharing drives ( needs 
DDS licences), control lun should be owned and assigned to master
server, 
please check jbconfig man page  or use Gui to configure assigned drives
to 
the storage node, this is if you like to share drives, i per say don't 
like sharing drives, so you can just assign some drives to SN and with 
proper zoning considerations, define remote devices for SN that the
master 
server is aware of.
There are other approaches, i.e ACLCS server, having multiple partitions

on the physical library ( in this case Control lun may be assigned to
SN).
Please look into persistence binding and also using driver feature to 
harden the tape drive  association to avoid drive resequiencing , since 
you are still doing the install, it's  may be a good idea to have this 
features turned on from get go.
Thanks



Jim Allison <jim.allison AT ASURION DOT COM> 
Sent by: EMC NetWorker discussion <NETWORKER AT LISTSERV.TEMPLE DOT EDU>
06/19/2008 11:38 AM
Please respond to
EMC NetWorker discussion <NETWORKER AT LISTSERV.TEMPLE DOT EDU>; Please respond

to
Jim Allison <jim.allison AT ASURION DOT COM>


To
NETWORKER AT LISTSERV.TEMPLE DOT EDU
cc

Subject
[Networker] Storage Nodes on same Library?






Hey folks,

I have a few questions about storage node configuration. I am new to
this
shop and we are using a configuration that I am unfamiliar with. We are
running 7.4.2 on Windows 2003 servers. Library is a fiber attached
Spectra
Logic T950 (one large partition defined) with fiber attached LTO IV tape
drives (12). We previously had storage nodes using the same library to 
take
some of the I/O load off the primary Networker server. They had issues
and
backed out the storage nodes previously (prior to tape drive upgrade).
My
question is this; Is a storage node that uses the same library resource
as
the primary server a valid configuration and does it not cause library
control contention? When we try to zone in the lib control port, the 
storage
node computer will hang and not boot like it has a  SCSI bus issue. I
have
used dedicated storage nodes in the past with drive sharing for lanless
backups, and I thought the main purpose of storage nodes was to run
additional libraries on one master server. Thanks, Jim Allison, Asurion,
Nashville TN.

To sign off this list, send email to listserv AT listserv.temple DOT edu and
type 
"signoff networker" in the body of the email. Please write to 
networker-request AT listserv.temple DOT edu if you have any problems with this

list. You can access the archives at 
http://listserv.temple.edu/archives/networker.html or
via RSS at http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER



To sign off this list, send email to listserv AT listserv.temple DOT edu and
type "signoff networker" in the body of the email. Please write to
networker-request AT listserv.temple DOT edu if you have any problems with this
list. You can access the archives at
http://listserv.temple.edu/archives/networker.html or
via RSS at http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER

To sign off this list, send email to listserv AT listserv.temple DOT edu and
type "signoff networker" in the body of the email. Please write to
networker-request AT listserv.temple DOT edu if you have any problems with this
list. You can access the archives at
http://listserv.temple.edu/archives/networker.html or
via RSS at http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER

To sign off this list, send email to listserv AT listserv.temple DOT edu and 
type "signoff networker" in the body of the email. Please write to 
networker-request AT listserv.temple DOT edu if you have any problems with this 
list. You can access the archives at 
http://listserv.temple.edu/archives/networker.html or
via RSS at http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER