Joan,
thanks a lot for your answer. So what we tried to do is not supported.
That's definitely good to know ;-))
The reason we didn't consider replication in the first place is that we
wanted to keep couch completely hidden behind a firewall. No one from
any other machine should ever be able to touch the database through any
other means than our application which runs locally on the couch server
and serves a a web application.
So it looks like what we need is to set up our Windows database(s) to
initiate pull replication, because the db on the windows machine should
just be a copy of the production db. it is mostly used for testing and
to reproduce errors of the production server.
Is it possible to do a Pull replication that only replicates "down"
meaning no documents from the db on the development machine ever move up
to the production server? Do we need to implement a Filter for this?
Thanks,
Joachim
Am 07.09.16 um 13:50 schrieb Joan Touzet:
Hi Joachim,
Is that a known bug or limitation? Is our way of backing up wrong for
cross-system restore? What would be the appropriate way to
backup/restore back and forth between Linux and Windows?
You should be using replication between your CouchDBs to transfer
the database from one system to the other. No guarantees are made
about the portability of .couch files between operating systems.
Replication is well documented:
http://docs.couchdb.org/en/1.6.1/replication/intro.html
I could hazard some guesses about why you have partial compatibility
in the setup you're using, but I don't want to get your hopes up,
as we're not going to support this scenario.
-Joan
