We run two Domino 8.5 servers in a clusterNow and then we get (one to many) replication conflicts of resources in clubusy.nsf
The creation date of the replication conflict documents is 02:nn h
Notes.ini parameter SERVERTASKSAT2=UpdAll
This problem occured already with Domino 8.0.2
Deleting the conflict document and 'tell rnrmgr check “” does not solve the problem.
Deleting the main document and 'tell rnrmgr validate “” creates a new document but the busytime info is not available
Rebuilding the two clubusy.nsf solves the problem until the next replication conflict occurs.
Technote http://www-1.ibm.com/support/docview.wss?uid=swg21141060 has been observed
Questions:
-
why are the conflict documents created
-
how can we handle busytime problems of single resources
Subject: Solution: exclude clubusy.nsf from replicating in the connection document (between the two cluster mates).
Solution: exclude clubusy.nsf from replicating in the connection document (between the two cluster mates).
Subject: BAD idea
If you exclude replication of the busytime data then you would actually make matters worse if your R&R server goes down and cluster failover happens. The data in busytime on the clustermate would not be current so RnRMgr could wind up double booking things because the busytime data was incomplete.
The better option is to open a ticket and we can dive further on the issue.
Bruce
IBM
Subject: Misunderstanding…
the cluster replication is still active, it’s only the 2-hourly additional replication I have disabled for clubusy.The replication history proofs it.
By the way: this has been recommended by Lotus in PMR 05974 124 848 
Subject: opened a PMR with IBM
05974 124 848
Subject: Great, please let us know the resolution.