Transaction logging is available for Lotus Domino servers running release 5 or later and databases using release version 5 or later On Disk Structure (ODS). Database changes are sent to a transaction log database and then written later to the target database. Transaction logging offers benefits for the following system activities:
- Backup throughput is increased because transaction logs back up quicker than normal databases.
- Disaster recovery is more complete in that data that was stored in the transaction log can be supplemented to the full system recovery so data is not lost. Data that is stored in the transaction log file is written to the database when the log file is recovered from tape.
- Database views are stored in the log file so database views may not need to be rebuilt.
Transactional logging also creates a unique database instance ID (DBIID) for each database. When transactions are added to the log, the DBIID is assigned so that the source database can be recorded. DBIID tags are assigned at the following times:
- The first time transaction logging occurs.
- In some instances when the Compact task is executed, such as reducing file size.
- When fixup is used to correct a corrupted database.
- When a database is moved to a server using transaction logging.
Transaction logging versions
You can choose from three different versions of transaction logging, including Circular, Linear, and Archived. Here are descriptions of each of these transaction logging versions:
- Circular: This version of logging uses up to 4GB of disk space and then begins writing over the oldest log information in the database. The transaction log database should be backed up daily using this deployment version.
- Linear: This version of logging is similar to circular logging, but can use more than 4GB of disk space.
- Archived: This version of logging creates transaction logs as needed. Log files are not overwritten; they are archived. Ensure that the logs are being backed up regularly or the server might run out of disk space.
Implementing transaction logging
Transaction logging needs to be properly planned before it can be implemented. Steps to complete before implementing transaction logging include:
- Make sure the server hardware is properly configured. Use a disk array with at least RAID 1 support and a dedicated disk controller.
- Define a backup plan and use software that supports Domino servers running transaction logging.
- Plan to use logging on all available databases, but remember that only databases using the R5 ODS or later will be able to use transaction logging.
- Decide which version of logging to use (Circular, Linear, or Archived).
To set up transaction logging on the server, follow these steps:
- Using the Domino Administrator, select the Configuration tab, select the Server document, and then click Edit Server Document.
- Select the Transactional Logging tab.
- In the Transactional Logging field, select either Enabled or Disabled.
- In the Log Path field, enter the explicit path to the transaction log database.
- In the Logging Style field, select either Circular, Linear, or Archived.
- The default selection for the Use All Available Space On Log Device is No. If you use the default selection, in the Maximum Log Space field, enter the amount of space in megabytes to be used for the transaction log database.If you select Yes in the Use All Available Space On Log Device field, the next option, Maximum Log Space, is removed as a valid selection.
- Choose Enabled or Disabled in the Automatic Fixup Of Corrupt Databases field. If Automatic Fixup is not enabled, administrators will need to manually perform database maintenance when errors occur.
- In the Runtime/Restart Performance field, choose from the valid options in the drop down menu: Favor Runtime, Standard, and Favor Restart Recovery Time.
- In the Quota Enforcement field, choose from these valid options:
- Check Space Used in File when Adding a Note
- Check Filesize when Extending the File
- Check Filesize when Adding a Note
- Select Save & Close to start transaction logging.