If a disaster occurs and the Lotus Domino archived transaction logging option was enabled, you can recover your Lotus Domino server databases by performing the following steps.
To recover a Lotus Domino server database with archived transaction logging enabled
You may need to reboot the server.
Important! Depending on the extent of the data loss, it may be necessary to install and configure a new Lotus Domino server. Make sure the new installation is configured in the same way as the damaged server, with the same directory structure, location, and log directory path, but do not launch the new server at this time.
You may need to reboot the server.
Note: Restore the database files under full session backup first, then restore database files under subsequent incremental session backups or restore from the last differential session backup. Ensure that the Perform Recovery option is not selected.
You can recover the backup files to the last committed transaction in the most recently archived transaction log extent.
Note: Restore the transaction log files under subsequent incremental session backups or restore from the last differential session backup. There is no need to restore log files under the full session backup.
TRANSLOG_Recreate_Logctrl = 0
TRANSLOG_Recreate_Logctrl = 1
TRANSLOG_Recreate_Logctrl = 0
Note: Alternately, you can also disable the creation of a new control file by removing the following parameter from the notes.ini file:
TRANSLOG_Recreate_Logctrl = 1
Note: You must shut down the Lotus Domino server before restoring database files.
Note: Recover the database files under full session backup first, then recover database files under subsequent incremental session backups only if there are archived log files backed up after that incremental session. There is no need to recover database files under the differential session backup.
When the disaster recovery process is complete, start the Lotus Domino server and execute server tasks and functions.
Copyright © 2016 |
|