|
This version of DSREPAIR has features which makes it a useful tool to check a 4.0x NDS database before upgrading to NetWare 4.10. To gain optimal 4.10 NDS performance, it is best to check for possible NDS databases inconsistencies
before upgrading. Although this step is optional, running DSREPAIR before upgrading ensures that NetWare 4.10 will perform as designed. For this reason, we suggest that you run this version of DSREPAIR on every 4.0x server before you upgrade. PLEASE READ accompanying DSREPAIR.DOC and UPGRADE.DOC files for complete instructions.
NEWER FEATURES OF DSREPAIR
The following is a summary of some of the features in this version of DSREPAIR that has proven useful to some of our customers. It is hoped that this version of DSREPAIR will allow the user to more quickly resolve possible issues. As you may notice, some of these features have been in previous versions of DSREPAIR.
- Command line switch "/8" will load and automatically run option 8 - "Verify Backlinks and External References".
- Bad volume ID's: Bad volume ID's are characterized by volumes not seen as a Directory Service (DS) object, or is seen as the wrong DS object, when using the map command. If the volume ID is wrong DSREPAIR will delete the ID thus preparing the way of a re-install of the volume object. The volume ID will only be verified if "check file system for valid trustee ID's" is selected. To invoke this option, make sure that there is an asterisk is next to option 6 in the options menu (the asterisk selects the option). Before re-installing the volume object, delete the current volume object that is bad. To reinstall the volume object use the UPGRADE MOUNTED VOLUMES option in INSTALL.NLM.
- Duplicate Time Stamps: No two objects should have the same time stamp. If DSREPAIR does find objects with the same time stamp, delete and recreate one of the objects. Running DSREPAIR with any combination of options will test for duplicate time stamps. It should be noted that duplicate creation time stamps are extremely rare in NetWare 4.0x and virtually impossible in NetWare 4.10.
- Same name Siblings: With NetWare 4.x, objects with duplicate names of different types are allowed, in NetWare 4.10 they are not; this is for simplified use. For example, if a user and a container have the same name and are siblings, NetWare 4.10 will not resolve names properly. The leaf object should be deleted or renamed before you upgrade. This version of DSREPAIR will find siblings of the same name for you. Running DSREPAIR with any combination of options will test for duplicate time stamps.
- External references: External references should be properly backlinked before you upgrade. To verify external references choose option "8" from the main menu in DSREPAIR. External references that do not properly match the real object will be identified. If any improper external references are found, remove the server from the tree and re-install it.
OTHER UPGRADE HINTS
Please read the errata that is found in the found in the NetWare 4.10 box. It is also important that you read, understand, and follow the README.41 file. Install lets you read this document but if you bypass it or would like to review it this ASCII text file is found in the \NW410\INSTALL\ENGLISH\README directory on the 4.10 CDROM. This document covers important limitations of having a mixed 4.0x/4.10 tree. You need to remember that until all the servers in the NDS tree are running NetWare 4.10, you will not benefit from the increased speed, reliability, or features 4.10. For this reason you should upgrade all of yours NDS servers as quickly as possible.
|
