Hello @ll,
I need to build a simple HA (High Availability) scheme to be used in a database environment. What I need to have is a database server (I'd like to run MySQL, that's the reason I'm posting here) with fail-over. So I'll have two real servers (ServerA and ServerB) running Linux and some typical HA utils (like mon, heartbeat, fake, etc). ServerA will be the main server and will serve all db traffic if no problem exists. If ServerA goes down, then ServerB would "substitute" it and would begin to serve. If ServerA is fixed and is turned up again, then ServerB will come back to a iddle state, and ServerA will continue to serve the database traffic. This is a typical fail-over scenario, where ServerB acts as the "backup server". The problem is that I need to have both databases (ServerA and ServerB) fully synchronized, i.e, replicated. I know MySQL supports database replication, but in a read-only mode (writing operations depends on the "master" server, so it would be a SPF [single point of failure] or a bottle-neck). But have you got any solution/tip for having replication with write support? If ServerA goes down, I need ServerB to be fully functional (including "write support" at database). I had thought in rsync'ing the database's files, but this is rude "solution" and will not avoid having inconsistences between both databases. Thanks in advance for your patience (and your ideas :-)). Salu2, --Roman -- PGP Fingerprint: 09BB EFCD 21ED 4E79 25FB 29E1 E47F 8A7D EAD5 6742 [Key ID: 0xEAD56742. Available at KeyServ] --------------------------------------------------------------------- Before posting, please check: http://www.mysql.com/manual.php (the manual) http://lists.mysql.com/ (the list archive) To request this thread, e-mail <[EMAIL PROTECTED]> To unsubscribe, e-mail <[EMAIL PROTECTED]> Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
