This README accompanies

	o GETNDS.NLM (usage: LOAD GETNDS)
	o PUTNDS.NLM (usage: LOAD PUTNDS)

GETNDS copies the NDS data files to SYS:SYSTEM. PUTNDS will restore them
to their original destination. Both pieces are now contributed to the
public domain. However, the author reservs all rights.

GETNDS does not copy login scripts etc. Only the pure NDS data will 
be copied.

PUTNDS will rarely be used. Lost partition information should be recovered
from other replicas on the network instead of using PUTNDS. It is included
here as a kind of last resort one may try before attempting to rebuild the
whole DS from scratch in case something bad had happened.

Let me warn you: PUTNDS will overwrite the existing NDS no matter what.
You will loose objects you created in the DS you are about to overwrite.
Also, any application reading and writing information to the database
through NDS will be affected and receive unpredictable results. Also, appli-
cations might do actions to NDS while it is written. So be sure you are the
exclusive user across the network.

Since the NLM does not know the environment you run in (multi-server 
replicas etc) it is running DSREPAIR at the end of the session. 

Please note that by using the software you will take all responsibilies.
No charging me with "I lost my 4000+ object DS", please. Testing has been
done on a 4.01 server pretty throughoutly, though. Just to keep the lawyers
happy.

In any case, if you are in doubt about the problems you might have which
lead you to use PUTNDS, consider to call professional help first (i.e.
Novell Support or get a CNE on site). 

Please do not consider GETNDS/PUTNDS as a replacement for a backup since
it does not copy any trustee information.


	September 11, 1993			Bernd Kunze



