tag:blogger.com,1999:blog-5412150273415696914.post4015598792984469154..comments2009-02-13T18:42:57.575-05:00Comments on Jay Janssen -- MySQL Guy: Where cluster needs to beJay Janssennoreply@blogger.comBlogger2125tag:blogger.com,1999:blog-5412150273415696914.post-22423365958063071892007-05-11T16:06:00.000-04:002007-05-11T16:06:00.000-04:00Whoops!, misspelled Oracle RAC as RAQ. I used to ...<I>Whoops!</I>, misspelled Oracle RAC as RAQ. I used to work at an ISP that used <A HREF="http://en.wikipedia.org/wiki/Cobalt_RaQ" REL="nofollow">Sun Cobalt RAQ</A> servers, so I always think of spelling it like that.<BR/><BR/><BR/>In reply to stewart's comment regarding replication channels: I was referring to the idea of actually setting up two masters and slaves between two clusters and replicating separate dbs or sets of tables down each channel. Not good for consistency, but if you knew it was safe, it would work.Jay Janssenhttps://www.blogger.com/profile/07146539825543443554noreply@blogger.comtag:blogger.com,1999:blog-5412150273415696914.post-27401371471751357242007-05-10T02:16:00.000-04:002007-05-10T02:16:00.000-04:00issuing START BACKUP in the management client will...issuing START BACKUP in the management client will create a consistent backup of the cluster.<BR/><BR/>the use of multiple replication channels is currently only for redundancy, not additional performance.Stewarthttps://www.blogger.com/profile/00989044306462002000noreply@blogger.com