Monday, March 27, 2017

How healthy are your Domino System Databases?

Are the System Databases on your Domino servers optimized and healthy? You know, the really important ones that seem to never get maintenance, log.nsf, names.nsf, mailjrn.nsf etc, are they getting huge, sluggish to open, slow to backup, wasting GB of disk space?

DDO makes this often never done Domino and database maintenance as simple as ticking a few boxes, set and forget,. If this is scheduled once a week the difference it makes to Domino is quite amazing.

Here are some screen shots from a customer's server showing DDO taking care of business while the admin was at home enjoying the weekend.

Here's the schedule they run each Friday Night at 10PM, targeting the Domino System Databases for maintenance.

At 10PM DDO ran the scheduled maintenance and we see the following in the log.nsf:

24/03/2017 10:04:32 PM DDO: Info - Running System Database Maintenance
24/03/2017 10:04:33 PM Router: Shutdown is in progress
24/03/2017 10:04:38 PM Router: Mail Router shudown

We can see System databases like names.nsf and catalog.nsf targeted:

We can clearly see by sorting the "Last Compact" column that during the 10PM maintenance on Friday night these System Databases were compacted:

Early the following morning (Saturday), as part of the scheduled 2:30AM DDO maintenance we can see these System databases such as catalog.nsf, log.nsf and names.nsf being defragged, removing the fragmentation introduced via the previous night's Compact maintenance.

The Bottom line here is that everything about this server runs faster and better, this means WAY less I/O and everything else from user response times through to backup windows just runs more efficiently and faster. DDO takes care of this so easily while the admin is at home enjoying the weekend as we see in the customer example above.

More performance means getting more value for this company's Domino investment.

Get more information and a trial version of DDO here.

Monday, March 20, 2017

The easiest way to enable Feature Pack 8 View Separation

In this 2 minute video, we will show how to use DDO to:

- Enable Feature Pack 8 View Separation (NIFNSF) with a single selection
- Direct the View NDX files into their own directory
- Schedule View Separation for all Mail 9 databases
- Schedule a Domino restart at 12:05 am to enable View Separation. Just for good measure, we'll run DBMT over all the System Databases at the same time.
- Schedule DBMT to run at 2:30 am for 2 hours, during which View separation will occur on Mail 9 databases.

One more thing, once that's all done, DDO will defragment the newly optimized NSF files. Optimizing the optimized files - it's just fantastic.

Want to know more ? Why not give DDO a trial run.

Friday, March 3, 2017

IBM Patents out-of-office email.


Thursday, December 8, 2016

DBMT Optimizations in DDO - real world example

Further to my previous post on "DBMT Optimizations in DDO that can reduce its workload by over 90%"  here is a real world screen shot of what is happening at one of our clients.

Now that's optimization.

Why not try DDO for yourself with a free 30 day trial?

DBMT Optimizations in DDO that can reduce its workload by over 90%

DDO includes three optimizations to DBMT that make a dramatic difference in its workload:

The first and most powerful setting is the “Only Compact when Freespace exceeds” fields on the Optimization Schedule.

By setting this field a database can only become a candidate for DBMT compacting when the freespace within it exceed the amount specified. This avoids potentially processing hundreds of database where little, or no, freespace can be recovered. This dramatically reduces DBMT processing times, prevents fragmenting those databases, and prevents unnecessary DBIID changes, which also reduces backup requirements.

Here is an example where only 12 databases exceed the Freespace exceeds setting:

As a result when DBMT runs all other databases are excluded from the compact sub-task of DBMT

DBMT therefore only compacts 12 of the 280+ databases

You can further fine-tune the databases that are excluded from compact processing by adding them to the “Exclude the following databases from DBMT processing field” or adding the directory to the “Exclude the following directories from DBMT processing field”

The end result is significantly less time “compacting for the sake of compacting” and the benefits from there are substantial.

One final note, the DBMT optimizations discussed here are only available in DDO.

Why not try DDO for yourself with a free 30 day trial?

Friday, December 2, 2016

What are the stages of optimization in DDO?

One of the great features of DDO is how it works through its optimization stages automatically to ensure you get the best 'bang for buck' from your Domino server.

The first stage is ensuring database properties on databases inheriting design from the mail template (or other identified templates) are set correctly. Any databases out of line are quickly put back into line.

Stage two optimization ensures databases that need to have DAOS applied, have it. Any new databases created based on the identified template names, get DAOSified. That night a specially targeted DBMT session is run to make it happen.

Stage three optimization is NSF file defragmentation. This occurs when and if required.

Other stages of optimization are core to the product, they include:
  • only running DBMT on databases with active freespace, no more compacting for the sake of compacting.
  • only running DBMT on databases that haven't had maintenance run for a given period.
  • running DBMT index optimisation on all databases.
  • running maintenance on system databases periodically
DDO can also automatically schedule DAOS synchronization, shutdown the mail router before performing maintenance on the mail journal and will do a full NTFS freespace optimization when required.

All this happens in a single package. If you would like to give it a go, check out our website at

Thursday, December 1, 2016

New product - The Domino Database Optimizer – DDO.

We are delighted to announce the general availability of our new product - The Domino Database Optimizer – DDO.

The DDO combines the power of DBMT, with the intelligence of an inbuilt configuration tuner while also integrating everything we’ve learned developing Defrag.NSF. We’ve wrapped it in a single application, with a super easy to use user interface and scheduler.

It is designed to work on all types of storage systems from direct attached, SSD, NSA, SAN or virtual. No matter what storage type you have, it will help you minimize your Domino Servers’ I/O.

With DDO you can:

  • Schedule DBMT with a super easy to use UI
  • Automatically enable advanced database properties like design and attachment compression. If settings ‘drift’ from your set standard they are automatically reset back to conform with what is required.
  • Automatically have databases ‘DAOSified’ based on their design template. Just set and forget. Databases that require DAOSification are individually identified and targeted.
  • DDO intelligently selects the databases requiring DBMT operations based on their last compact date and the freespace they contain – no more spending time ‘Compacting for the sake of Compacting’
  • Schedule database optimization of system databases with the click of a radio button – this easily reduces the size of databases like log.nsf and mailjrn.nsf. Smaller databases open faster and require less time to backup.
  • Automatically defragment databases that require it, further reducing backup times while increasing overall system throughput – we built Defrag.NSF into DDO.
DDO is everything you need to maintain your Domino Databases and keep them in tip-top shape. Just ‘Set and Forget’ and let it do the work for you. Your servers will be more responsive, your backups faster.
For more information please check out our website at and while you are there request a free 30 day trial.

System requirements:

Domino 9.01+
Windows Operating System