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.
--=_2479924D.0B6A0487
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Bob,
I would check the below URL or with Novell and ask them to point out
where and what the correct version of TSA500.NLM is that you need. Make
sure you tell them what version of "CLIB", "DS" and run "version" and
give them the information as well.
You probably find out it is a timing conflict with the version of CLIB
and TSA500 that is causing you problem.
Scott J.
Richard Mickle responded to your question with the below (nice job
Richard)
We ran into the same problem with SP3. After turning OTM off, BPCD
abended
the server. The group we get our support through found a reference on
Novels sight to problems with the TSA500 NLM that shipped with SP3
abending
the server when using Backup Exec (see link below). The recommended
solution was to downrev the TSA500 NLM to the version that shipped
with
SP2. We did that and where able to backup the server. We have not
turned
OTM back on yet, so I do not now if that fixed the problem of OTM
abending
the server.
http://support.novell.com/cgi-bin/search/searchtid.cgi?/10064953.htm
Richard Mickle
UNIX Systems and Storage Administrator
Moore Response Marketing Services
E-Mail: rmickle AT rms.moore DOT com
Phone: 920-339-1695
Fax: 920-339-1231
>>> "Bob Grabbe" <GRABBEB AT dominos DOT com> 03/07/02 10:19AM >>>
It doesn't work with otm turned on. I have vers 5.01 of tsa500,
5/24/2000 on the server and it still abends when the backup starts.
Will
try it with otm off to see what happens.
>>> <rmickle AT rms.moore DOT com> 3/7/02 9:52:05 AM >>>
We ran into the same problem with SP3. After turning OTM off, BPCD
abended
the server. The group we get our support through found a reference on
Novels sight to problems with the TSA500 NLM that shipped with SP3
abending
the server when using Backup Exec (see link below). The recommended
solution was to downrev the TSA500 NLM to the version that shipped
with
SP2. We did that and where able to backup the server. We have not
turned
OTM back on yet, so I do not now if that fixed the problem of OTM
abending
the server.
http://support.novell.com/cgi-bin/search/searchtid.cgi?/10064953.htm
Richard Mickle
UNIX Systems and Storage Administrator
Moore Response Marketing Services
E-Mail: rmickle AT rms.moore DOT com
Phone: 920-339-1695
Fax: 920-339-1231
Date: Wed, 06 Mar 2002 16:53:56 -0500
From: "Bob Grabbe" <GRABBEB AT dominos DOT com>
To: <veritas-bu AT mailman.eng.auburn DOT edu>
Subject: [Veritas-bu] Netware CLient 5.1 w/SP4
Is anyone using Netbackup with Netware 5.1 client and SP4 yet ? I want
to go to SP4 and bypass SP3 due to many problems I have seen with it,
but on the server I upgraded to SP4, I have problems.
After NBU client is loaded, it is impossible to unload bpcd. I type
unload bpcd at the command prompt and it doesn't unload.
Everytime I try to run a backup, OTM abends the server almost
immediately.
Veritas support didn't have a copy of SP4 until I called to open an
incident with them, they are downloading it now, but may not be able
to
support it.
Evironment is Netbackup 3.4.1 on a Solaris 8 server, Stek 9740
enclosure w/8 DLT7000 drives, mixed NW5.1 SP2, and NT/2000 clients.
Any input ?
Thanks in advance.
Bob Grabbe
Dominos Pizza LLC
734-930-3703
Fax 734-669-3703
grabbeb AT dominos DOT com
_______________________________________________
Veritas-bu maillist - Veritas-bu AT mailman.eng.auburn DOT edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
--=_2479924D.0B6A0487
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=Content-Type content="text/html; charset=iso-8859-1">
<META content="MSHTML 5.50.4807.2300" name=GENERATOR></HEAD>
<BODY style="MARGIN-TOP: 2px; FONT: 8pt MS Sans Serif; MARGIN-LEFT: 2px">
<DIV><FONT size=2>Bob,</FONT></DIV>
<DIV><FONT size=2></FONT> </DIV>
<DIV><FONT size=2>I would check the below URL or with Novell and ask them to
point out where and what the correct version of TSA500.NLM is that you
need. Make sure you tell them what version of "CLIB", "DS" and run
"version" and give them the information as well.</FONT></DIV>
<DIV> </DIV>
<DIV><FONT size=2>You probably find out it is a timing conflict with the
version of CLIB and TSA500 that is causing you problem.</FONT></DIV>
<DIV><FONT size=2></FONT> </DIV>
<DIV><FONT size=2>Scott J.</FONT></DIV>
<DIV><FONT size=2></FONT> </DIV>
<DIV><FONT size=2><STRONG>Richard Mickle responded to your question with the
below (nice job Richard)</STRONG></FONT></DIV>
<DIV><FONT size=2></FONT> </DIV>
<DIV>We ran into the same problem with SP3. After turning OTM off, BPCD
abended<BR>the server. The group we get our support through found a
reference on<BR>Novels sight to problems with the TSA500 NLM that shipped with
SP3 abending<BR>the server when using Backup Exec (see link below). The
recommended<BR>solution was to downrev the TSA500 NLM to the version that
shipped with<BR>SP2. We did that and where able to backup the
server. We have not turned<BR>OTM back on yet, so I do not now if that
fixed the problem of OTM abending<BR>the server.<BR><BR><A
href="http://support.novell.com/cgi-bin/search/searchtid.cgi?/10064953.htm";>http://support.novell.com/cgi-bin/search/searchtid.cgi?/10064953.htm</A><BR><BR>Richard
Mickle<BR>UNIX Systems and Storage Administrator<BR>Moore Response Marketing
Services<BR>E-Mail:
rmickle AT rms.moore DOT com<BR>Phone:
920-339-1695<BR>Fax:
920-339-1231<BR></DIV><BR><BR>>>> "Bob Grabbe"
<GRABBEB AT dominos DOT com> 03/07/02 10:19AM >>><BR>It doesn't
work
with otm turned on. I have vers 5.01 of tsa500,<BR>5/24/2000 on the server and
it still abends when the backup starts. Will<BR>try it with otm off to see what
happens. <BR><BR><BR>>>> <rmickle AT rms.moore DOT com> 3/7/02
9:52:05
AM >>><BR>We ran into the same problem with SP3. After turning OTM
off,
BPCD<BR>abended<BR>the server. The group we get our support through found
a reference on<BR>Novels sight to problems with the TSA500 NLM that shipped
with
SP3<BR>abending<BR>the server when using Backup Exec (see link below).
The
recommended<BR>solution was to downrev the TSA500 NLM to the version that
shipped<BR>with<BR>SP2. We did that and where able to backup the
server. We have not<BR>turned<BR>OTM back on yet, so I do not now if that
fixed the problem of OTM<BR>abending<BR>the server.<BR><BR><A
href="http://support.novell.com/cgi-bin/search/searchtid.cgi?/10064953.htm";>http://support.novell.com/cgi-bin/search/searchtid.cgi?/10064953.htm</A>
<BR><BR>Richard Mickle<BR>UNIX Systems and Storage Administrator<BR>Moore
Response Marketing Services<BR>E-Mail:
rmickle AT rms.moore DOT com <BR>Phone:
920-339-1695<BR>Fax:
920-339-1231<BR><BR>Date: Wed, 06 Mar 2002 16:53:56 -0500<BR>From: "Bob Grabbe"
<GRABBEB AT dominos DOT com><BR>To:
<veritas-bu AT mailman.eng.auburn DOT edu><BR>Subject: [Veritas-bu]
Netware
CLient 5.1 w/SP4<BR><BR>Is anyone using Netbackup with Netware 5.1 client and
SP4 yet ? I want<BR>to go to SP4 and bypass SP3 due to many problems I have
seen
with it,<BR>but on the server I upgraded to SP4, I have problems.<BR>After NBU
client is loaded, it is impossible to unload bpcd. I type<BR>unload bpcd at the
command prompt and it doesn't unload.<BR>Everytime I try to run a backup, OTM
abends the server almost<BR>immediately.<BR>Veritas support didn't have a copy
of SP4 until I called to open an<BR>incident with them, they are downloading it
now, but may not be able<BR>to<BR>support it.<BR>Evironment is Netbackup 3.4.1
on a Solaris 8 server, Stek 9740<BR>enclosure w/8 DLT7000 drives, mixed NW5.1
SP2, and NT/2000 clients.<BR>Any input ?<BR>Thanks in advance.<BR><BR>Bob
Grabbe<BR>Dominos Pizza LLC<BR>734-930-3703<BR>Fax
734-669-3703<BR>grabbeb AT dominos DOT com
<BR><BR><BR>_______________________________________________<BR>Veritas-bu
maillist - Veritas-bu AT mailman.eng.auburn DOT edu<BR><A
href="http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu";>http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu</A><BR></BODY></HTML>
--=_2479924D.0B6A0487--
|
