Syncing Issue with Replicated Database

[Guest]

Here's the situation:

The replica that is on our network that all of the user's sync to has some
missing data. On one of the local user's backend's has the data that is
missing. I had that user sync out to the network replica and it overwrote the
user's data so it matches the network replica of having nothing. How come it
didn't write the data that was missing out to the network replica? Does it
only notice recent changes?

 

[David W. Fenton]

Here's the situation:

The replica that is on our network that all of the user's sync to
has some missing data. On one of the local user's backend's has
the data that is missing. I had that user sync out to the network
replica and it overwrote the user's data so it matches the network
replica of having nothing. How come it didn't write the data that
was missing out to the network replica? Does it only notice recent
changes?

If the data is missing from the 1st replica because it was deleted,
then a synch with the 2nd replica will delete the data from the
replica where it still exists.

How else would you want it to work?

The way replication works is that any two replicas in a replica set
are just one synch away from having identical data. However, which
changes get propagated in which order depends on the kind of changes
involved, and is highly dependent on the relational integrity rules
in the database.

But if somebody deletes records in one replica, they are going to be
deleted in all the replicas -- by definition.