Error: -6034 when restoring the eDirectory database using DSBK.NLM.

(Last modified: 05Oct2005)

This document (10099184) is provided subject to the disclaimer at the end of this document.

fact

Novell NetWare 6.5 SP3

Novell eDirectory 8.7.3 for NetWare 6.5

DSBK.NLM

symptom

Error: -6034 when restoring the eDirectory database using DSBK.NLM.

Error: -755 when restoring the eDirectory database using DSBK.

Error: -666 when restoring the eDirectory database using DSBK.

Error: -625 when restoring the eDirectory database using DSBK.

How to troubleshoot eDirectory errors with the log produced by DSBK.

change

Using DSBK to backup and restore the eDirectory database.

note

DSBK should only be used by someone who has an advanced understanding of eDirectory, understands the concepts behind eDirectory's database roll forward logs as well as the ramifications of performing a restore of that database. Please carefully read the documentation carefully. It can be found at http://www.novell.com/documentation/edir873/index.html.

Below are sections of particular importance.
- Administration Guide - Backup and Restore
- Administration Guide - Troubleshooting
- Administration Guide - Maintaining Novell eDirectory
- Administration Guide - Managing Partitions and Replicas

The LogicSource for eDirectory is another valueable guide in understanding how eDirectory maintains integrity.

cause

The above errors indicate a misuse of the DSBK utility in an attempt to restore eDirectory's database.

Good practice requires the following before using DSBK:
- The administrator has enabled logging.
- That a current roll forward log exists preferably on a volume other that where the database resides.
- Non-current roll forward logs of the current set have been backed up with the last dib set backup.
- These logs plus the current one are all present when attempting a restore.

NOTE: If all volumes have been destroyed, the current log is lost and an emergency restore must take place this can be done easily in a single server tree environment. If the tree contains multiple servers it is recommended that you contact Novell before the restore of a server so that guidance may be provided to ensure there will be no damage done to the existing tree.

Below is an example of a DSBK log.

|==================DSBackup Log: Backup================|
Backup type: Full
Log file name: sys:nds\nds.log
Backup started: 2005-9-27'T10:57:17GMT
Backup file name: sys:nds\ndsbk
Server name: \T=HVTREE\O=provo\CN=HVSERVER1                           Current Roll Forward Log: 00000001.log
DS Version: 1055279
Backup ID: 4338D835
Starting database backup...
Database backup finished
Completion time 00:00:00
Backup completed successfully

Here is the backup. We can tell that roll forward logs (RFL) were properly turned on prior to taking the backup. There is currently only one RFL, the current one.

|==================DSBackup Log: Restore================|
Log file name: sys:nds\nds.log
Restore started: 2005-9-27'T11:2:43GMT
Restore file name: sys:nds\ndsbk
Server: \T=HVTREE\O=provo\CN=HVSERVER   Replica: \T=HVTREE  Status: OK
Starting database restore...
Restoring file sys:nds\ndsbk
Database restore finished
Completion time 00:00:13
Restore completed successfully

Here is the restore. There is only one RFL and it is the current one. The current RFL is correctly in place and the restore was successful. This server's transitive vector is the correct time since the current RFL was present and therefore matches what the other servers in its replicas are expecting in regards to current timestamps.

|==================DSBackup Log: Restore================|
Log file name: sys:nds\nds.log
Restore started: 2005-9-27'T11:3:40GMT
Restore file name: sys:nds\ndsbk
Starting database restore...
Restoring file sys:nds\ndsbk
Server: \T=HVTREE\O=provo\CN=HVSERVER   Replica: \T=HVTREE    Status: ERROR = -6034   Local TV   Remote TV s4338d361 r02 e002   s4338d992 r02 e002                s4338d49f r01 e001   s4338d992 r01 e003
Error!: -755
Database restore finished
Completion time 00:00:11
1 Error!

Here we see that a second restore was made. This utility should not be used to simply perform another restore since it is now using a stale RFL. Another backup should be performed in order to get a new and current RFL. The restore completes. However, when DSBK compares this server's transitive vector timestamp to the more current one the other servers know of, DSBK detects the difference and throws a error: -6034" as well as a error:-755. This means the times do not match. It is warning that there could be data that was lost when DSBK overwrote the database without a current RFL.

|==================DSBackup Log: Restore================|
Log file name: sys:nds\nds.log
Restore started: 2005-9-27'T11:4:52GMT
Restore file name: sys:nds\ndsbk
Starting database restore...
Restoring file sys:nds\ndsbk
Server: \T=HVTREE\O=provo\CN=HVSERVER   Replica: \T=HVTREE         Status: ERROR = -666          Error!: -625           Database restore finished
Completion time 00:04:05
1 Error!

Here is yet another restore without first performing a backup. The -666 error could indicate several things with serious transitive vector problems being the most likely. In addition this could also result from restoring the dib the the wrong server or a mismatch between ds and dsloader versions. The 625 could be due to a server down or restoring incorrect referrals to the other servers in the tree. Bottom line, the procedure was performed incorrectly.
_____________________________________________________________________________________________________________________________________________

In summary, restoring eDirectory is not something to be taken lightly nor is it an operation that should be performed by someone who does not have extensive experience in eDirectory's operation. To not carefully consider how backups are made, whether to restore, how to restore and its ramifications in doing so can lead to serious inconsistancies in the server dibs which can lead to tree wide data loss. The RFL is crucial. It must be present, it must be current. The other logs of the set must be present prior to the restore. The current RFL should be on a volume other than the one that contains the dibset. If this is an emergency and all drives were lost the restore should be done off the wire so the other servers can no longer see it. The restore is performed, all replicas must be removed via a dsrepair -xks then all the replica rings of which this server was a member must be cleaned up. After this is completed this server can be returned to the wire where its external references can be successfully backlinked. Then and only then can the previous replicas be added back.

document

Document Title:	Error: -6034 when restoring the eDirectory database using DSBK.NLM.
Document ID:	10099184
Solution ID:	NOVL103765
Creation Date:	05Oct2005
Modified Date:	05Oct2005
Novell Product Class:	Novell Directory Services

disclaimer

The Origin of this information may be internal or external to Novell. Novell makes all reasonable efforts 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.
Any trademarks referenced in this document are the property of their respective owners. Consult your product manuals for complete trademark information.