This is a MIME message. If you are reading this text, you may want to
consider changing to a mail reader or gateway that understands how to
properly handle MIME multipart messages.
--=__Part41634B38.1__=
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Mark,
I also use SSO and when adding new drives 1) found the sg/st files
would not get created as expected and had to create them manually and 2)
as mentioned by Cheryl, at the time of configuration, all shared drives
must not be in use.
So as far as SSO, I currently have 20 shared LTO II drives running with
no issues on SLES 8.
I also use the ENABLE_AUTO_PATH_CORRECTION in the vm.conf file which is
useful when after the drives are configured correctly.
-sj
>>> <Mark.Donaldson AT cexp DOT com> 10/5/2005 10:48 am >>>
We've been having the same problem with drive discovery. In our case
it's a
problem with Linux vs Netbackup SSO. If the drive is reserved by
another
server, then Linux doesn't identify the drive as reserved, it seems to
ident
it as down or similar. It then doesn't build the drive into the sg &
st
links.
Since the Linux start routines for volume manager runs this discovery
every
time, it rebuilds the links every time and various drives come and go.
I opened a ticket with Veritas/Symmantec and after bopping around
inside
their org for a couple of days the response was basically, "Yep, that's
the
way it works". The official work-around is to quiesce every drive,
identify
the drives, then comment the discovery part out of the start routines
so it
doesn't do it every time.
I stared at it awhile and managed to build in the missing drives by
hand.
Theoretically it's possible to do that every boot so you don't have to
mess
with the editing the discovery stuff out (and potentially having it
replaced
every upgrade & patch).
We're also having driver issues with our LTO drives on the v20 Sun
Opteron
boxes. The moment the data starts to flow, the box crashes. I don't
blame
Veritas on this, just adding it here for good measure.
Right now, I'd not suggest Linux for anything other than a dedicated
drive
arrangement (no shared drives).
-M
-----Original Message-----
From: veritas-bu-admin AT mailman.eng.auburn DOT edu
[mailto:veritas-bu-admin AT mailman.eng.auburn DOT edu]On Behalf Of Jeff
Lightner
Sent: Wednesday, October 05, 2005 6:57 AM
To: Jerry; veritas mailing list
Subject: RE: [Veritas-bu] Linux as a master/media server
We attempted to use Linux (RedHat EL AS 3) as a media server for our
setup which is SAN using Connectrix and Surestore to an L700.
Unfortunately it doesn't seem to discover all the drives correctly so
we
gave up and do network backups on it. This despite the fact we were
able to get the Linux server to access the Clariion array storage over
the fibre SAN.
Oddly enough the other night I attended the local Unix users group
meeting which has many of the same members as the local Linux users
group. I asked about this very issue and was told that Linux doesn't
do well with fibre. They said that it appears that it recognizes
devices by a very specific array of information so subtle differences
such as the firmware level on one device can make it undiscoverable.
I'm not saying it's impossible but it appears that unless you buy an
out
of the box solution designed specifically for Linux you may not be
able
to do it. I think Dell may sell this as in our installation they were
surprised to find out we weren't going to be using their library.
They
do have documentation for how to setup their library for Linux.
-----Original Message-----
From: veritas-bu-admin AT mailman.eng.auburn DOT edu
[mailto:veritas-bu-admin AT mailman.eng.auburn DOT edu] On Behalf Of Jerry
Sent: Wednesday, October 05, 2005 12:09 AM
To: veritas mailing list
Subject: [Veritas-bu] Linux as a master/media server
I'm considering replacing my aging Solaris box with a
Linux system. Does anyone have any opinions on how
well Veritas supports Linux as a Master server, Media
server, or both. In the past it seemed some features
were only available in Solaris, but I can't recall
specifics.
Currently I have an L700e with ACSLS for library
control. I'm especially interested in any of the tape
drive whackiness that might exist in Linux since
Veritas is relatively new to Veritas on Linux
(compared to Solaris).
How about mixing media/master servers.... keeping my
master server as a Solaris box, with Linux media servers???
__________________________________
Yahoo! Mail - PC Magazine Editors' Choice 2005
http://mail.yahoo.com
_______________________________________________
Veritas-bu maillist - Veritas-bu AT mailman.eng.auburn DOT edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
_______________________________________________
Veritas-bu maillist - Veritas-bu AT mailman.eng.auburn DOT edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
_______________________________________________
Veritas-bu maillist - Veritas-bu AT mailman.eng.auburn DOT edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
--=__Part41634B38.1__=
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; charset=3Diso-8859-1"=
>
<META content=3D"MSHTML 6.00.2800.1400" name=3DGENERATOR></HEAD>
<BODY style=3D"MARGIN: 4px 4px 1px; FONT: 10pt Tahoma">
<DIV>Mark,</DIV>
<DIV> </DIV>
<DIV>I also use SSO and when adding new drives 1) found the sg/st files =
would not get created as expected and had to create them manually and 2) =
as mentioned by Cheryl, at the time of configuration, all shared drives =
must not be in use.</DIV>
<DIV> </DIV>
<DIV>So as far as SSO, I currently have 20 shared LTO II drives running =
with no issues on SLES 8.</DIV>
<DIV> </DIV>
<DIV>I also use the ENABLE_AUTO_PATH_CORRECTION in the vm.conf file which =
is useful when after the drives are configured correctly.</DIV>
<DIV> </DIV>
<DIV>-sj<BR><BR>>>> <Mark.Donaldson AT cexp DOT com> 10/5/2005 =
10:48 am >>><BR>We've been having the same problem with drive =
discovery. In our case it's a<BR>problem with Linux vs Netbackup =
SSO. If the drive is reserved by another<BR>server, then Linux =
doesn't identify the drive as reserved, it seems to ident<BR>it as down or =
similar. It then doesn't build the drive into the sg & st<BR>link=
s.<BR><BR>Since the Linux start routines for volume manager runs this =
discovery every<BR>time, it rebuilds the links every time and various =
drives come and go.<BR><BR>I opened a ticket with Veritas/Symmantec and =
after bopping around inside<BR>their org for a couple of days the response =
was basically, "Yep, that's the<BR>way it works". The official =
work-around is to quiesce every drive, identify<BR>the drives, then =
comment the discovery part out of the start routines so it<BR>doesn't do =
it every time.<BR><BR>I stared at it awhile and managed to build in the =
missing drives by hand.<BR>Theoretically it's possible to do that every =
boot so you don't have to mess<BR>with the editing the discovery stuff out =
(and potentially having it replaced<BR>every upgrade & patch).<BR><BR>W=
e're also having driver issues with our LTO drives on the v20 Sun =
Opteron<BR>boxes. The moment the data starts to flow, the box =
crashes. I don't blame<BR>Veritas on this, just adding it here for =
good measure.<BR><BR>Right now, I'd not suggest Linux for anything other =
than a dedicated drive<BR>arrangement (no shared drives).<BR><BR>-M<BR><BR>=
-----Original Message-----<BR>From: veritas-bu-admin AT mailman.eng.auburn DOT
edu=
<BR>[mailto:veritas-bu-admin AT mailman.eng.auburn DOT edu]On Behalf Of
Jeff<BR>Li=
ghtner<BR>Sent: Wednesday, October 05, 2005 6:57 AM<BR>To: Jerry; veritas =
mailing list<BR>Subject: RE: [Veritas-bu] Linux as a master/media =
server<BR><BR><BR>We attempted to use Linux (RedHat EL AS 3) as a media =
server for our<BR>setup which is SAN using Connectrix and Surestore to an =
L700.<BR>Unfortunately it doesn't seem to discover all the drives =
correctly so we<BR>gave up and do network backups on it. This =
despite the fact we were<BR>able to get the Linux server to access the =
Clariion array storage over<BR>the fibre SAN. <BR><BR>Oddly enough the =
other night I attended the local Unix users group<BR>meeting which has =
many of the same members as the local Linux users<BR>group. I =
asked about this very issue and was told that Linux doesn't<BR>do well =
with fibre. They said that it appears that it recognizes<BR>dev=
ices by a very specific array of information so subtle differences<BR>such =
as the firmware level on one device can make it undiscoverable.<BR><BR>I'm =
not saying it's impossible but it appears that unless you buy an out<BR>of =
the box solution designed specifically for Linux you may not be able<BR>to =
do it. I think Dell may sell this as in our installation they =
were<BR>surprised to find out we weren't going to be using their library.&n=
bsp; They<BR>do have documentation for how to setup their library =
for Linux.<BR><BR>-----Original Message-----<BR>From: veritas-bu-admin@mail=
man.eng.auburn.edu<BR>[mailto:veritas-bu-admin AT mailman.eng.auburn DOT edu]
On =
Behalf Of Jerry<BR>Sent: Wednesday, October 05, 2005 12:09 AM<BR>To: =
veritas mailing list<BR>Subject: [Veritas-bu] Linux as a master/media =
server<BR><BR>I'm considering replacing my aging Solaris box with =
a<BR>Linux system. Does anyone have any opinions on how<BR>well =
Veritas supports Linux as a Master server, Media<BR>server, or both. =
In the past it seemed some features<BR>were only available in Solaris, but =
I can't recall<BR>specifics.<BR><BR>Currently I have an L700e with ACSLS =
for library<BR>control. I'm especially interested in any of the =
tape<BR>drive whackiness that might exist in Linux since<BR>Veritas is =
relatively new to Veritas on Linux<BR>(compared to Solaris).<BR><BR>How =
about mixing media/master servers.... keeping my<BR>master server as a =
Solaris box, with Linux media servers???<BR><BR><BR><BR>___________________=
_______________ <BR>Yahoo! Mail - PC Magazine Editors' Choice 2005 =
<BR>http://mail.yahoo.com<BR>______________________________________________=
_<BR>Veritas-bu maillist - Veritas-bu AT mailman.eng.auburn DOT
edu<BR=
>http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu<BR><BR>_________=
______________________________________<BR>Veritas-bu maillist =
- Veritas-bu AT mailman.eng.auburn DOT
edu<BR>http://mailman.eng.auburn.edu/=
mailman/listinfo/veritas-bu<BR>____________________________________________=
___<BR>Veritas-bu maillist - Veritas-bu AT mailman.eng.auburn DOT
edu<=
BR>http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu<BR></DIV></BOD=
Y></HTML>
--=__Part41634B38.1__=--
|
