Couchdb Replication Sync #4281
-
Hi everyone, Thanks! |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments
-
You could run a pair of replication jobs. A one-shot replication from the source to the new target. Then, make the target the default (production) db. Then perform another one-shot replication from source to target to bring over any document which may have been written there since the start of the previous one, so you don't leave any documents behind. The one-shot ( One subtle moment to keep in mind is that one-shot replication replicate from a snapshot of the database from when they start. So it might not see any documents written since then. |
Beta Was this translation helpful? Give feedback.
-
Great idea, @nickva. As the database is a bit large (around 300GB) and the 1st one-shot replication takes a lot of time, I'll manually move it via SCP, which is faster, and then run a second one-shot replication to push any new document, as you suggested. I think that should work. |
Beta Was this translation helpful? Give feedback.
You could run a pair of replication jobs. A one-shot replication from the source to the new target. Then, make the target the default (production) db. Then perform another one-shot replication from source to target to bring over any document which may have been written there since the start of the previous one, so you don't leave any documents behind. The one-shot (
continuous = false
) replication will just finish when there are no more document left to replicate.One subtle moment to keep in mind is that one-shot replication replicate from a snapshot of the database from when they start. So it might not see any documents written since then.