ServerA and ServerB are replicating Mail*.nsf with each other initiated by ServerA. ServerB is the “home mail server” of a few databases so emails are send to ServerB and then replicated back to ServerA by scheduled replication.
Problem is: Some databases (not all) does not replicate at all even if:
both replica ID are identical
No cut-off date is set in either replicas
both replicas are active
replication is working for other mail db between both svrs
ACL are identical on both sides (with both server Manager)
No Read or Author field are used on those dbs
replication history has been deleted (on both sides)
No formulas are used in either replicas
Priority of each replicas match the connection document
The replicas was all made like this:
Stop the Source Domino server
Copy mail database on a media
restart the source Domino server
Stop the Destination Server
Copy back the mail database on the destination server
Start the Destination Domino server
The only way I found to correct this problem was by created a brand new replica with the Lotus Notes client from the Source to the Destination Domino server and replacing the current replicas on it !
Problem is I only have a 256 Kb WAN link between the two physical locations which are seperated by 75 miles and some mail databases are over 300 Mb so it is almost suicide to replicate on the WAN. It is simpler and faster to made physical copy on a media and drove back to copy them on the destination server even with the distance factor.
Does anyone ever experienced something like this ?
I’m really open to any comments that can help me understand what I’m facing …
Subject: Replication issues - Is anyone experienced this ???
Rather than do a direct copy of the source database have you tried creating a local replica, copying this replica to your media and then on to to your destination server? I have used this method on remote users laptops in the past.
Subject: RE: Replication issues - Is anyone experienced this ???
Good idea, though I still have to jump in my car … I’m most of all searching for any kind of “unofficial” technote or something about that kind of behavior ?
As for the other two comments, “mail*.nsf” is not the real syntax in the connection docs. It was a statement to explain that others mail dbs were replicating fine.
And explicit replication did not resolve this issue unfortunately.
So I guess I will have to live with this strange situation without knowing where it comes from.
Subject: RE: Replication issues - Is anyone experienced this ???
Old technote 156522
Duplicates of Databases Created at the Operating System Level Do Not Replicate
Problem:
You create a duplicate of a replica database at the operating system level and the database does not replicate with the original database.
Solution:
This issue has been reported to Lotus Quality Engineering; however, it was determined not to be a software problem.
Replicas should be created using Notes by selecting File, Replication, New Replica because the replication setting “Only Replicate Incoming Documents Saved or Modified After” is cleared when a new replica is created. If a replica must be created using the operating system, you will need to manually clear the “Only Replicate Incoming…” setting, as well as the Replication History.
You can clear the replication history, the cut-off date but i would suggest going in the space saver section, instead of the 90 days, just go down one day like 89 days,
close the db
replicate the db with the server
put the 90 days back
reopen the db
We had similar problems and shacking the db with the 89 days parameters did the job.
Subject: Replication issues - Is anyone experienced this ???
When I’ve run into similar problems, I’ve found that explicitly replicating (with notes client or admin client) can break the spell and get things back to normal.