Corrupting Data from synching.

[Dave31]

Hi,

I have two backends on two different servers overseas. I have a button which synchings up the data. The only problem now is, it seems to corrupt the backends (without actually corrupting any of the data) So, now when i go into the backend (to synch up) it produces 73 (ish) messages about corruption. I have tried compacting and repairing but the next time i open it, it still says its corrupted. I have looked at the data as well, and i cant seem to see any issues with it.
Does anybody have any ideas why this is? or any ideas how to prevent this issuse or even fix it?

Many Thanks

 

[dfenton]

I have two backends on two different servers overseas.

Are they on the same network, or is there a WAN or Internet connection between them?

I have a button which synchings up the data.

What method are you using to do the synch?

The only problem now is, it seems to corrupt the backends (without actually corrupting any of the data) So, now when i go into the backend (to synch up) it produces 73 (ish) messages about corruption.

What are the specific messages? Can't diagnose a solution without that!

I have tried compacting and repairing but the next time i open it, it still says its corrupted. I have looked at the data as well, and i cant seem to see any issues with it.

My guess is that you've been using DIRECT replication across a WAN and because of the unreliability of these connections, you produced problems in your replica set.

If that's the case, the first thing you have to do is STOP doing DIRECT replication and set up either INDIRECT or INTERNET replication (I only do INDIRECT because I don't like the dependency on IIS that the alternative introduces).

Getting rid of the errors is a harder problem. The actually solution depends entirely on which kind of errors they actually are.

--
David W. Fenton
David Fenton Associates
http://dfenton.com/DFA/