Disk space required for Transaction Logging
The white paper states 4 meg is recommended for TransLogging
Is there any advantage to using 1G (as thats the drive size that I have)
Disk space required for Transaction Logging
The white paper states 4 meg is recommended for TransLogging
Is there any advantage to using 1G (as thats the drive size that I have)
Subject: Read the Admin help document “Planning for transaction logging”
I think you misread “4 meg is recommended”, I assume it said 4 GB. It is also highly recommended that you use the fasted drive you can, along with it’s own dedicated controller. I suggest you read this document:http://www-10.lotus.com/ldd/today.nsf/Lookup/Transaction_logging
here is an excerpt from the help document…
Comparing transaction logging styles
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.
Subject: RE: Read the Admin help document “Planning for transaction logging”
Thanks Alan, can I just ask one more
As Im new to TL, How often does the logs commit to NSF, I just need to understand that if the logs are backed up every night, at what point do these TLs become useless