Levi Smith wrote: > > The > question is, once I start getting a database out there, what's the best > method for keeping them synchronized?
http://dev.mysql.com/doc/mysql/en/replication-faq.html Q: What issues should I be aware of when setting up two-way replication? A: MySQL replication currently does not support any locking protocol between master and slave to guarantee the atomicity of a distributed (cross-server) update. In other words, it is possible for client A to make an update to co-master 1, and in the meantime, before it propagates to co-master 2, client B could make an update to co-master 2 that makes the update of client A work differently than it did on co-master 1. Thus, when the update of client A makes it to co-master 2, it produces tables that are different than what you have on co-master 1, even after all the updates from co-master 2 have also propagated. This means that you should not co-chain two servers in a two-way replication relationship unless you are sure that your updates can safely happen in any order, or unless you take care of mis-ordered updates somehow in the client code. You will probably want to start your reading here: http://dev.mysql.com/doc/mysql/en/replication.html It looks like MySQL natively does replication without having to resort to third party tools. -john -- [email protected] http://www.kernel-panic.org/cgi-bin/mailman/listinfo/kplug-list
