Only when you add a extra view in your servers’ maildatabases ($Conflicts), you can see if you are infected with it. One of my customers noticed a huge amount of replication events on Sundays between 00:12 AM – 02:00 AM. We couldn’t find any problem or evidence for this behavior.
Situation in the IBM Domino infra:
2 IBM Domino servers in a MailCluster
1 IBM Domino server for backup purposes and contains a replica of all maildatabases.
Every Sunday we see a lot of replication events between the Domino servers in its own cluster and to the backup server.
Only when we added an extra view to see if there any save conflicts, we noticed there was a bigger problem then we ever could imagine.
In 2700 maildatabases we counted multiple hundred of thousands of save conflicts. These save conflicts where only found on Meeting Calendar items.
And when we checked the items and their invited users, we discovered that there is ALWAYS a user in it who is in the Adminp “rename person” process.
After correlate the users between calendar items and the Adminp flow, we discovered that the save conflicts are created in the finalizing stage ProxyAction 185 Rename user and calendar entries and profiles in mail file.
During this process, all servers where Adminp can find a database with a renamed user inside it, Domino performed the rename. Not only on your home/mail server, or the administration server, no….on ALL servers.
But now its finally solved in 10.0.1FP1: http://www-10.lotus.com/ldd/fixlist.nsf/SPRNum/FE47E04B449CEA44002583D1006DEAD6?OpenDocument&ca=drs-fo
Visits: 252