Somewhere along the way (version 5.2.x of the TSM client if memory serves), the 
ALL-LOCAL domain was updated to automatically include NDS backups on servers 
that hold replicas.  I fixed the problem by changing the domain line in the 
dsm.opt file for all of my replica-holding servers (except the one I actually 
perform NDS backups from) to the following.

DOMAIN          ALL-LOCAL -NDS:

That still does an all local backup, but excludes NDS.

Matt Zufelt
Southern Utah University
  
>>> zforray AT VCU DOT EDU wrote on 3/2/2005 9:15 AM:
> We have this Netware system that has been giving us heartburn for a long
> time and we can't seem to get over it.
> 
> The client is 5.2.3.0 (nothing newer since July 2004) since this is a 
> 6.0
> system.  The TSA modules are at the latest level available from Novell.
> 
> The errors (from the DSMSCHED.LOG file) we get usually start with:
> 
> 02/23/2005 01:51:16 ANS1228E Sending of object '.[Root].' failed
> 02/23/2005 01:51:16 ANS1301E Server detected system error
> 
> 02/23/2005 01:51:19 ANS1228E Sending of object '.[Root].CN=Security'
> failed
> 02/23/2005 01:51:19 ANS1301E Server detected system error
> 
> 02/23/2005 01:51:19 ANS1228E Sending of object '.[Root].O=VCU' failed
> 02/23/2005 01:51:19 ANS1301E Server detected system error
> 
> 02/23/2005 01:51:19 ANS1228E Sending of object
> '.[Root].CN=Security.CN=Authorized Login Methods' failed
> 02/23/2005 01:51:19 ANS1301E Server detected system error
> 
> ...........
> 
> 02/23/2005 01:51:58 ANS1228E Sending of object
> '.[Root].O=VCU.OU=ACAD.OU=CPRED.CN=DSWISTOCK' failed
> 02/23/2005 01:51:58 ANS1301E Server detected system error
> 
> and goes on and on for over 16K failed objects.
> 
> It seems to be trying to backup the :NDS eventhough there isn't a DOMAIN
> statement in the OPT file and the book says the default is ALL-LOCAL.
> 
> Supposedly, the userid assigned to the backup process, has FULL rights !
> We even recreated the TSM.PWD file, at least twice.
> 
> The owner of the system asked if they could they be related to the level
> of the eDirectory on the system (8.7.2) ?
> 
> Anyone have any suggestions on resolving these errors ?