I am trying to configure mysql for redundancy using replication and the built-in mysql master/slave configuration. What I don't understand, even after much reading, is how to recover from a failure. If host B is slave to host A, and A goes down, B could then be manually or automatically configured to be master itself, and thus take over A's role completely. However, if B was not completely caught up from A before the failure took place, then once A was back up the two would be out of sync, and A could contain data B did not, and B would undoubtedly contain data A did not. How do you avoid this situation or re-sync the two after a failure like this?
I'm finding it difficult to locate a concise and cohesive method to create a redundant database system using mysql. Any other resources or references would be heartily appreciated. Joe --------------------------------------------------------------------- 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
