* Master-Master ("dual master") but write to only one of them. (Writing to both can lead
to duplicate keys, etc., unless you are very careful in your code.)
* Have the two Masters geographically separate. (Think tornados, floods, earthquakes,
* Have Slave(s) hanging of each master -- (1) for read scaling, and (2) to avoid a major
outage when one Master goes down and you need to take the other one down to clone it.
Another thing to consider:
Backing up via a "LVM snapshot" requires only a minute or so of downtime, regardless of
Percona's XtraBackup is also very good.
I also agree that MyISAM in not best. But, caution, InnoDB's disk footprint is 2x=3x
bigger than MyISAM's.
You can Load Balance reads (among slaves and, optionally, masters); you cannot do writes.
Any number of Apache servers can talk to MySQL. But watch out -- MaxClients should not be
so large that it swamps max_connections.
DNS is the simple way to load balance Apache.
There are low-impact software solutions.
There are hardware solutions. (This is what I am used to at work; it is severe overkill
for most users.)
Bottom line: There is no "best" or "perfect" solution. First decide what 'keeps you up
> -----Original Message-----
> From: Joey L [mailto:mjh2000@stripped]
> Sent: Monday, June 11, 2012 7:26 AM
> To: mysql@stripped
> Subject: i need advice on redundancy of mysql server.
> I am running a site with about 50gig myisam databases which are the
> backend to different websites.
> I can not afford any downtime and the data is realtime.
> What is the best method for this setup? master-master or master-slave?
> What are the best utilities to create and maintain this setup? as far
> as load balancing between the two physical servers that i am running.
> I am currently working with percona utilities - is there something
> better ?
> what would you use to load balance mysql ? what would you use to load
> balance apache.
> MySQL General Mailing List
> For list archives: http://lists.mysql.com/mysql
> To unsubscribe: http://lists.mysql.com/mysql