Backup does run ok with otm turned off. Whether it actually backed every
file up or not, I don't know, but it does have a status of 0.
Bob Grabbe
Dominos Pizza LLC
734-930-3703
Fax 734-669-3703
grabbeb AT dominos DOT com
>>> "Scott Jacobson" <SJACOBSO AT novell DOT com> 3/7/02 2:07:23 PM >>>
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
|
