In this series of blog posts we will look at the features of Domino Optimizer in more detail.
Let's take a look at the Scheduling and it's benefits:
The Schedule section provides a simple UI for scheduling optimizer maintenance. This simple interface, eliminates the requirement to use program documents to configure and run multiple maintenance steps in a logical sequence.
Entering a % value in the “Only Compact when Freespace exceeds” column controls which databases DBMT will process during it’s compacting stage. To qualify for DBMTcompacting, the freespace within a database must exceed the value entered here. This avoids potentially processing hundreds of large databases where little, or no, freespace can be recovered. This dramatically improves the “out of the box” DBMT processing behaviour and workload, prevents fragmenting those databases and prevents unnecessary DBIID changes, thereby reducing backup requirements. Databases where freespace exceeds this amount are processed by DBMT in the usual manner.
An Effective Strategy for Optimized Performance
Entering a value in the Only Compact if not compacted in N Days column controls whether each database will be compacted based on how many days since it was last compacted. For example, in the previous screenshot, optimization is scheduled for 2.30am each day and DBMT will be allowed to run for up to 120 minutes. For the days Mon through Sat any database that has not been compacted in the last 5 days and also has more than 10% freespace will be compacted. On the Sunday maintenance (set for 0% freespace) any database that did not get compacted in the last 7 days, due to not satisfying the 10% freespace requirement on those days will be now picked up and compacted (except system databases and others manually configured for exclusion). This type of schedule strategy ensures that those databases where excess freespace was not recoverable would not be unnecessarily compacted during the maintenance cycle but would be compacted once per week on Sunday.
This eliminates the need for using any Program Documents for Compact maintenance.
Then Backup with options – Enabling this option allows DO.NSF to automatically call Domino 12's new backup feature once it's completed database optimization. DO.NSF will automatically run DBMT then defrag the databases (optional) then initiate the Domino backup process. Several immediate benefits of this include:
- Reduced Domino backup times
- Significantly less I/O
- Eliminates the need to schedule Domino backup with clumsy program documents.
Domino Backup Timeout (in minutes)
By default backup of a database times out after 15 minutes. If you have a slow backup architecture or large databases, consider increasing the limit. Increasing the limit to 60 is recommended by HCL.