I do believe this is a problem with the version of TSAs in Netware 5. I am
pretty sure that SP5 solves the problem.
Quoting "Keith E. Pruitt" <[EMAIL PROTECTED]>:
> Can anyone tell me the correct way to backup the NDS on Netware 5.0 from
> the command line? Right now I'm forced to manually back it up from the
> web client. My dsm.opt file has the statement 'DOMAIN nds all-local'
> included just as I have seen suggested from the posts here. The backup
> user that was created has Full rights from the ROOT level all the way
> down. If you back up just files, there is no problem. As soon as you do
> an incremental of the NDS it starts and backs up everything at the root
> level OK but when it starts with the other OU's, none of the leaf
> objects keep their context and therefore fail with a message stating
> that there is no such entry in the directory. For instance, a user in
> the Chicago container named KPR should be .[ROOT].O=MBP.OU=CH.CN=KPR.
> The NDS backup gets to that user and reads the following
> 09/26/2000 17:44:07 There is no such entry in the directory.
>
> 09/26/2000 17:44:07 ANS1228E Sending of
> object '.[Root].O=MBP.CN=KPR' failed
> 09/26/2000 17:44:07 ANS1301E
> Server detected system error
> I'm wondering why does it seem like it's treating all the objects in
> the other containers as objects in the ROOT but the web client backup
> seems to be working fine?
> Any help is appreciated.
> We use Netware 5.0, SP3 ADSM client v3.1.0.8, TSM server v3.7.3.62
> SMDR v5.03 3/12/99
>
>
> TSA500 v5.01 2/19/99
>
>
> TSANDS v5.00 9/10/1998
> Keith Pruitt
> Network Administrator
>
