I reckon I'll just stick to a single MySQL instance given the complexities of syncing. I can always run a nightly dump and transfer to the backup server so I can fail over manually.
Bart... -----Original Message----- From: Nigel Frankcom [mailto:[EMAIL PROTECTED] Sent: 10 December 2006 21:58 To: SpamAssassin Subject: Re: Synchronising Bayes mysql data between two server On Sun, 10 Dec 2006 16:32:13 -0500, "Michael Scheidell" <[EMAIL PROTECTED]> wrote: > >> -----Original Message----- >> From: Nigel Frankcom [mailto:[EMAIL PROTECTED] >> Sent: Sunday, December 10, 2006 4:14 PM >> To: SpamAssassin >> Subject: Re: Synchronising Bayes mysql data between two server >> >> >> On Sun, 10 Dec 2006 15:57:40 -0500, "Michael Scheidell" >> <[EMAIL PROTECTED]> wrote: >> IMO, running a single, load balanced backend SQL divorced from your >> SA servers is a better and easier solution to implement. If mail and >> SA/SQL are all on the same lan, Gbit ether will keep it fast. >> > >Maybe share (at least) with the list what you use for, or mean by 'load >balanced'. > >Do the load balanced servers cross update themselves, or are they just >separate? >(which, I suppose, if the MX servers are same weight, and the sql >servers are balanced equally, it wouldn't really be necessary to share >data between them) SQL Load balancing is something quite apart from SA and is well documented on dev.mysql.com - that aside, the whole point of load balancing is that all/any server has the same data as any other in the cluster. The sa end of it doesn't care. It uses a single MySQL point within the lan and draws it's data from there, since all data is the same whichever MySQL server serves, it's essentially a single point. OK - so that's the ideal. In reality I run a single, dedicated SQL for SA. The downside is it gives me single point failure. Adding balancing should alleviate that, and, when I get a week or so to figure out wtf the MySQL docs actually mean I may even run it in. The point still stands tho - a single mysql - balanced or not, allows for multiple SA front ends to connect. In my setup that can happen if a single SA drops or if any of them are busy. I'm certainly no guru so to me it is mostly common sense based around way too many years developing databases and their redundancy. SA & my MTA make it easy. I accept I haven't explained the load balancing much (if at all) - but the mysql docs do it so much better - and a lot depends on what versions of mysql you run. A search back through the mail archives will find my original enquires and the suggested routes (1 - 2 years ago). Please hunt - it saves me doing it and a lot of typing to boot :-D KR Nigel
