Another approach you may want to consider for data redundancy that does not rely on MySQL's finicky replication stuff is DRBD. Think of it as RAID-1 across Ethernet. I have used it in production on some VERY busy (> 1200 qps) MySQL servers for a couple years with no problems. Another nice side effect is a relatively simple means of doing a total point in time "cold" backup of all you DB's without regard to the db engine(s) your using and minimal down time. If you can afford ~ 1 minute/day of downtime... stop MySQL, break DRBD replication, restart mysql, mount data on the rep. slave, backup data files, unmount, restart replication. DRBD tracks the deltas so it will catch up quickly, and that entire process can be automated.
Anyways, if you're interested, check our http://drbd.org. Please make sure you fully understand what it's doing before using it in production though. A lack of understanding can lead to nasty things like replicating the wrong way. Note, that this can be used as a very simple means of providing warm standby * servers as well. Coupled with something like mon, you can provide for automatic failover as well. Josh McAllister -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Noah Miller Sent: Monday, May 08, 2006 10:17 AM To: Asterisk Users Mailing List - Non-Commercial Discussion Subject: Re: [Asterisk-Users] MySQL replication for voicemail Hi Gary - > I have voicemessage ODBC storage working and MySQL replicating, > but I didn't setup the replication after-the-fact, therefore didn't need the > 'LOAD DATA FROM MASTER'. You may want to try a different method > (more manual) of synching your machines. Yes, I've been reading about some errors with LOAD DATA FROM MASTER that might not get fixed until after 5.1 is released. Yikes! I'll take your advice and move a mysqldump of the info over to the slaves, and manually set the replication points. > Does your voicemessages table contain specially large messages? > The errors you get don't suggest this, but the only change I had to make > was to increase the maximum packet size -- it was 1M by default and I > changed it to 16M. Aha. I didn't even know there was such a setting. I'm sure there will come a time when someone leaves a message larger than 1M. Thanks! Noah > On 5/8/06, Noah Miller <[EMAIL PROTECTED]> wrote: > > > > Does anybody have any ideas on what's causing this error? Why would > > MySQL not have enough memory? What does it mean, "points outside data > > file"? Is anybody else doing this successfully, or am I a lone freak? > > > _______________________________________________ > --Bandwidth and Colocation provided by Easynews.com -- > > Asterisk-Users mailing list > To UNSUBSCRIBE or update options visit: > http://lists.digium.com/mailman/listinfo/asterisk-users > _______________________________________________ --Bandwidth and Colocation provided by Easynews.com -- Asterisk-Users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users _______________________________________________ --Bandwidth and Colocation provided by Easynews.com -- Asterisk-Users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
