Replication of address book out of sync

The replication of address book between few server is functioning well. All the records are tally and in sync between these few servers.

However recently found that this address book record are out of sync among these few servers. Tried manual push down and replicate but it does not update correctly.

Any idea how i re-sync back the address book?

Subject: Replication of address book out of sync

Firstly there is a warning: How long have these been out of Sync… if greater than a couple of weeks, taking a OS copy from the others server would be a good idea. This is because deletin stubs and old changes may come back and cause your domain a whole deal of pain.

If this has just happened and you can confirm this then there are things to check.

Permissions to the DB for Local Domain Servers etc. : should have Editor access (or higher).

Check the DB properties to make sure the “do not replicate this database” button has not been ticked.

Check Replication settings etc send and recieve documents blah blah.

See how this goes…

Subject: RE: Replication of address book out of sync

further to Nathan’s points, if you are certain the replicas are out of sync for # of days less than the purge interval you can clear replication history to force a full recalculation of docs to replicate. However, if the replicas are out of date for longer than the purge interval then you should take new replicas or else you may get back previously deleted docs.

Subject: RE: Replication of address book out of sync

Paul’s right. You should be careful

Are they out of sync because you have old documents in some replicas (Deleted ones)?

Can you identify the type of documents that don’t replicate? (Person, Group, Holiday,etc)

JYR

Subject: RE: Replication of address book out of sync

Hi Nathan,Discovered that the address book out of sync at least 2-3 weeks. Have checked the ACL, db properties, replication setting, everything seems fine.

Hi Paul,

Can you advise how do i check on the purge interval and where it was schedule for the purge? I have no idea on this, i am quite new on domino administration.

From the Replication setting, i only found this → This replica includes deletion stubs for all documents deleted since 12/01/2008 01:00:13AM

If i would to clear the replication history, should i clear on the main server address book? What will happen to those that are in sync? Do i need to clear the history of those out of sync?

Hi Jean,

You are right, there are still some old documents(deleted ones) still found in the address book. There are some latest update does not replicate over too.

I am not so sure the type, how can i verify? Any tools that i can compare the difference between the main server address book and other server replicated over address book? As this is a huge address book, thousands of entry inside there.

Subject: RE: Replication of address book out of sync

The safest way to deal with this is:

Take the server down…

Delete or remove the Names.nsf from the server (never to return)

Take an OS copy or restore from one of the other server and place this in the Servers data directory.

Start Domino Server.

This will bring your server up with the correct Domino Directory. Now check the permissions to the database. Make sure the server has the correct access… Manager access for Local Domain servers would be OK (make sure the server is in local Domain server).

Test it by making a little change then replicate it back to somewhere.

Once this has been done you should not have a issue at all.

The Replication history can be view from Database properties. You can clear this information from there as well (button on the right). I would say stay safe and save your job :slight_smile:

Good luck

Subject: RE: Replication of address book out of sync

About OS copy style

We had problems a few years ago due to this method. It was suppose to be related to an old version of Lotus Notes.

The technote is from 1997-12-15.
For what I can say, the problem is still there in 6.5.

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.

Subject: RE: Replication of address book out of sync

If the above is a worry then create a replica of the address book locally then use that on the server. This would then be correct???

Do not try and do this:::::

Relicate the database (names.nsf) to the server under another name. This si because the server may replicate the changes to itself and then all the old DB information would return to the new replica and then replicate around.

I as the other have cannot state that this should be approached carefully. OS copy is safest or a restore. If there was an issue with IS copy of databases then installing a domino server in a remote location with Replica files on a CD would not be an option.

I will say take Jean-Yves warning seriously and check replication after the change has been made.

Subject: RE: Replication of address book out of sync

Hi All,Thanks for all the advise.

I understand the safest way is to down the server, remove the names.nsf and restore back.

I tried not doing so as we have more than 10 overseas sites affected. I hope to find a solution so as not to have major impact on the server operation for the overseas sites.

I am currently liasing with vendor support and IBM technical personnel, hopefully there’re other way out

Subject: RE: Replication of address book out of sync

Hi,

you didn’t mention if you have identify what types of documents are in problems ie more Group documents in one NAB, less person documents in another, etc.

Just a quick one, create a view in your NAB (Select @all)

First column, sorted, categorize. Column value : Form

Second column: Total, hide details

It’s not scientific but you could at least know where is your problem. Then compare the numbers each categories in all of your NAB

Do your users have local replicas of your NAB?

Do you manage every servers in your environement. Maybe it is an old server that was brought back to like after the purge interval

A big problem encountered by many users:

http://www-10.lotus.com/ldd/nd6forum.nsf/55c38d716d632d9b8525689b005ba1c0/1acb01c8dc57378785257377002dfd5f?OpenDocument

Tool to find Old documents or deleted documents pushed back to server by replication

Link : http://www.openntf.org/Projects/codebin/codebin.nsf/CodeByDate/300F25985BCB5CA38625737900608E54

This db allows you to find the Added to file date of all person documents in your NAB.

The search is done against the Mail Users views.

In your search , you have to specify which mail servers (From your mail users view) to look at.

Find Old documents or deleted documents pushed back to server by replication

Deleted documents are reappearing after replication

http://www-1.ibm.com/support/docview.wss?rs=0&uid=swg21098733

It’s possible to find them by script with the AddedToThisFile API.

Q&As about replication purge intervals and cutoff dates

http://www-1.ibm.com/support/docview.wss?rs=0&uid=swg21110117

How to track down where replication changes originate

http://www-1.ibm.com/support/docview.wss?rs=0&uid=swg21225071

You can reuse this code to search other dbs, or other types of document sin the NAB (server documents, holiday documents, etc)

JYR