Lotus notes local replica not updating online dating mexican women
There are variations on the scenario, server C replicating with B, B initiating the replication with A.I have an application that is build around this expectation, and it has worked well most of the time.
Upon further investigation, it was determined that the document on the secondary server had a higher sequence number which implies that it was updated more recently than the document on the primary server.
Resolving the problem 1.) A short term solution would be to modify the document on the primary server so that its sequence number is higher than document on the secondary server.