6.5 Clustering log messages - failing over from server A to server A

I have a cluster comprised of two servers. I am seeing the following occassional log entries for Users on Server A that DO NOT have a mailfile on Server B:

Failing over from ServerA/Domain!!mail\jdoe.nsf, directing open to ServerA/Domain

Clustering for mail\jdoe.nsf is not enabled in cldbdir.nsf on ServerA.

Any ideas why this is being logged?

Thanks for any input

Subject: 6.5 Clustering log messages - failing over from server A to server A

We’re having pretty much the same problem. We have a 3 server cluster with 2 front end servers (Server1 and Server2) with the mail databases split across them and the third server (Server3) is setup for failover with all mail databases. Right now, the messages are appearing on Server1 for databases on Server2 and no failover event are happening. Everything seems to be working but the logs on Server1 are huge.

Here’s the results from “Show Cluster” on Server1:

sh cluster

Cluster information:

Cluster name: CLUSTER1, Server name: Server1/Domain

Server cluster probe timeout: 1 minute(s)

Server cluster probe count: 4386

Server cluster default port: CLUSTERPORT

Server availability threshold: 0

Server availability index: 26 (state: AVAILABLE)

Server availability default minimum transaction time: 3000

Cluster members (3):

Server: Server2/Domain, availability index: 61

Server: Server1/Domain, availability index: 29

server: Server3/Domain, availability: BUSY

The interesting thing is, Server2 has a higher Availability Index than Server1 and it is generating these failover events