Archive for the ‘Database Properties’ Category

The hardships of enourmous mail files.

I manage an environment with over 1800 mailboxes that are greater than 2GB (including hub and cluster mate copies) and 66 above 10GB. The physical limit of a Domino database is 64GB.

However, anything beyond 2GB becomes very difficult to manage and here’s why.
1. Databases become corrupt very often.
2. Running Fixup or Compact on a weekly basis as part of Domino routine maintenance becomes problematic because the server is always running the maintenance on the databases. In fact, you’ll need to split up fixup and compact to run on specific directories during different evenings of the weeks. You may even want to run Updall on different directories different nights of the week.
3. Backups take forever and may not finish before the beginning of your work day.
4. Opening the mailboxes takes a very long time because it has to index the inbox every time you open it (if the user does not file messages to folders, which most don’t).
5. You pretty much can’t have full text indexing turned on for the server copies of the database because the full text indexing will be continuous around the clock on your server, not to mention more disk space required on server.
6. We’ve had some very strange things happen with Blackberry Enterprise Server accessing very large mailboxes. Specifically, We have had instances where a Domino server running Blackberry Enterprise Server (BES) can have frequent outages in IDTable code when working with large ID tables, which causes the server to crash. See technote titled “BES server crash in IDTable code”

7. If users have local replicas of their mailboxes, sometimes their hard drive is not large enough, sometimes the local replica becomes corrupt on the hard drive because no maintenance (fixup/compact) is ever run on it.
8. Creating new replicas onto new servers can take a week across the wire.

The list goes on.

These are real world examples of issues that I come up against every week. The best practice is to have quota policies in place that the upper management supports.

The second major thing to note here is that a proper archiving solution needs to be implemented. The local archiving that is built into Notes is often times not sufficient if you have so many enourmous mail files.

SuperAdmin Review

I posted last week about the SuperAdmin OpenNTF project. I installed it last Friday and let the agent run a while, and came in this morning to check out what it could report.

Keith Brooks commented in the last post that the ability to see the templates and ODS has been available in the Administration client since 6.5, plus the ability to modify the Administration Server (not see it). This is all true, but I still find the tool very useful for cleaning up ACL and administration server inconsistencies.

Here’s my review: Read the rest of this entry »

SuperAdmin to the rescue!

Yesterday, I posted about setting the administration server on all of my mailboxes at the suggestion of my colleague Jean-Yves Riverin

Well, today, I received yet another great tip from him. He pointed me to an OpenNTF project called SuperAdmin by project chef Declan Lynch

Here’s the synopsis:

Have you ever wondered if you have dead mailfiles sitting on your server taking up space, or if the all your databases are on the latest ODS version, or if the administration server in the ACL is set correctly on all databases, if so then this is the app for you.

Written by a notes admin for notes admins all the information that you need to make sure your Domino environment is running like a well oiled machine will be waiting for you once you deploy SuperAdmin.

I’ll setup it up and review it in a subsequent post.

LZ1 compression on 6.5.6 – Does it replicate?

I’m doing some testing on my Domino 6.5.6 FP3 servers.

I’ve got a bunch of mailboxes that did not already have LZ1 compression enabled (mostly archive mailboxes and a few mailboxes scattered around on remote servers). Mostly, it’s been turned on, and it’s definitely turned on in all of our mail.boxes.

The only reason that it is not turned on for all mailboxes up to this point is that we had to disabled it in our OpenNTF1.7b template because we have a couple of Mac OSX users. When design would run on the server at 1AM every night, the LZ1 property would be turned on for these 2 Mac users even though, we had manually turned it off. It was weird since, technote 1176010 entitled “Which Database properties are affected by a Design Replace or Refresh” clearly indicates that LZ1 compression is only affected by design replace and not design refresh.

These Mac OSX users would have problems with their attachments. There used to be technote number 1193756 on the issue, but it’s gone now. IBM must have fixed the issue and removed the technote.

I’ve enabled LZ1 compression for all databases now with the admin client (advanced properties).

Now, I’ve set the DEBUG_ENABLE_LZ1_REPAIR=1 in our * Configuration document so that it gets written to the notes.ini of all of our servers. Read the rest of this entry »


I'm currently available
for Lotus Notes / Domino consulting engagements.


Connect with me: