This problem has been solved many times. The absolute most bomb-proof MySQL failover solution involves a combination of DRBD and Linux HA (Heart Beat). The replication model has too many issues IMO.
On Sun, Nov 23, 2008 at 9:10 AM, Uwe Kastens <[EMAIL PROTECTED]> wrote: > Hi Krunal, >> * I am having 2 MySql servers. Lets say 192.168.1.5 >> <http://192.168.1.5> & 192.168.1.6 <http://192.168.1.6> >> * Opensips is at 192.168.1.4 <http://192.168.1.4>. >> * I would like to use 192.168.1.6 <http://192.168.1.6> mysql server >> for failover. >> * I mean to say if 192.168.1.5 <http://192.168.1.5> goes down then >> opensips should start to use 192.168.1.6 <http://192.168.1.6> >> mysql server. >> > > I am just on my way to implement the same. At the moment I am planing a > kind of Mysql Master - Master together with one VIP for > Mysql-opensips-communication. So for your example you will have to > mysql-servers. opensips is connection to lets say to 192.168.1.4 which > points on one of your mysql-servers. You will need active-active for > mysql since opensips will write some information in the database as well. > > > I am working with mysql-5 and heartbeat-2 in mode 1. Its nearly working. > > BR > > Kiste > > -- > > kiste lat: 54.322684, lon: 10.13586 > > _______________________________________________ > Users mailing list > [email protected] > http://lists.opensips.org/cgi-bin/mailman/listinfo/users > _______________________________________________ Users mailing list [email protected] http://lists.opensips.org/cgi-bin/mailman/listinfo/users
