For this part of the Guided Tour we will look at the different maintenance options for an individual database.
Configuring individual database maintenance options.
In any of the views you can double-click on a database document to access the Database Details, basic information about the database and also configure specific maintenance options for the database. This makes it very easy for the Domino admin to integrate the traditional Domino maintenance tasks with the scheduled defrag maintenance.
The available options are detailed below.
Exclude from been selected for Automatic Maintenance.
Ticking this box will exclude this database from being processed during the Automatic Maintenance run. You may decide to do this if you do not wish for a certain database to be included in scheduled maintenance for whatever reason.
Manually selected for defragmentation.
Ticking this box will specifically select this database for defragmentation.
Compact the database with option.
Ticking this box will set up the database for compacting with the desired option switch. If a compact option is not specified the default used will be the -b option. Immediately after the Compact completes the database will be defragged to “clean-up” any fragmentation caused by compacting.
Fixup the database.
Ticking this box allows a database Fixup to be configured for the next maintenance run. The available Fixup options are listed below once the box has been ticked.
Monitor Free Space.
Ticking this box enables Defrag.NSF to monitor the free space in the database.
Pre-allocate Free Space.
Ticking this box will enable Defrag.NSF to allocate the configured amount of free space within the database. The “Freespace Ceiling” setting is used to set a freespace (MB) amount that will never be exceeded, (This is useful when large databases are present and the percentage allocations would therefore result in excessive freespace in these large databases).
The default is 100MB but this can be set to the user's preference.
The “Pre-allocate free space” feature is very effective in preventing future fragmentation of the database by ensuring there is always a set amount of free space available within the database for additional data writes.
Once the desired options for the database have been selected, click the Save and Close button. Next time scheduled, or manual maintenance is run the configured database options will be processed prior to the defragmentation of the database.
As shown in a previous blog post, on a Domino 9 server another option available in Defrag.NSF is to target a database individually (or a directory) for integrated DBMT and Defrag maintenance. Simply enter the path information for the file in the Path field provided and set a schedule for when you want this maintenance to occur. This performs a fully automated workflow of the following maintenance as required.
Purges deletion stubs
Expires soft deleted entries
Merges full-text indexes
Updates unread lists
Ensures that critical views are created for failover
Defragments the database
The pic below shows a single mail file (photos.nsf) targeted in this manner.
The resulting workflow of this maintenance is described below, as it happens on the console:
Next up we will look at each tab of the Technical Settings and the different options available on each tab and the options for Performance Reports, Freespace Reports and the Automatic Selection Methods.
Click here if you want to know more about Defrag.NSF