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_01C4264D.9F21F8BC
Content-Type: text/plain
VSP is automatically enabled when you upgrade/install 4.5 FP5 or higher, OTM
is not disabled and you have to "hack" the registry and disable it manually.
Penelope
_____
From: Major, Rusty [mailto:jrmajor AT TexasChildrensHospital DOT org]
Sent: Monday, April 19, 2004 2:15 PM
Cc: veritas-bu AT mailman.eng.auburn DOT edu
Subject: VSP (Was RE: [Veritas-bu] We all need some feed back on NBU 5.0)
VSP has been enabled by default on every client I've upgraded from 3.4. I
don't know if OTM is disabled if it will leave VSP disabled, but since it's
a completely different animal than OTM, I would doubt it.
Rusty
-----Original Message-----
From: Karl.Rossing AT Federated DOT CA [mailto:Karl.Rossing AT Federated DOT CA]
Sent: Monday, April 19, 2004 10:53 AM
Cc: veritas-bu AT mailman.eng.auburn DOT edu
Subject: Re: [Veritas-bu] We all need some feed back on NBU 5.0
veritas-bu-admin AT mailman.eng.auburn DOT edu wrote on 04/19/2004 09:19:47 AM:
> On Mon, Apr 19, 2004 at 09:17:24AM -0400, Bobby R Windle wrote:
> > Please, if you have any experiences both good or bad in or around
> > moving from NB4.5 to NB5.0, please express your concerns or praises.
> > This is an important issue that we all need to hear about. There have
> > been a lot of different takes on this. Try to keep it constructive and
> > fair. New products will always have fixes.. otherwise we would all
> > be home fixing toasters.
>
> We're fighting a significant battle with NBU 5.0 MP1 right now. It
> seems like the host-based include/exclude processing for our Solaris
> clients isn't working at all and all files are being backed up all the
> time - we've had dozens of the same files being backed up when we should
> have had only 1. We have a support ticket open with Veritas on this.
Wow, I'm glad i'm still on 5.0GA.
The two problems i ran into are:
1) VSP is enabled by default on 5.0. I never dealt with VSP on 4.5MP5.
Apparently VSP appeared on 4.5FP5.
2) Windows clients were getting alot of 25 errors. had to "/usr/sbin/ndd
-set /dev/tcp tcp_time_wait_interval 1000" on our solaris master.
Oh yea... The windows admin console tends to disappear/crash, which is odd
since xp doesn't notice and doesn't a crash report to microsoft. But this i
can live with.
------_=_NextPart_001_01C4264D.9F21F8BC
Content-Type: text/html
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=US-ASCII">
<META content="MSHTML 6.00.2800.1400" name=GENERATOR></HEAD>
<BODY>
<DIV dir=ltr align=left><SPAN class=344472620-19042004><FONT face=Arial
color=#0000ff size=2>VSP is automatically enabled when you upgrade/install 4.5
FP5 or higher, OTM is not disabled and you have to "hack" the registry and
disable it manually.</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=344472620-19042004><FONT face=Arial
color=#0000ff size=2></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=344472620-19042004><FONT face=Arial
color=#0000ff size=2>Penelope</FONT></SPAN></DIV>
<DIV dir=ltr align=left>
<HR tabIndex=-1>
</DIV>
<DIV dir=ltr align=left><FONT face=Tahoma size=2><B>From:</B> Major, Rusty
[mailto:jrmajor AT TexasChildrensHospital DOT org] <BR><B>Sent:</B> Monday,
April 19,
2004 2:15 PM<BR><B>Cc:</B> veritas-bu AT mailman.eng.auburn DOT
edu<BR><B>Subject:</B>
VSP (Was RE: [Veritas-bu] We all need some feed back on NBU
5.0)<BR></FONT><BR></DIV>
<DIV></DIV>
<DIV><SPAN class=672531218-19042004><FONT face=Arial color=#0000ff size=2>VSP
has been enabled by default on every client I've upgraded from 3.4. I don't
know
if OTM is disabled if it will leave VSP disabled, but since it's a
completely different animal than OTM, I would doubt it.</FONT></SPAN></DIV>
<DIV><SPAN class=672531218-19042004><FONT face=Arial color=#0000ff
size=2></FONT></SPAN> </DIV>
<DIV><SPAN class=672531218-19042004><FONT face=Arial color=#0000ff
size=2>Rusty</FONT></SPAN></DIV>
<BLOCKQUOTE
style="PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #0000ff 2px solid">
<DIV class=OutlookMessageHeader dir=ltr align=left><FONT face=Tahoma
size=2>-----Original Message-----<BR><B>From:</B> Karl.Rossing AT Federated
DOT CA
[mailto:Karl.Rossing AT Federated DOT CA]<BR><B>Sent:</B> Monday, April 19,
2004
10:53 AM<BR><B>Cc:</B> veritas-bu AT mailman.eng.auburn DOT
edu<BR><B>Subject:</B>
Re: [Veritas-bu] We all need some feed back on NBU
5.0<BR><BR></FONT></DIV><BR><FONT
size=2><TT>veritas-bu-admin AT mailman.eng.auburn DOT edu wrote on 04/19/2004
09:19:47 AM:<BR><BR>> On Mon, Apr 19, 2004 at 09:17:24AM -0400, Bobby R
Windle wrote:<BR>> > Please, if you have any experiences both good or
bad in or around<BR>> > moving from NB4.5 to NB5.0, please
express
your concerns or praises.<BR>> > This is an important issue that we all
need to hear about. There have<BR>> > been a lot of different
takes on this. Try to keep it constructive and<BR>> > fair. New
products will always have fixes.. otherwise we would all<BR>> >
be
home fixing toasters.<BR>> <BR>> We're fighting a significant battle
with NBU 5.0 MP1 right now. It<BR>> seems like the host-based
include/exclude processing for our Solaris<BR>> clients isn't working at
all and all files are being backed up all the<BR>> time - we've had dozens
of the same files being backed up when we should<BR>> have had only 1.
We have a support ticket open with Veritas on
this.<BR></TT></FONT><BR><FONT size=2><TT>Wow, I'm glad i'm still on
5.0GA.</TT></FONT> <BR><BR><FONT size=2><TT>The two problems i ran into
are:</TT></FONT> <BR><BR><FONT size=2><TT>1) VSP is enabled by default on
5.0.
I never dealt with VSP on 4.5MP5. Apparently VSP appeared on
4.5FP5.</TT></FONT> <BR><BR><FONT size=2><TT>2) Windows clients were getting
alot of 25 errors. had to "/usr/sbin/ndd -set /dev/tcp tcp_time_wait_interval
1000" on our solaris master.</TT></FONT> <BR><BR><FONT size=2><TT> Oh
yea... The windows admin console tends to disappear/crash, which is odd since
xp doesn't notice and doesn't a crash report to microsoft. But this i can
live
with.</TT></FONT></BLOCKQUOTE></BODY></HTML>
------_=_NextPart_001_01C4264D.9F21F8BC--
|
