June 6, 1995

//**************************************************************

The JCMD.NLM will allow you to backup and restore the NDS 
simply, quickly, and completely. It also backs up partition
information so that an NDS partition can be maintained
by only one server without fear, provided of course, you
back up the NDS every once in a while with JCMD.NLM.

//***************************************************************

To install JCMD.NLM,

1. ncopy.exe jcmd.nlm sys:\system /v

2. flag sys:\system\jcmd.nlm +ro +sh

//***************************************************************

To BACKUP ALL of your NDS files:

**** Be forewarned that performing the next step will disable all 
logins, logouts, and all read/write requests to the NDS files, so
you'll probably want to do this "after hours".

3. At the server console, 
type:  unload ds.nlm

*** DS.NLM handles all READs and WRITEs to the NDS.
*** You cannot copy (backup) or write-over  (restore) the most 
important NDS files (*.NDS)  while DS.NLM is loaded.

//************************************************************
  
4. load jcmd.nlm

*** Make sure you type HELP at the SYS:\> prompt (at the server console),
so you can see all the options available to you.  Notice the DIR, ATRIB, 
COPY, and DEL commands and parameters. 

5.  At the SYS:\> prompt (at the server console) type:  md nds
*** Instead of  nds, you could have used other valid directory names.
At, this step you are just making a directory to copy your NDS files into.

6. cd _NETWARE

*** This puts you in the hidden SYS:\_NETWARE>  directory where all
of the NDS files are stored.

*** If your NDS has many user objects in it, then you might not want to 
type: DIR at this point too often because all the NDS files are stored in 
this one sys:\_netware  directory , and all the user's (who are in a 
partition "serviced" by this server) login scripts are the unique *.000 
files, and the screen will scroll forever - almost. But, I would suggest 
you type DIR here at least once, so you can take a peak at those 
mysterious NDS files.

No harm done here.

7. At the SYS:\_NETWARE> prompt type:  copy *.* sys:\nds
All of your NDS files will be copied into your  SYS:\NDS directory, ready
for you to copy to tape AND to a safe drive.

8. cd /  should put you back at the SYS:\> prompt.

9. load ds.nlm

That's it for the backup part.

//*****************************************************
 I'm sure you can guess how to RESTORE the NDS files.

1. unload ds.nlm
2. load jcmd.nlm
3. cd nds
4. copy *.* sys:\_NETWARE
5. cd /
6. exit
7. load ds.nlm

That's it.

//**************************************************

Notes:

1.  You can delete ALL the NDS files in the SYS:\_NETWARE> directory
by using the ATTR and DEL commands.

*** This comes in very handy when you cannot "Remove Directory Services"
with "Load Install.NLM". If you deleted all the files in the SYS:\_NETWARE 
directory and then tried to "Remove Directory Services"  with 
"Load Install.NLM", you would get a meesage saying that Directory 
Services have already been removed from this server.
Now, you could reinstall this server into the NDS again, by typing 
"Load Install.NLM" and then "Installing Directory Services" back 
onto the server.

2. I have tested the problem of restoring the partitions after all 
information of that partition has been lost,  except for a backup 
copy of the NDS files made with JCMD.NLM.
And, when I restored the files with JCMD.NLM, I had a perfect restore 
of the previous server and all partition information was restore too. 
The other servers, also recognized and communicated with the newly 
restored server. And, when I ran DSREPAIR.NLM on this server, I 
received no errors. ----> A perfect backup and restore.

3. *** Notice, with JCMD.NLM you do not have to be logged into the network
or the fileserver to be able to copy files to and from the server volumes, 
or to and from the SYS:\_NETWARE directory.


//******  THE CURRENT WORST PROBLEM WITH NW 4.10 and NDS which 
I hope Novell will fix soon:

SCENARIO: Your server is the only server "servicing" your partition in 
the NDS tree. In other words, there are no other replicas of your partition.
 
If you do NOT have a "fairly up to date" (meaning: There have been changes 
made to the NDS such as repartitioning the NDS, or moving server objects 
around in the NDS.) copy of your NDS made with JCMD.NLM and your 
server dies, OR if you do not have any backups of your NDS and your 
server dies, then you have corrupted the NDS forever (or whenever a 
solution can be found) for yourself and everyone else in the tree.

Although the corruption which others outside your partition will 
encounter will be "minor", similar to a benign tumor latched in the 
the NDS forever. The extent of the corruption is this: If, in NWADMIN, 
you click on your partition, you will get an error message which says 
it has a problem accessing subordinate objects (meaning every object 
in that partition is gone forever. You cannot delete the partition. 
To get your server back on line, you will have to install it into a 
new and different named container with a different server name too 
(What will all your users say when you tell them they have to change 
their email addresses, and all email to them is bouncing ?).

The extent to which other objects (users too) outside your lost 
partition will feel the repercussions of your lack of a backup, 
will probably be like not being able to perform CX /A/R/T 
throughout the entire tree. CX /A/R/T will return objects to 
the display only to the point when it runs into your lost partition 
then it will quit. Also, I would think you would not be able 
to perform searches of the NDS with NWADMIN.EXE past your lost partition. 

The NDS is cracked for everyone in the tree.

I'm sure a solution will be sooner or later, but I wish Novell would hurry.

//*************************************************************************

Please take everything I have written here with a grain of salt, and think 
through it for yourself. And, please let me know if you find any 
interesting break-throughs.

Joseph Lynn Flowers, son of Jimmie Joe Flowers
joe_flowers@ncsu.edu
flowers@social.chass.ncsu.edu
June 6, 1995

