You'll want an alert to page you when the replication slaves stop for an error; look for Matthew Montgomery's script; we added paging and an 'autofix' step to correct a limited number of duplicate key errors (and email when it does so); I page for other errors. We've had M-M 5.0 replication and M-S 5.1 replication configs running okay for a while....
-----Original Message----- From: Tompkins Neil [mailto:[EMAIL PROTECTED] Sent: Monday, November 17, 2008 2:16 AM To: [MySQL] Subject: Using Replication in mySQL version 5 Hi We are looking to upgrade our version of mySQL to the latest version of mySQL 5. One of the main features we are going to think about using is replication for our website data. Basically we have 2 websites located in the UK and US which share similar information, and we are going to be using replication as a way of keeping the data up to date and in sync. Based on your experiences, is there anything we should be aware of before investigating this route and putting it into practice ? Thanks, Neil -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
