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.