Auto sync (replication) mysql or PostgreSQL master-master avoiding conflicts

Question

I have two server one in cloud host and the other local in my office

I want a tool if my office get down of the internet or any reason, when its get up it will sync auto

Is there a lazy way to solve the conflicts?

Any suggestion?

Answer 1

i found the solution by using this tool, RubeyRep its providing asynchronous replication and syncing option, in my case i can have master - master with out worrying about if the internet is got down delay lets say 1 minute or 2 minutes, its fine in my case,

Scan Features

rubyrep can scan corresponding tables of left and right database3 for diverging data.

• Different output modes: from count of differences over row diffs to full row dumps.
• enter code hereLow bandwidth mode available: reduced number of round-trips; only actual differences go through the network.
• Shows progress bar with estimated remaining amount of work.

Sync Features

• All scan features also apply to syncs

• Automatically orders table syncs to avoid foreign key conflicts.

• Sync policy specifyable: ignore deletes in left database, ignore created records in right database, etc.

• Prebuild conflict resolution methods available: left db wins, right db wins

• Custom conflict resolution methods specifiable via ruby code snippets

• Merge decisions can optionally be logged in the rubyrep event log table. Replication Features

• Automatically sets up necessary triggers, log tables, etc.

• Automatically discovers newly added tables and synchronizes the table content

• Automatically reconfigures sequences to avoid duplicate key conflicts

• Tracks changes to primary key columns

• Can implement both master-slave and master-master replication

• Prebuild conflict resolution methods availble: left / right wins; earlier / later change wins

• Custom conflict resolution specifiable via ruby code snippets

• Replication decisions can optionally be logged in the rubyrep event log table]2

Answer 2

It's called replication and you can set up a master in your office and your cloud machine can be slave: see http://dev.mysql.com/doc/refman/5.0/en/replication.html

Data security - because data is replicated to the slave, and the slave can pause the replication process, it is possible to run backup services on the slave without corrupting the corresponding master data.