What is DSREPAIR -RC?
This document (3594642) is provided subject to the disclaimer at the end of this document.
Novell eDirectory 8.7 for All Platforms
Novell eDirectory 8.6 for All Platforms
Novell eDirectory 8.5 for All Platforms
Novell Directory Services 8
Novell Directory Services 7
Novell Directory Services 6
How to restore the NDS database
DSREPAIR -RC is not a replacement for a SMS backup of Directory Services.
DSRepair -RC will create a backup DIB set for all the NDS files, including all stream files. DSREPAIR -RC locks the database as it is running.
This should NOT take the place of tape backup as a regular NDS backup method, however it is very helpful to have, as you can use this file to get a server back into the tree quickly due to corrupt database issue or hardware failure on a server. The backup made with dsrepair -rc is commonly used by Novell Support when there are other servers with existing replicas on other functioning servers in the tree.
In NDS8.x, NDS85.x NDS 8.6, NDS 8.7.x NDS 8.8.x etc - the backup is placed in SYS:\SYSTEM\DSR_DIB directory 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.
Loading DSREPAIR without the -RC switch will allow you to choose the placement of the file.
LOAD DSREPAIR | Advanced options menu| NDS archive options | Create NDS archive. This will allow you to place the NDS archive in the directory you specify.
NOTE: Files created with DSREPAIR -RC or through Create NDS archive can only be restored by calling Novell Technical Support.
Formerly known as TID# 10064386
This Support Knowledgebase provides a valuable tool for NetIQ/Novell/SUSE customers and parties interested in our products and solutions to acquire information, ideas and learn from one another. Materials are provided for informational, personal or non-commercial use within your organization and are presented "AS IS" WITHOUT WARRANTY OF ANY KIND.
- Document ID:3594642
- Creation Date:08-DEC-06
- Modified Date:26-APR-12
Did this document solve your problem? Provide Feedback