Program DSREPAIR byl určen přímo k opravám databáze eDirectory. Pokud bylo potřeba dávkové zpracování, bylo vhodné znát poněkud více parametrů a vědět, co dělají.

DSREPAIR [options]


- option - Descrition
- Required
-A - Advanced mode
-A0 - Correct the problem (-613 errors) with incorrect syntax on attributes "modifersName" and "creatorsName", the repair strips the two attributes out of schema on the server. 
-A1 - uknknown
- uknknown
-A2 - uknknown
- uknknown
-A3 - uknknown
- uknknown
-A4 - uknknown
- uknknown
-A5 - uknknown
- uknknown
-A6 - uknknown
- uknknown
-A7 - Remove any invalid attribute values from objects in the tree
-A8 - uknknown
-AB - Bypass reference check
- uknknown
-AC  - uknknown
- uknknown
-AD - uknknown
- uknknown
-AF  - uknknown
- uknknown
-AO - Fix Audit Object Mode
- uknknown
-AS - uknknown
- uknknown
-AT - uknknown
- uknknown
-AV - uknknown
- uknknown
-AZ - uknknown
- uknknown
-D <DIB extension> - Repair the DIB with extension <DIB extension>. Defaults to 'NDS' if not specified. The 'NDS' DIB is always closed and locked regardless of the DIB being repaired.
- DSREPAIR -D <DIB extension>
-DR - Destroy replica
-INS - INS Mode - Post NetWare 5 Schema Update
-L - Specify an alternate location/name for the log file. Default is 'sys:system\dsrepair.log'. The path can be any NetWare volume or dos drive, as in 'a:temp.lg'.  Path and filename specified MUST be DOS 8.3 format.
- DSREPAIR -L Drive:\Path\filename
-M - Report move inhibit obituaries, this is used to discover if a move has completed or if a partition is reported as BUSY because there are move inhibit obituaries in a replica that have either not completed processing or that are broken.
(A better way of finding obituaries is to use DSREPAIR -A, "Advanced Menu", "Check External References"; See the Solutions on error -637)
-N [Number of days] - Specifies the number of days old that a net-address property is allowed to be on a user class object. It the net-address property is older than the number of days specified, then it is deleted. This resolves a problem where the net-address is never deleted when a connection is terminated, and results in a reduction of allowed connections to the server. The default is 60 days.
- DSREPAIR -N Number
-OT - Orbiturary time synchronization (Obit Timesync)
-P - Mark all unknown class objects as referenced ( a referenced object is not synchronized ).
-RC - Create a database backup file (SYS:SYSTEM\DSREPAIR.DIB or SYS:\SYSTEM\DSR_DIB\*.$DU)
-RD - Repair Local Database
-RDL - Repair Local Database Locked
-RI - Repair remote server ID's
-RL - Specify an alternate log file. Unlike the L option, the existing file is deleted first instead of appended to.
-RM <partition root ID> - Set this server as the master in the replica ring of the specified replica.
- DSREPAIR -RM <partition root ID>
-RN - Repair network addresses.
-RR <partition root ID> - Repair the specified partition root, check remote ID's in the ring.
- DSREPAIR -RR <partition root ID>
-RU - Unatended replica repair
-RV - Volume object repair
-RVT - Volume object repair followed by trustee check of all trustees on the volume
-U - Unattended mode - useful to run scheduled repairs through CRON
-WM - Check and delete for too many values on the WM:Registered Workstation attribute
- uknknown
-XK1 - uknknown
- uknknown
-XK2 - Highly destructive - last resort - removes all replicas, partitions and objects - leaves behind external references to all objects (See TID #10026822 for more information)
-XK3 - Clears the backlink status of all external references - need to SET DSTRACE=*B in order to force the backlink process to rebuild the backlinks
-XK4 - uknknown
- uknknown
-XK5 - uknknown
- uknknown
-XK6 - Remove rights from traditional volume

DSRepair -rc will create a DIB set backup for the NDS including all stream files, this should not be used to take the place of  tape backup as a regular NDS backup method.  DSREPAIR -RC essentially takes a "snapshot" backup of the database and captures the entire NDS database including all objects, replica and partition information, schema and stream files.

In NDS6.x and NDS7.x the backup will be placed in SYS:SYSTEM\ called DSREPAIR.DIB
In NDS8.x, eDirectory 8.5.x and eDirectory 8.6.x the backup will be placed in SYS:SYSTEM\DSR_DIB\ called 00000000.$DU, the backup will create a new file for every 100Mb of data in the NDS by incrementing the filename e.g. 00000001.$DU. This is only for DSDUMP tools.

Loading DSREPAIR without the -rc switch will allow you to choose the placement of the file and filename if you select 'Create a Database Dump' or 'NDS Archive Options" under the 'Advanced options menu'.

First fix. Remove Directory Services (NWConfig -dsremove). The problem with this fix is it also removes trustee rights. You need to remove the server from the replica ring on all servers in the ring with dsrepair. You also need to remove volume objects and server objects from NDS.

Second fix. If you have a receit DIB set (from DSDUMP or DSRepair -rc), restore it.Immediately run DSRepair -xk2 -xk3 - Advanced Options Menu - Repair Local Database on the server. Remove the server form the replica ring then add it back. Redesignate as master if necessary. This saves the trustee rights.

Postup po DSREPAIR -RC a padu NDS 8.x:
V adresari vytvorit C:\$HWNDS.BAK a SYS:\SYSTEM\HWNDS.BAK, z adresare SYS:\SYSTEM\DSR_DIB zkopirovat soubory do vyse specifikovanych adresaru a u vsech zmenit pripony z $DU na $HW spustit NWCONFIG a dat NDS restore after hardware upgrade.

Postup po DSREPAIR -RC a padu NDS 6.x, 7.x:
Zase je mozne obnovit NDS pomoci struktury adresaru pouzitych pri HW upgrade. Pro obnovu se vyuziva souboru SYS:\SYSTEM\DSREPAIR.DIB. Je potreba spustit INSTALL/NWCONFIG a dat NDS restore after hardware upgrade

Powered by Drupal - Design by artinet