We have a cluster envt. Mail changed and deleted in one database is also immediatly changed/deleted in he replica.But, it appears that the size and nb of documents in both dbs are often very different.
For example, a user has 27 docs on one db, and 706 on the other. if i delete a doc on the db with the 27 docs, it’s immediatly removed on the other. But, what about the 706-27 docs that stays in the secnd db ? How to remove them ?
How could i tell Domino to re-synchronize (one or all) the dbs so they are exactly equivalent ?
Thanks,
Yan
Subject: Force delete documents
You say “if i delete a doc on the db with the 27 docs, it’s immediatly removed on the other. But, what about the 706-27 docs that stays in the secnd db ?”
On one hand you say it is immediatly removed on the other, then you say it stays. That’s confusing. Maybe you can explain it in more detail, with examples?
Thanks
Subject: RE: Force delete documents
Hi Matt,Here some (better ?) explanation:
On server1, the db contains 63 documents. Server1 is the user’s mail server.
On Server2, the replica of the db contains 706 documents.
If i change a doc in db on Server1, it’s changed on the db on Server2. If a doc is deleted, same thing.
So, the cluster works well.
But, why does all the documents previously deleted (i don’t know when) on Server1 have not been also deleted on Server2 ?
Hope its clearer.
Subject: RE: Force delete documents
There seems to be a replication issue. I found this on SearchDomino that may help you identify other issues as well. In the meantime, is it possible for the database on server1 to be recreated?
http://searchdomino.techtarget.com/tip/0,289483,sid4_gci1192350,00.html?track=lc_cluster
Subject: RE: Force delete documents
Matt,I’ll look further the code on techtarget.
Concerning the recreation of the dbs, the one on Server1 is the most acurate. So, i would rather delete and recreate the one on Server2 to have a brand fresh new replica.
The curious thing is that i discovered this situation wednesday for another user( say U1): the rep command didn’t sync the dbs and i had also some documents found in one dbs but deleted in the other one. This morning for U1, i launched a rep betwenn the dbs and the deleted documents on one replica were added to the other. I then deleted the obsolete docs and they were removed on the replica…
Strange…
I think it has to do with the rep process of the cluster. The help admin db tell about changes held in memory if the rep process cannot work. Do you have some info about this ?