Hi, you can configure bin-log on one, and send logs the second server for sync. you will have an almost real-time synchronization env.
problem is that you MUST use inodb for ttansactions, and apply exactly the changes to the standby server. no replication, no cluster. This is a simple but needed to be maintained solution. Mathias Selon Susan Ator <[EMAIL PROTECTED]>: > This is our situation: We have two servers running RHES3 with samba > connections to a server running RHES4. (No, it's not dns. Believe me > when I say I don't ever want to go through *that* pain again) Our ES4 > server contains shared data that is not controlled through cvs. Our two > ES3 servers contain our website which is controlled through cvs. Both > our ES3 servers have mysql. The mysql dbs have our username/password > (and other) information. > > We are in the process of setting up ip failover using a dns round-robin. > My concern about keeping the mysql dbs on the ES3 servers is the > possibility of changing the db on one and also changing the db on the > other; I don't know how to keep the changes synced. > > I was considering putting the mysql db on the ES4 server and both the > ES3 servers would connect to the mysql db there. > > My partner in crime is concerned about this since it would be a single > point of failure. > > This is my question: What would be the best configuration for > maintaining database integrity? I don't mean just between what I > outlined, but in general? Clusters seems to be overly complicated (from > what I can understand of it). I just need some direction at this point. > > Thanks, > > Susan > > -- > MySQL General Mailing List > For list archives: http://lists.mysql.com/mysql > To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED] > > -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
