Reputation: 2169
This question may seem like a strange one, but here what I noticed with our admin: we have an application which we want replicate scheduled it. All the docs. from this app, after the replication, are gone/deleted. Our admin noticed from the log file that the server where the replication takes place didn't have enough rights.
Creating a manual replication works just fine ( pull - push ), without any problems.
What could be the reasons?
BTW: we also replicate other applications, using scheduled replication, but it is working OK, without issues. So, what does this application have which "block" the scheduled replication and which cause the document to be deleted?
Upvotes: 0
Views: 553
Reputation: 12060
You answered your question already by yourself: The server that replicates does not have enough rights: Most probably the server is not member of any of the readers- fields in the documents. When replicating the server "sees" that it should not "see" any of the documents, and removes them from the database (NOT DELETE, because deletion would create deletion stubs).
If you manually replicate a database, then replication is done with the rights of the person, who starts it: This person seems to have the right permissions...
Upvotes: 2