Table of Contents
Transaction logging is a real time log of transaction occurring on your Domino server. If you are starting with transaction logging for the first time refer to the article Notes/Domino Best Practices: Transaction Logging.
General Transaction Logging Recommendations for 8.5.x Servers
When working with transaction logging at Domino version 8.5.x, your first decision must be the type of transaction logging. If you are using a backup utility that will manage the transaction logs for you or need point in time recovery, then you will want to use archived style logging. Be aware that archived logs are not cleaned up by Domino automatically. When using archived style logging, you must use a backup utility to clean up the old logs to avoid filling all available disk with old logs. If you are not going to be a backup utility to manage the archived logs or performing point in time recovery, then you should choose to use the circular logging style. The maximum size for circular logs is 4GB and that is the recommended value for all but the smallest implementations of Domino.
One source of confusion over many years is where to place the log directory. It may be easier to state where you should not place your log directory. It should not be placed on the same physical disk as your Domino data directory. That means you may place it within the data directory when using a RAID disk array (like IBM i). For more information refer to Transaction Logging Best Practices hardware recommendations.
Transaction Logging Tips
There are some things that every Domino administrator should know in order to prevent problems with transaction logging:
- Domino must always be able to obtain write access to the transaction log files, thus you should not run anti-virus on the transaction log directory.
- The transaction log tracks database changes through the DBIID. Thus, you should never have multiple .nsf files with the same DBIID. The Lotus Notes client and Domino server will ensure this never happens. However; if you are moving, when copying files or restoring files at the OS level, be sure that you do not accidentally duplicate a DBIID. If you need to make copy or restore a file at the OS level, you can easily protect yourself by running a fixup or copy-style compact on the current database to change the DBIID before you make the copy or restore.
- If you have a problem with the transaction logs, always keep a copy of the log files, console.log and any logasio*.txt files you may have in the IBM_TECHNICAL_SUPPORT directory. Without that information, Lotus Support may not be able to assist you in determining the cause of your problem.
- To determine if a system database should be have transaction logging enabled, refer to the table in the DAOS Best Practices article.
NOTES.INI Recommendations for Domino 8.5.x Servers
To help optimize your transaction logging configuration, there are some NOTES.INI parameters that you should be aware of and may want to set on your Domino server.
NSF_DONT_LOG_MAILBOX_BODY=1: This setting will prevent the message body from being logged for messages in the mail.box file(s). Since the mail.box files are very busy, this can improve the performance and throughput of your mail.box file(s). If your mail files are transaction logged, the message will then be logged at the point the message is delivered rather than at the mail.box files.
RM_NO_LOG_LARGE_OBJECTS=1: No attachments larger than 1 MB placed into the server mail.box file(s) will be transaction logged. This can improve the efficiency of mail delivery for large messages.
Schedule_DisableTXNLogging=1: This setting will disable transaction logging for the scheduling databases (busytime.nsf or clubusy.nsf).
Domino 8.5.x and ODS 51 Updates
Starting at Domino 8.5 and ODS level 51, log compression is not enabled. Transaction Logging will store the data in the same format as the database. If the data is already compressed, it will be compressed in the transaction logs. If the data is not compressed, the data will not be compressed in the transaction logs. What data is being referred to here? It could be data documents, design documents or attachments.
There are some cases where, for performance reasons (most often on system z and IBM i systems), you may want to compress your transaction logs, but not compress your data. In this case there are two NOTES.INI settings that can accomplish this for you:
- NSF_COMPRESS_TXN_LOGS - Compress both design and data documents within the transaction logs.
- NSF_ENABLE_LZ1_TXN_LOGS Compress attachments stored within the transaction logs using the LZ1 algorithm whether or not they have been stored compressed within the Domino database.
Enabling LZ1 compression for attachments
To enable LZ1 compression in your environment, open the Lotus Domino Administrator client, connect to your server, and select the Files tab. On the right panel, select Advanced Properties. Select the option to enable Use LZ1 Compression… and select OK to apply as shown in figure 1 below.
After this option is set, the LZ1 compression will work from this period on all new attachments, everything before this activation will remain the same way (without compression). To covert the existing attachments to LZ1 compression, you can run the compact task with the -ZU parameters.
Enabling design document compression
Open the Lotus Domino Administrator client, connect to your server, and select the Files tab. On the right panel, select Advanced Properties. Select the option to enable Compress database design and select OK to apply as shown in figure 1 below.. In order to compress the design,a copy-style compact must now run on the database.
Enabling document data compression
Open the Lotus Domino Administrator client, connect to your server, and select the Files tab. On the right panel, select Advanced Properties. Select the option to enable Compress document data and select OK to apply as shown in figure 1 below.. In order to compress the existing documents a copy-style compact must run on the database.