Hi, Joe,
I have exactly the same scenario. Did you get any valuable response you
could share with me? I haven't seen any on the list.
In fact, my case is slightly more complicated; I have "N" computers, all
having their local databases, and have an additional computer, which I
call the "central" one, having a "central" copy of the database. I'd like
to sync all the N+1 databases continuously, so they are identical.
A---C---B
|
D
That is, if I change anything on any PC's DB (e.g. "A"), it replicates
itself to the central DB ("C"), and then migrates to "B" and "D". This
means that the A<->C connection is such that "A" is a master and "C" is
a slave, and the C<->B is such that C is a master and B is a slave. On
the other hand, if I change something on another local DB than "A",
e.g. "B" or "C" itself, I'd like this to migrate to "A", i.e. this case
the A<->C connection is such that "A" is the slave.
Altogether, I'd need a continuous master-master replication between all
DBs and "C". Similar to a RAID-1 array, just in the world of databases,
and over TCP. Maybe there is a problem with my concept, and this solution
of pushing for reliability will eventually cause chaos.
The Mysql manual does not mention master-master replication:
"Starting in Version 3.23.15, MySQL supports one-way replication
internally. One server acts as the master, while the other acts as the
slave."
Cheers,
Gaspar
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
