Multiple entry points for data? That seems to imply a cluster rather than database replication.
mysqldump, raw data replication, replication are all premised on there being an authoritative server. You can't just use those if the nodes are equal - what will happen if 2 sites update the same data? You could end up with a database inconsistency. If both sites are already connected via VPN tunnel though, couldn't you just point both applications to the same database using routing/firewall rules? Have 1 site be authoritative, have the other site be a read-only copy that activates in case the VPN goes down. On Fri, Feb 19, 2010 at 11:17 PM, jan gestre <[email protected]> wrote: > Hi Guys, > What would be the best way to achieve database replication wherein the copy > of db1 and db2 on MySQL server on network1 should be the same on MySQL > server on network2, every time changes happen whether it happens on site1 or > site2, db1 and db2 on both sites should still be the same, raw data > replication? or MySQL Master/Slave replication? using mysqldump run through > a script/cronjob? Both sites are connected via VPN tunnel. > Thanks in advance. > -- > http://jangestre.blogpsot.com > > _________________________________________________ > Philippine Linux Users' Group (PLUG) Mailing List > http://lists.linux.org.ph/mailman/listinfo/plug > Searchable Archives: http://archives.free.net.ph > -- This email is: [ ] actionable [ ] fyi [ ] social Response needed: [ ] yes [ ] up to you [ ] no Time-sensitive: [ ] immediate [ ] soon [ ] none _________________________________________________ Philippine Linux Users' Group (PLUG) Mailing List http://lists.linux.org.ph/mailman/listinfo/plug Searchable Archives: http://archives.free.net.ph
