home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Network Support Encyclopedia 96-1
/
novell-nsepro-1996-1-cd2.iso
/
download
/
netware
/
dsreps.exe
/
DSREPS.TXT
< prev
Wrap
Text File
|
1994-06-21
|
9KB
|
200 lines
NOVELL TECHNICAL INFORMATION DOCUMENT
TITLE: DSREPAIR.NLM 2.01 for NetWare 4.0x
DOCUMENT ID: TID015613
DOCUMENT REVISION: B
DATE: 10JUN94
ALERT STATUS: Yellow
INFORMATION TYPE: Symptom Solution
README FOR: DSREPS.EXE
NOVELL PRODUCT and VERSION:
NetWare 4.01
ABSTRACT:
This file contains the latest version of DSREPAIR.NLM 2.01 for NetWare 4.0x.
------------------------------------------------------------------------------
DISCLAIMER
THE ORIGIN OF THIS INFORMATION MAY BE INTERNAL OR EXTERNAL TO NOVELL. NOVELL
MAKES EVERY EFFORT WITHIN ITS MEANS TO VERIFY THIS INFORMATION. HOWEVER, THE
INFORMATION PROVIDED IN THIS DOCUMENT IS FOR YOUR INFORMATION ONLY. NOVELL
MAKES NO EXPLICIT OR IMPLIED CLAIMS TO THE VALIDITY OF THIS INFORMATION.
------------------------------------------------------------------------------
SYMPTOM
Earlier versions of DSREPAIR did not work with levels of DS.NLM above 296.
SOLUTION
Implement DSREPS.EXE containing DSREPAIR.NLM 2.01, which supports versions
290, 291, 296 and versions later than 296.
Self-Extracting File Name: DSREPS.EXE Revision: A
Files Included Size Date Time
\
DSREPR.TXT (This File)
DSREPAIR.NLM 53025 05-16-94 9:16a
Installation Instructions:
1. Copy DSREPAIR.NLM to the SYS:SYSTEM subdirectory of the server on which it
will be run.
2. At the console prompt of the file server, type the following command:
LOAD DSREPAIR
Solution Specifics:
RELEASE NOTES
This version of DSREPAIR has been enhanced to allow the editing of replica
rings. This README describes this editing and gives examples of how to use
DSREPAIR to correct the errors.
Normal partitioning operations should be done with client utilities NWADMIN or
PARTMGR. This feature should only be used when the MASTER replica of a
partition has been lost because of server/hardware failure and the server will
be reinstalled into the NetWare Directory Services Tree.
Caution should be used when changing a SECONDARY to a MASTER. If a server
containing a SECONDARY is changed to a MASTER and the server containing the
original MASTER is brought back up, there is a possibility that the partition
will have two MASTERS.
Attempting to use older version of DSREPAIR to designate a new master replica
when the master replica has been lost, and the replica is in a split or join
state, creates other errors.
*** WARNING ***
YOU MUST BE SURE YOU ARE USING THE CORRECT VERSION OF DSREPAIR!
Version 2.01 or later can be identified by the following message on the top of
the main screen when the NLM is loaded at the server console:
NetWare 4.02 NetWare Directory Services Repair Utility
Item 4 in the options menu has been enhanced to resolve a problem that occurs
in replica rings for partitions.
To invoke the option, select item 4 under the options menu.
Start the repair in the normal way by selecting "2" in the main menu.
When the DIB (local database on this server) repair has completed, the ring
repair menu will appear. It will list all replica root objects stored on this
server.
This includes types of replicas; MASTER, SECONDARY, READ-ONLY, and
SUBORDINATE. You do not see the SUBORDINATE type from client utilities, such
as PARTMGR.
It is preferred to only change a SECONDARY or READ-ONLY replicas to be a
MASTER replica. Changing a SUBORDINATE to a MASTER will cause all objects in
the replica to become UNKNOWN.
Each replica is assigned a unique number on the left side of the screen. If
there are more replicas than can be displayed on the first screen, you will be
prompted to press a key to see the next screen, and this continues until all
the replicas have been displayed.
You are prompted to select a replica by keying in the number of the replica
that has been displayed. If the replica you want to use is on a previous
screen, you must remember the number it was assigned. You can key in the
replica number of the replica that you want to work on or "0" (zero) to exit
the replica ring edit procedure and continue with the repair.
When you select a replica, you are prompted for the following operation:
1) Change the replica type on this server to a MASTER replica.
This option is used to select a new master replica for a partition that has
somehow lost the master replica. The master replica could have been lost
because the server that contained it has been uninstalled from the NetWare
Directory Services Tree with INSTALL.NLM or the server may have been damaged
or destroyed.
Without a MASTER replica, partition operations, such as split and join, cannot
be performed, because the client utilities first contact the MASTER replica of
the partition to schedule these operations.
In this case, selecting the option to change the replica type to MASTER will
set this server (the one running the NLM) as the MASTER replica in the replica
ring (the list of all servers that contain replicas of the partition).
If you want to set some other server that has a replica of the partition as
the master, then you will need to run DSREPAIR on that server and perform the
operation there.
After changing a SECONDARY or READ-ONLY, there will be confirmation on the
screen that THIS server was found in the replica ring and that it has been
changed to type MASTER. If another server is found in the replica ring that
had been the MASTER, it is changed to a SECONDARY.
Another possible MASTER failure is that all the servers containing a replica
of the partition have been lost. This includes the case where there was only
one replica of the partition and that server has been lost.
When this happens, there may still be SUBORDINATE replicas stored on servers
in the NetWare Directory Services Tree. You will see the partition with the
client utilities; however, when you try a partition operation it will fail,
and when you try to view the servers that contain replicas of the partition,
none will be displayed, because the client utilities do not show servers with
SUBORDINATE type partition roots.
When this type of failure occurs, there is a replica ring of SUBORDINATE
reference partition roots for the partition; however, no real replicas of the
partition exist. Because no replicas exist, there are no copies of the
objects, their properties, or their data left in the NetWare Directory
Services tree.
There may, however, be external reference objects subordinate to the
SUBORDINATE reference partition roots that contain the names of the objects.
These external reference objects were created on these servers because they
needed object IDs to grant rights to the file system for these objects.
In this case, and ONLY this case, you need to change a SUBORDINATE reference
to a MASTER replica. When you select this option you are alerted on the
screen that you will have to run DSREPAIR again on this server. This is
because the subordinate reference objects that were contained by the
SUBORDINATE replica are now subordinate to a MASTER replica.
This is an illegal condition in the NetWare Directory Services database. When
DSREPAIR runs again, it will change the external reference objects to real
objects with a base class of "unknown." Be aware that DSREPAIR will generate
a lot of errors on the objects in this replica when this takes place.
At this point, you have a MASTER replica of the partition, and it contains
some but probably not all of the objects that were in the original replica.
However, these objects all have the object class of UNKNOWN, and they have no
properties or data.
You can restore the replica from a tape drive with SMS, which will restore all
the properties and data for these objects, or to clean up the tree, delete all
the objects in the replica. Then join the partition root object with the
parent partition, which changes the object from a partition root to just a
container, and then delete the container object.
You should always log the output of dsrepair to a log file, and check the log
file after the repair to see if objects in replicas have been damaged. If so,
the objects have been repaired or deleted in the LOCAL DATABASE ONLY. Further
operations, such as removing the damaged replica from the server and
reinstalling it again to replace the damaged objects with a good copy may be
necessary.
_Verified by customer
_Verified by Novell
----------------------------------------------------------------
Any trademarks referenced in this document are the property of their
respective owners. Consult your product manuals for complete trademark
information.
----------------------------------------------------------------