Hi All,

I have a problem creeping up with a 3 server replicated setup.
I think I might be missing something..

The setup is a s follows:
3 servers, all with outgoing replication remote folders as well as incoming replication folders.

I built a replication service with a timer that saves updates on each of the 3 servers at 1 minute intervals.
After updates are saved, the incoming folders are scanned and incoming updates are loaded.

All outgoing files are deleted after successful upload, and loaded update files are deleted after loading updates. All seems to work well except for the issue below..

The problem...
When server A saves and uploads it's update files to Servers B and C, servers B and C receive the update files, loads them, and immediately saves updates again to their respective outgoing folders. Server B uploads back to A and C and  C uploads back to A and B.

Is there away to prevent this from happening?
It seems that the ElevateDB server saves updates whether records were altered via user input as well as when records are altered via loading updates from a file.

Is there a way to prevent saving updates for records altered via loading incoming update files?

My current workaround is to set server A as master and B and C as slaves, so B and C don't save updates at all. This fixes the problem, but I really need a multi primary setup working.

Should I un-publish tables before loading updates? What happens then if I have a multi primary system and a user edits a record during a LOAD UPDATES procedure? Or just before, after un publishing the tables?

Should I use transactions? Not really sure..

Replication seems to work 100% except for all the unnecessary updates files being sent back and forth..

Thanks,
Tony