Database Administrators Stack Exchange is a question and answer site for database professionals who wish to improve their database skills and learn from others in the community. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

EDIT: I'm encountering precisely the same issue.

  • Assume that I have two RavenDB instances.
  • Instance 1 contains one document: users/1.
  • Instance 2 contains three documents: users/2, users/3, and users/4.


  • Assume that I configure and enable replication for both instances.
    • That is, Instance 1 will replicate to Instance 2 and Instance 2 will replicate to Instance 1.
  • After replication, both instances will have all four documents.
    • But both instances will agree that users/1 's Raven-Replication-Source is Instance 1, and users/2, users/3, and users/4 will have their Raven-Replication-Source set to Instance 2.


  • Assume that Instance 1 suffers a catastrophic failure and I need to reinstall RavenDB.


  • My testing shows that in this scenario: users/2, users/3, and users/4 will again be replicated to Instance 1.
  • However, users/1 will not be replicated to Instance 1 because its Raven-Replication-Source is Instance 1.

My Question:

  • How can I force Instance 2 to replicate users/1 back to Instance 1, even though users/1 was originally created on Instance 1 and its Raven-Replication-Source is Instance 1?
share|improve this question

migrated from May 8 '13 at 22:34

This question came from our site for professional and enthusiast programmers.

up vote 1 down vote accepted

Configure replication as 'Changed and Replicated'.

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.