We are trying to setup the following MySQL replication MSSQL Server - Push replication to Server 1 Server 1 - (Receives push replication from MSSQL and is Master MySQL for Server 2) Server 2 - (Slave to Server 1, Master for Server 3) Server 3 - (Slave to Server 2)
Okay to make a long story short we have a MSSQL server required by our accounting package. We use a push replication on the MSSQL server to replicate the data from MSSQL to a local MySQL database in a remote office (accounting office). The information in that database needs to be replicated over a relatively slow WAN link to a series of MySQL slaves. In order to save bandwidth we set-up a single MySQL server that will slave from the remote MySQL in our accounting office and redistribute the database to our other MySQL servers. The first MySQL server is in the remote accounting office. All updates and changes from the accounting department are made to that database server through a push replication from MSSQL. This part works fine. In another office we have a single MySQL server (Server 2) that is a slave to Server 1. We then have 4 MySQL servers which slave from Server 2. Since these are all identical read only slaves I'll refer to them collectively as Server 3 (they all experience the same behavior) The problem we are having is that Server 2 does not make the data it replicates from Server 1 available for replication to Server 3 Example We make data change to MSSQL MSSQL replicates the change to Server 1 Server 1 updates its master status to indicate new data Server 2 pulls the changes from Server 1 and updates its slave status to show its in sync with Server 1 Server 2 does NOT update its master status to indicate that anything has changed in its database Server 3's slave index still matches with server 2's master index so server 3 does not replicate the changes that server 2 received through replication. What seems to be strange is if we update server 2 directly with a change (make any update that does NOT come from replication) it will update its master status and Server 3 will replicate that change. It appears that MySQL does not treat replicated data as changed data when it comes to the master status and bin-log. We are using MySQL 4.0.4 as we require transaction support to do the push replication from MSSQL. Does anyone have an idea on how we can force server 2 to add the data it receives to its bin-log and update its master status so that it will be replicated down to server 3. Thanks in advance Kelvin Hockin --------------------------------------------------------------------- Before posting, please check: http://www.mysql.com/manual.php (the manual) http://lists.mysql.com/ (the list archive) To request this thread, e-mail <[EMAIL PROTECTED]> To unsubscribe, e-mail <[EMAIL PROTECTED]> Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
