Chad Scott

Official documentation is available here.

Notes/Domino 8.0.2 FP1 is now available on Fix Central. This is the first fix pack ever offered for the Notes client. You can read the details here. Note that in addition to the dozens of fixes, there is one configuration change: Streaming Cluster Replication is now re-enabled by default. This was disabled in 8.0.2 due to some bugs that caused it not to work well, but those have since been fixed.

I've worked in Domino support for nearly five years, and in that time I've learned that the various monitoring tools included with the product tend to be drastically underutilized by customers. I think it's largely a problem of quantity; there are so many tools that it can be hard to know where to begin. As such, I'm going to cover a multipart introduction to Domino monitoring to help administrators get started using this powerful suite of features.

We'll begin by looking at statistics, monitoring's most basic building block. Domino captures a wide range of statistics by default, and these can be viewed in the Administration client on the Server -> Statistics tab or by running the console command "show stat". You can drill down on individual statistics through the Admin client or run a modified version of the console command to retrieve specific statistics (e.g. 'show stat Server.AvailabilityIndex'). These are great tools for getting a quick snapshot of a particular statistic, but most of the value lies in tracking statistics over time, and it certainly isn't practical to refresh the Admin client or run the console command repeatedly.

To solve this problem, you can create a Statistic Collection document that, not surprisingly, collects statistics. Once a statistic collection document is in place, snapshots of statistics from your servers will be saved to statrep.nsf, giving you an archive of prior statistics. A word of warning: statrep.nsf can grow very large if you let it. The database has a default document purge interval of 14 days, and you should think long and hard before changing it. Note also that statrep.nsf is not a replica throughout the domain. If you decide to make statrep.nsf replicate to all servers, make sure you plan accordingly. If you have a lot of servers, it's a near guarantee that this database will be huge.

With a Statistic Collection document in place, you will be able to leverage additional monitoring features that will make your life much easier. And really, isn't that the goal of every administrator? I'll cover one of those additional features--statistic charting--in Part 2.

The DAOS development team has published a great best practices guide for DAOS backup and restore. Be sure to check it out.

Heads up on a bug with 2048-bit encryption and DAOS. This problem manifests if you use 2048-bit encryption (not the default) and choose to encrypt NLOs (default). Changing either works around the problem, and a hot fix is available should be available this week if you need both.

The 8.5 InfoCenter has a good overview of basic DAOS troubleshooting tips that can be used to resolve most common DAOS problems. Be sure to check it out.

In case you missed it, there's a fix available for all platforms to address an AdminP issue in 8.5. This is something everyone running 8.5 should install as soon as possible.

If you are having trouble knowing where to begin with 8.5, I recommend starting here. This document has links to almost all of the information you need.

For Domino 8.5, there is no background thread that automatically resynchs DAOS reference counts. My recommendation is to add a manual resync to your regularly scheduled maintenance routines, preferrably during non-peak hours. You can set up a program document as follows:

Program name: (n)server
Command line: -c "tell DaosMgr resync"

Mine runs at 3:00 AM on Sundays.