Many documents are replicated, for no good reason

Hi,

The situation:
- one database X
- two servers, A and B, two different Domino domains
- one Notes client PC
- there's a replica of X on A and B, and on the client
- the servers don't replicate, they're not cross-certified
- the client is certified in both domains
- the client replicates often (in the background) with server A, to test modifications to the design
- every now and then, the client replicates with server B
- as long as the client replicates with 1 server, replication is fast
- once the client switches to the other server and does a manual replication, many documents seem to have been modified (50%)

I assume it's not a rights issue, since both servers are in the ACL as Manager and the user is Manager as well.

1. Explanation??
2. Solution, except from cross-certifying both servers??

Some day the servers will be cross-certified, but I want to make sure that they don't keep on replicating the same documents over and over again...
LVL 46
Sjef BosmanGroupware ConsultantAsked:
Who is Participating?
 
doninjaConnect With a Mentor Commented:
If you combione the following entries into your client Notes.ini you shoul be able to see which documents are replicating and therefore work out what may have changed. Works on R7/R8 basic clients not tried on 8.5+

Debug_Outfile=C:\TEMP\DEBUG.TXT
Debug_Console=1
Debug_Repl_All=1
LOG_REPLICA=5
Client_Clock=1
0
 
doninjaCommented:
Could there be a date time difference between the servers and replciation history is not picking up the right check date.
Also it isn't deletion stubs that are getting replicated by any chance.



0
 
Sjef BosmanGroupware ConsultantAuthor Commented:
Time difference: it's possible, I'd have to check. One server is Windows, the other Linux. I'm a little worried about the Windows server...
0
Free Tool: Path Explorer

An intuitive utility to help find the CSS path to UI elements on a webpage. These paths are used frequently in a variety of front-end development and QA automation tasks.

One of a set of tools we're offering as a way of saying thank you for being a part of the community.

 
Sjef BosmanGroupware ConsultantAuthor Commented:
Thanks! I didn't think of it...
0
 
Sjef BosmanGroupware ConsultantAuthor Commented:
It was caused by an agent that was still active... The help offered was helpful in getting closer to the solution.
0
 
doninjaCommented:
ah good old local agents no doubt :)
Least you solved it.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.