If the active transaction log is lost, you can recover the database only up to the transactions contained in the last transaction log.
However, if all of the transaction logs are lost, you must have the following to recover the database:
In addition, if the monitor change journal is enabled, you must disable it in the registry before beginning the Lotus Domino server recovery.
The following steps provide instructions for disabling and re-enabling the monitor change journal in the registry, and then recovering the Lotus Domino server, databases, and transaction logs.
To recover the Lotus Domino server, databases, and transaction logs when archive logging is enabled
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.
In the Restore Job Properties dialog box, under Settings, click General.
Using a text editor, change the TRANSLOG_Status setting in the notes.ini file on the Domino server to 0.
Using the Backup Exec Agent for Lotus Domino, restore the last transaction log backed up prior to the loss of the active transaction log.
Shutdown and then restart the Backup Exec Agent for Lotus Domino.
Delete all transaction logs except the transaction log restored in step 5, from the Domino transaction log directory.
Using a text editor, change the notes.ini file for the Domino server to match the following:
Run a full restore of the Domino databases or a PIT state within the archived log extents.
After the full restore finishes, the TRANSLOG_Logctrl parameter in the notes.ini file is reset to 0.
If monitor change journal was disabled prior to beginning the disaster recovery process, you must re-enable it.
More Information