Symantec Backup Exec

To recover the Lotus Domino server, databases, and transaction logs when archive logging is enabled

1. Restore the non-database Domino server files (*.id and notes.ini).

   If necessary, reinstall but do not configure the Domino server and then restore the non-database Domino files, which include the notes.ini and *.id files. Use the same directory structure, directory location, and logdir path as was created in the original installation. Do not launch the server after reinstalling it.

2. In the Restore Job Properties dialog box, under Settings, click General.

3. Check Restore over existing files.

4. Using a text editor, change the TRANSLOG_Status setting in the notes.ini file on the Domino server to 0.

   For example, TRANSLOG_Status=0

5. Using the Backup Exec Agent for Lotus Domino, restore the last transaction log backed up prior to the loss of the active transaction log.

6. Verify the transaction log restore was successful.

7. Shutdown and then restart the Backup Exec Agent for Lotus Domino.

8. Delete all transaction logs except the transaction log restored in step 5, from the Domino transaction log directory.

9. Using a text editor, change the notes.ini file for the Domino server to match the following:

   TRANSLOG_Recreate_Logctrl=1

   TRANSLOG_Status=1

10. Run a full restore of the Domino databases or a point-in-time state within the archived log extents.

    Backup Exec automatically restores all DAOS NLO files along with the DAOS-enabled databases. In addition, Domino automatically recreates both the daos.cfg file and the daoscat.nsf when you restart the Domino server.

    After the full restore finishes, the TRANSLOG_Logctrl parameter in the notes.ini file is reset to 0.

11. Start the Domino server. Disaster recovery is complete.

12. If monitor change journal was disabled prior to beginning the disaster recovery process, you must re-enable it.

    See Re-enabling the monitor change journal.