[prev in list] [next in list] [prev in thread] [next in thread] 

List:       mysql
Subject:    RE: recommended high availability setups
From:       Martin Gainty <mgainty () hotmail ! com>
Date:       2008-08-28 23:37:45
Message-ID: BLU142-W11CE875F83D584EC0750AEAE600 () phx ! gbl
[Download RAW message or body]


agador-

did you look at replication implementations using master/slave configuration?
http://dev.mysql.com/doc/refman/5.0/en/replication-solutions-diffengines.html

HTH/
Martin 
______________________________________________ 
Disclaimer and confidentiality note 
Everything in this e-mail and any attachments relates to the official business of \
Sender. This transmission is of a confidential nature and Sender does not endorse \
distribution to any party other than intended recipient. Sender does not necessarily \
endorse content contained within this transmission. 


> Date: Thu, 28 Aug 2008 13:38:37 -0700
> From: sparctacus@gmail.com
> To: mysql@lists.mysql.com
> Subject: recommended high availability setups
> 
> What's the recommended method for high-availability setups?
> 
> I've currently got a master-master replication setup that I'm testing
> but it doesn't quite seem as complete a solution as I had pictured.
> 
> When a failed server comes back online you still have to manually add
> it based off of the line numbers/binlog correct?  And adding a new DB
> requires reloading the MySQL server?
> 
> I've been looking around at other technologies as well like linux-ha.
> What are other people using for systems that have to be up 100% of the
> time but aren't complete nightmares to manage?
> 
> TIA!
> 
> -Bryan
> 
> -- 
> MySQL General Mailing List
> For list archives: http://lists.mysql.com/mysql
> To unsubscribe:    http://lists.mysql.com/mysql?unsub=mgainty@hotmail.com
> 

_________________________________________________________________
Get ideas on sharing photos from people like you.  Find new ways to share.
http://www.windowslive.com/explore/photogallery/posts?ocid=TXT_TAGLM_WL_Photo_Gallery_082008




[prev in list] [next in list] [prev in thread] [next in thread]