Restoring a dsbk backup without verification

There may be a need to restore a dsbk backup to a new server without contacting other servers in the tree.  This could be a disaster recovery test or an actual disaster situation in which multiple servers are lost.  When attempting the restore, the job fails with an error.  The log shows:

RestoreFile::verifyStatus
Server: \T=tree-name\dc=foo\CN=servername
   Replica: \T=tree-name
      Status: ERROR = -626
Error!: -626
Error: -626 occured in DSBperformRestore
Database restore finished
Completion time 00:04:28
1 Error!

The dib directory contains RST.db, RST.01, and RST.lck files as well as an RST.rfl directory.  Renaming these files to nds.* and attempting to open the agent fails with a -663 ERR_DS_LOCKED error.

Use the following steps to restore the dsbk backup to a new server.

* NOTE: The restore verification process exists for a reason.  If you are going to bypass the verification process be sure that you understand the implications and accept the risks.

• Install the appropriate eDirectory version to the server
• Install the appropriate Security Services patch
• ln -s /etc/opt/novell/nici.cfg /etc/nici.cfg  (This step is to address the "Unable to load backupcr module" error mentioned in KB 3950804)
• Edit /etc/dsbk.conf and add the line: /tmp/dsbk.command
• touch /tmp/dsbk.command
• dsbk restore -f /tmp/dsbk_file -l /tmp/restore.log -r -a -o -n -v -k

The restore can be monitored by executing tail -f against /tmp/restore.log