MONITORING
Use this checklist for your transaction logging planning.
There are three logging styles to choose from -- circular, linear, and archived. The logging style you choose is also dependent on your disk size and backup strategy.
With circular logging, Domino reuses a fixed amount of disk space (up to 4GB) for transaction logs. After the disk space is used up, Domino starts overwriting old transactions, starting with the oldest. When the space fills up, perform a backup on the databases. You may need to do daily backups to capture database changes before they are overwritten, depending on the server activity level. Use circular logging if the size of the log needed between full database backup intervals is less than 4GB.
Linear logging is like circular logging, except it allows more than 4GB. Use linear logging if the size of the log needed between full database backup intervals is greater than 4GB, and you are not using archive media.
Archived logging creates log files as needed. It simplifies backup and restoration, and provides online and partial backups. The log files are not overwritten until you archive them. With archived logging, you must have a backup utility to back up the filled log extents so that they are ready if needed. If you do not have a backup utility, the server continues to create log extents, fills up the disk space, and then panics.
Improved format for transaction logs
You can set a NOTES.INI parameter to upgrade the format of new transaction logs. The upgraded format is useful if the Domino server has a disk block size different from 512 bytes. Upgraded logs created at server startup will have properly aligned blocks for i/o.
1. Shut down the Domino server.
2. Delete the contents of the transaction log directory.
3. Set the following parameter in the NOTES.INI file on the server:
Related topics