Database replica deleting records

HCL Domino Domino Forum
1

Hello, I have had the same issue a few times now. I have 2 servers in a cluster Server A and Server B with a replica DB on each. The Server A is the Prod server and server B the backup. Users are complaining they don’t see records that other users have submitted to the DB on server A. I look on the replica copy on server B and see the missing records. Apparently when they are replicating Server B DB is deleting the Server A records. To resolve I have cleared all replica history then replicated the DB’s. The records appear in server A then are deleted once more. Finally I deleted the history again and replicated. I then deleted the Server B copy and made a new replica copy from Server A to Server B. I went a few weeks and then the issue reappeared. So far this DB is the only one with this issue as I can tell. Has anyone else experienced this?

2

Subject: some stuff to check

  1. are there any Readers fields on the docs? If so, make sure your servers are included as members of the Readers field(s). Best way to do this is add a Role to the field(s) and add your servers to the role.

  2. In the replication settings for the dbs make sure that “remove docs not modified in x days” is NOT enabled.

  3. Is there a replication formula in the replication settings for the dbs? This will typically cause such an issue. Replication formulas can be tricky and misleading.

  4. Are there any agents removing the documents?

  5. Make sure all of your servers have at least Editor with Delete access to each other. One server should be Manager with all roles to act as the master server.

  6. Check the User Activity log on each replica when the docs go missing to see where the problem occurs and if possibly you can see “who” or what might be deleting them.

3

Subject: DB record deletions

Paul Thanks for responding!

  1. are there any Readers fields on the docs? If so, make sure your servers are included as members of the Readers field(s). Best way to do this is add a Role to the field(s) and add your servers to the role.

I do not think there are any readers fields. I am reluctant to blame the design as it has not changed in some time.

  1. In the replication settings for the dbs make sure that “remove docs not modified in x days” is NOT enabled.

Remove docs is not checked. Also these documents that are being deleted are recent documents.

  1. Is there a replication formula in the replication settings for the dbs? This will typically cause such an issue. Replication formulas can be tricky and misleading.

They can be I agree. There are no replication formulas in the DB.

  1. Are there any agents removing the documents?

There are no agents deleting documents.

  1. Make sure all of your servers have at least Editor with Delete access to each other. One server should be Manager with all roles to act as the master server.

Localdomainservers have manager access with delete

  1. Check the User Activity log on each replica when the docs go missing to see where the problem occurs and if possibly you can see “who” or what might be deleting them.

I do see the Server B is the one deleting documents in the Server A copy. I probably should have mentioned I saw that in the activity log.

Also I did run fixup on both DB’s along with updall and refreshed all the views after deleting the history and replicating. I also verified neither DB is being refreshed from a template as I was thinking maybe template corruption may have corrupted one of the DB’s.

Maybe I should put a template out on the server to assure the DB is refreshed each night.

Thanks

4

Subject: check activity log on server B

if you see server B deleting docs from server A (server B shows in user activity log on server A replica) then check the activity log on server B and it should record who/what is deleting the docs on server B.

5

Subject: activity log

Hi Paul,

The thing is documents are getting deleted on server A but not server B even though they are exact replica copies of each other. If I delete the rep history then replicate the documents come back to Serv A copy for a little while, but then get deleted out of seerver A but not server B. I think this is crazy. The only thing I can think is coruption of the replication history or something like that on Server B. In the recent past I had deleted the Server B copy and made a new replica copy from Server A. after a few weeks it reoccured. I ended up doing the same thing this time but still not sure of the cause.

Thanks for your time in giving me some ideas I’ll keep poking around.