Let me add a few things gleaned from my (and others) experience with this
process.

1. It is best to get the 5.2.2.3 patch release. It addresses memory-leak
issues in 5.2.2.0.

2. While the recommendation of running the backup "from the server that
holds the master replica" is probably OK in general, use caution (and
testing) with this configuration. I did this and started having all kinds
of problems, due to the high-CPU spikes (documented in a Novell TID)
caused by the TSM backup (100% off and on during the backup). Our primary
eDirectory (aka NDS with LDAP front-end) server handles 20000+
authentication requests per hour (and will grow as we expand the use of
eDirectory). Running the backup from this server, was detrimental.  I
moved it to one of the replica servers and haven't had any issues, so far.

3. Make sure to get the latest TSANDS and TSA600 NLMs from Novell.  In
this same vein, the common thread on this discussion in a Novell
discussion group has been to avoid using TSAFS with TSM (not ready for
prime time) and watch out for the NW6 Service Pack 4 updates. Lots of
issues caused by it.

As always, YMMV !

"ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU> wrote on 01/14/2004
04:42:37 PM:

> Hi,
>
> >>> I need to backup a Netware 6.0 SP3 server with eDirectory (NDS +
> LDAP).
> Do I need to code anything special in the DSM.OPT / INCLUDE or is this
> an
> automatic thing ?  If it is automatic, how can I tell ?  Is it part of
> the
> "server specific" stuff ? <<<
>
> you have two requirements to backup eDirectory:
>
>  - load TSANDS.NLM before loading DSMC.NLM or DSMCAD.NLM
>  - specify the domain "NDS:"
>
> I recommend using the Netware-Server that holds all master-replicas of
> your NDS tree. Second it's useful to configure a separate job for this
> task.
>
>
> >>> Also plan to do a test recovery of this server to another box, to
> test
> the restore aspect, including the NDS/eDirectory piece. <<<
>
> This test server shouldn't be connected to your production network,
> otherwise you'll get a lot of synchronization problems within your
> NDS-tree. In a real-time scenario you have to recreate your new and
> empty NDS-tree before you can proceed with a full-restore of NDS on your
> server, which is holding all your master-replicas.
>
> For further informations regarding restoring NDS you should read the
> many TIDs you can find on http://support.novell.com.
>
> Best regards,
> Wolfgang Bayrhof