Jerry, what we were told is that the TSA nlm's that shipped with
LIPUP8.EXE from Novell have a problem with ADSM. We have since installed
LIPUP9.EXE's files, but Novell didn't ship any TSA files in this update.
I haven't seen anything yet on a SMDR update from Novell yet that might
include newer TSA nlm's.
I was told by someone on this service that the problem would be
fixed in the next release of the ADSM client. This was back around the
middle of August? I was able to download the latest client last night,
but I haven't had a chance to get it installed on the servers to see if
it fixes the problem.
Also, not sure who posted the question about backing up long files
spaces on the Novell server. What we do in an NCF files (Novell's server
batch files) is load the TSANDS.NLM, TSA410.NLM, TSADOS.NLM and the
TSAOS2.NLM before loading the DSMC.NLM and it seems to work fine for us.
Though I can't really tell what the files are that get backed up with
the long file name, the backup logs don't seem to show any problems on
the volumes that are supporting the long files spaces.
Hopefully this will help ....... Bob T
Jerry Lawson wrote:
>
> ---------------------------- Forwarded with Changes
> ---------------------------
> From: INTERNET.OWNERAD at SNADGATE
> Date: 10/3/96 5:33AM
> To: Jerry Lawson at TISDMAIL
> *To: *Multiple recipients of list ADSM-L at SNADGATE
> Subject: Temporary Novell Connection Failure
> -------------------------------------------------------------------------------
>
> Bob -
>
> You should be loading the TSA NLM just before you load ADSM. On a NetWare 3.x
> system, it is either TSA311 or TSA312, depending on your release. On a
> NetWare 4.x system, it is TSANDS.NLM. I am not familiar with TSANDS, but the
> TSA31x NLMs also autoload SMDR.NLM.
>
> If you are trying to remotely attach to a server - the TSA modules must also
> be loaded on those machines.
>
> Jerry Lawson
> jlawson AT itthartford DOT com
> ________________________Forward Header________________________
> Author: INTERNET.OWNERAD
> Subject: Temporary Novell Connection Failure
> 10-03-96 05:33 AM
>
> Does anyone see the following, which happens fairly frequently
> on our Novell ADSM clients -- ones running both NetWare 3
> and Netware 4 --- when starting a scheduled backup.
>
> An error ANS4972E (highlighted below) is *always* followed after
> a few seconds by a successful connection between client and server.
> The ADSM server is 2.1.0.8 running under AIX 4.1 on an RS/6000;
> the client level is 2.1.0.3.
>
> Thanks,
> Bob Douglas
> ----------------------------------------------------------------------
> 20/08/96 01:07
> Executing scheduled command now.
> 20-08-1996 01:07:13 Session established with server OX_HFS:
> AIX-RS/6000 20-08-1996 01:07:13 Server Version 2, Release 1, Level
> 0.8 20-08-1996 01:07:13 Server date/time: 20-08-1996 01:08:34 Last
> access: 19-08-1996 09:56:04
>
> 20/08/96 01:07
> Connecting to a NetWare File System (NSF_OUCS).
>
> 20/08/96 01:07
> Connected to NSF_OUCS.
>
> ****** 20-08-1996 01:07:19 ANS4972E Unable to connect to NetWare target
> ****** service ''. Make sure the TSA NLM is loaded on the specified machine.
> 20/08/96 01:07 Connecting to a NetWare File System (NSF_OUCS).
>
> 20/08/96 01:07
> Connected to NSF_OUCS.
>
> 20-08-1996 01:07:22 Incremental backup of volume 'NSF_OUCS\SYS:'
> etc etc --- successful backup
> -------------------------------------------------------------------------
-----------------------------------------------------------
| Bob Thornton | Schreiber Foods, Inc. |
| Bob Thornton | Schreiber Foods, Inc. |
| Network Administrator | P.O. Box 19010 |
| Email: bobt AT netnet DOT net | Green Bay, Wi. 54307-9010 |
| | Phone: (414) 437-7601 |
-----------------------------------------------------------
=========================================================================
|
