Based on this
post and this
post, a blogger (who will
remain anonymous) sent me this little gem.  More suggestions most
welcome

Based on Ed’s
post today (where the logic of
the customer was truly lost on me), I wanted to put together some "priceless"
advertisements on Domino clustering (or domino in general).  For example:

"New  Shared Disk Array -
€18,000….

Implementing  Active/Passive clustering
using MS Exchange for your company – €10,000

Look on the CTO’s face when the Disk
Array dies and the IT department cannot restore the Exchange folders -
"Priceless"

Get real data resilience- Use Domino"

Just a thought……  I am sure
the more eloquent of you lot can put together far far better ones then
this…..

I noticed this on an ND654 server yesterday
when completing an audit for a customer.  It seems that the mail stats
have become more granular from the outset.  If you type in "Sh
Stat Mail" on the Domino console, you get the usual mail statistics
but with some extras.  See the entries I have highlighted below:

Mail.AverageDeliverTime = 16

  Mail.AverageServerHops = 1

  Mail.AverageSizeDelivered = 18

  Mail.CurrentByteDeliveryRate
= 0

  Mail.CurrentByteTransferRate
= 0

  Mail.CurrentMessageDeliveryRate
= 0

  Mail.CurrentMessageTransferRate
= 0

  Mail.DBCacheAged = 10

  Mail.DBCacheEntries = 1

  Mail.DBCacheForcedOut = 0

  Mail.DBCacheHighWaterMark = 2

  Mail.DBCacheHits = 7

  Mail.DBCacheMaxEntries = 513

  Mail.DBCacheReads = 18

  MAIL.Dead = 0

  Mail.Delivered = 20

  Mail.DeliveredSize.100KB_to_1MB
= 4

  Mail.DeliveredSize.10KB_to_100KB
= 7

  Mail.DeliveredSize.1KB_to_10KB
= 6

  Mail.DeliveredSize.Under_1KB
= 3

  Mail.Deliveries = 18

  Mail.DeliveryThreads.Active =
0

  Mail.DeliveryThreads.Max = 8

  Mail.DeliveryThreads.Total =
2

  Mail.Domain = MOONEY

  MAIL.Hold = 0

  Mail.MaximumDeliverTime = 19

  Mail.MaximumServerHops = 1

  Mail.MaximumSizeDelivered = 70

  Mail.MinimumDeliverTime = 15

  Mail.MinimumServerHops = 1

  Mail.MinimumSizeDelivered = 1

  Mail.TotalKBDelivered = 1,067

  Mail.TotalKBTransferred = 146

  Mail.TotalKBTransferred.SMTP
= 146

  Mail.TotalPending = 0

  Mail.TotalRouted = 25

  Mail.TotalRouted.NRPC = 20

  Mail.TotalRouted.SMTP = 5

  Mail.Transferred = 4

  Mail.TransferredSize.10KB_to_100KB
= 2

  Mail.TransferredSize.1KB_to_10KB
= 2

  Mail.Transferred.SMTP = 4

  Mail.TransferThreads.Active =
0

  Mail.TransferThreads.Concurrent.Highest
= 1

  Mail.TransferThreads.Concurrent.Max
= 4

  Mail.TransferThreads.Max = 8

  Mail.TransferThreads.Total =
2

  MAIL.Waiting = 0

  MAIL.WaitingForDIR = 0

  MAIL.WaitingForDNS = 0

  MAIL.WaitingRecipients = 0

Now this could be me, but are these
statistics new?  They are also available in the ND7 console.  The
stats above are from my server (no, I don’t publish customer’s stats!).

One of the most common issues I come across on sites is that clusters don’t
always have replicas of all the databases.  For example, your mail
file is on server A but not on its cluster, Server B.  Previous to
Notes6, if you registered a person and created a mail file, you had to
manually place a replica of the file onto the other server.  New registration
options and even the registration settings document in ND6 have helped
greatly, giving the administrator the option to create the replica when
registering the user.
But the standing issue still remains, how can I check that each cluster
member has all the replicas it needs?  Well, there are numerous ways,
including scripting and tools on the sandbox site.  But a simple check
on a two-way cluster is to run the Decommission Server Analysis tool.
You will find the DSA tool in the
admin client, under SERVER/ANALYSIS tab.  Go to the TOOLS PANEL on
the right and click on "Decommission Server"


The DSA tool is a part of the administration client and is often forgotten.
 Its primary purpose is to analyse a server you are about to decommission
and compare it to its replacement.  It will tell you what connections,
certificates, configurations, access controls that are different on each
server, to assist in a smooth decommissioning process.
It also checks replicas.
By running the DSA tool the output report will list non-matching replicas
between the servers.  Give it a go or click
here for more details.

For the record.

I really like this
backup software for Lotus Domino.
 It is scalable and fast and gives you the ability to restore a single
document from a database if you need to, instead of restoring an entire
database to a temp drive and then copying in the deleted document.  But,
local resellers of this kit are causing themselves problems by insisting
that each domino server has to have transactional logging running to use
this software.  It doesn’t.  You only require transactional logging
to be enabled if you want to utilise the incremental logging facility of
the product.  If you still run nightly full backups, you do not need
transactional logging enabled.

In production environments, Transactional
logging can increase performance of your servers if your hardware is appropriate.
 Do not implement transactional logging on the same raid array as
the domino\data directory.  Performance is hurt… bad.  If you
wish to implement this feature, do so on a separate disk array with
a separate controller.

Some re-working this weekend.  Hopefully,
next time you see this site, you will be really looking at a DB2 backend.
 Why?, well why not I suppose.  A Blogsphere site does not really
require DB2 backends to run it (as this site in total is about 30MB), but
it will be nice to run it for a while anyway.

I upgraded one of our primary clients to ND654 last week.  There are
a completely web based Domino intranet.  400 users all running iNotes
for mail and all business applications running as Domino web based apps
(including full document management).  There are numerous enhancements
to the iNotes mail file in 6.54 including several little performance tweaks,
including iNotes "lite".   Read
this excellent Developerworks document for details.
 By enabling some of these features, performance was improved on mail
with no impact on user experience.  Worth a look.

A few months back, I
posted about a 2GB attachment being sent in ONE email.
  I thought that was it…. no way that would be beaten.  How
silly I was.  I have reputable information from a new customer site
(promised as true).  This one takes the biscuit, the biscuit tin,
the crock, kitchen and bakery.  Yep guys, a 4 1/2 GB attachment was
attempted to be sent through an ND6.52 server off an R5.012 client not
two weeks back.  There was no limit on attachment sizes and the Domino
server basically hung up its hat trying to route it.  Just a shame
I don’t have a screenshot this time.

Did not have time to post much last
week, but this one made me smile.  While upgrading Notes Servers/clients
on a customer site (500 users) to ND654 I used the Desktop policy to force
Notes Mail file upgrade to the latest Domino Web Access (iNotes6.ntf) template
as soon as their client software was upgraded.  All went very well
but one user complained that now when they delete their mails, they disappear
(into the trash folder).  No longer do they appear with an "X"
beside them.  This user found it most frustrating because they often
changed their mind on what they wanted to delete.

This was a first for me.  Am I
alone here?

Click
here for details

"MOBILE ADMIN 3.0 NEW FEATURES:

- Palm devices, such as the TREO or Tungsten.
- Windows Smartphone and Pocket PC, as well as Nokia Series 60 and 80 devices
(in final stages of beta now – for more information, please email beta@idokorro.com)
- Additional BlackBerry Enterprise Server 4.0 management features, including
the ability to "kill" handhelds, set passwords, lock handhelds,
and set enterprise activation passwords
- Ability to browse the network and add servers to be managed by Mobile
Admin from the handheld device"