The first is to have the TSA NLM loaded on both NetWare machines.  TSA is
release dependant, so be careful - if the server is a 3.x box, then it should
be running either TSA311 or TSA312.  If it is 4.x, then the module is TSANDS.
The TSA NLMs provide communications between the servers, and are required by
NetWare.  It also helps to have then at least at the same level on all
machines.  Probably the newer the better.

I did find that this was a slow process - when we tried to back up large
files, performance dropped on both machines, to the point where we got
performance calls.   This was on older processors (386 50 Mhz machines, most
likely) so if you are running a faster chip, it may not be an issue.

I also put a domain statement in my DSM.OPT on the machine doing the actual
backup, that included the server name and file system  DOMAIN SERVERA/SYS:  I
also included an NWUSER and NWPASS statement to handle the netware user id
prompts.  Check the syntax in the manual if you have a question.

Since all of our machines are in the building anyway, we found that while this
did work, there was no real advantage to it, and so don't do it any more.  For
one thing, there is a lot of Network overhead, since files are moved from one
server to the other before they are sent to ADSM, so in essence, there is
double I/O for every file moved.

Jerry Lawson
jlawson AT itthartford DOT com
________________________Forward Header________________________
Author: INTERNET.OWNERAD
Subject: Netware Include question: Backing up another server
11-08-96 02:19 PM

I am trying to backup netware server B from Netware server A. My
include is something like:

include B\*\...\*
include A\*\...\*
exclude A\vol1:\...\*

The server A is getting backed up, but not  a single file from server
B.  I tried variations indicating volume names for the second server
(including volume names instead of using the * for all volumes)
without any success.

Can ADSM do incremental backups from a netware server other than the
one where ADSM is running?