Domino Program documents and schedule
Thomas Hampel
6 September 2012Problem: A customer reported Domino would not be responding at a specific point in time, but servers dont crash - they are unresponsive.
Analysis: Looking into the Domino server logs at about the time when the problem reported showed that some scheduled tasks were running.
While scrolling down the logs it became clear that the compact task was blocking access to the server's system databases - in this case log.nsf - which caused the server to ignore incomming requests.
From the end users point of view the server came to an halt while from the servers point of view all was okay.
Action: Getting Domino program documents scheduled perfect could be a long journey. Here is my recommendation on how to do it right.
| Program | Command Line | Schedule | Comments |
| convert | -l mailprimary.ind | 18:50 each day Repeat interval of: 0 minutes Days of week: Sun, Mon, Tue, Wed, Thu, Fri, Sat | Generates a list of mail files by reading people's mail files from the Domino Directory and writes the list into an IND file. |
| compact | -A mailprimary.ind | 19:00 each day Repeat interval of: 0 minutes Days of week: Sun, Mon, Tue, Wed, Thu, Fri, Sat | Archive data but dont reduce the mail file size, thats because compacting will be done thru another program document. |
| compact | -B -S 20 -w | 23:00 each day Repeat interval of: 0 minutes Days of week: Fri | Once per week, reduce the file size if there are at least 20% whitespace in the file Exclude system DB's with option -w , for servers before 8.5.4 this requires the variable DEBUG_ENABLE_COMPACT_8_5=1 Note: Reducing the file size for every file every day will just increase the level of fragmentation and will reduce performance. |
| compact | -b -w | 23:00 each day Repeat interval of: 0 minutes Days of week: Sun, Sat | Make sure the white space is located at the end of the NSF file for better performance when creating new documents Note : Do not run on Friday, due to backup. |
| compact | -b log.nsf | 04:30 each day Repeat interval of: 0 minutes Days of week: Sun, Mon, Tue, Wed, Thu, Fri, Sat | Special schedule for log.nsf after 04:00 when purge has been completed. To make sure the white space is located at the end of the NSF file for better performance when creating new documents. |
| catalog | 01:00 each day Repeat interval of: 0 minutes Days of week: Sun, Mon, Tue, Wed, Thu, Fri, Sat | Updates information in catalog.nsf | |
| updall | 02:00 each day Repeat interval of: 0 minutes Days of week: Sun, Mon, Tue, Wed, Thu, Fri, Sat | Updates existing views | |
| statlog | 05:00 each day Repeat interval of: 0 minutes Days of week: Sun, Mon, Tue, Wed, Thu, Fri, Sat | Record statistics | |
| daosmgr | resync | 23:30 each day Repeat interval of: 0 minutes Days of week: Mon, Wed, Fri | Every second day resync the DAOS repository |
| collect | At server startup only | Remark: Make sure the task is not loaded in the Notes.ini via “ServerTasks=” | |
| http | At server startup only | Remark: Make sure the task is not loaded in the Notes.ini via “ServerTasks=” | |
| rnrmgr | At server startup only | Remark: Make sure the task is not loaded in the Notes.ini via “ServerTasks=” | |
| (n)server | -c "tell sched validate" | 02:00 each day Repeat interval of: 0 minutes Days of week: Sun, Mon, Tue, Wed, Thu, Fri, Sat | Rebuilds the clubusy/busytime |
| (n)server | -c "tell mtc purge 7" | 00:00 each day Repeat interval of: 0 minutes Days of week: Sun, Mon, Tue, Wed, Thu, Fri, Sat | Purge data older than 7 days from the message tracking store |
Optional Program Documents for Specific Server Types
| Program | Command Line | Schedule | Comments |
| (n)server | -c “tell router compact” | 18:00 each day Repeat interval of: 0 minutes Days of week: Sun | This will reduce the file size of the mail.box'es, but will increase fragmentation on disk. Not recommended for servers with high mail volume. |
Of course noone is perfect, so any comments and suggestions for improvements are very welcome !