From: Nitin Mehta Date: May 3 2012 4:24am Subject: Re: using the bin-log approach on the master side, how can I accomplish my replication objectives List-Archive: http://lists.mysql.com/mysql/227303 Message-Id: <1336019075.33671.YahooMailNeo@web161602.mail.bf1.yahoo.com> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="406169123-196311771-1336019075=:33671" --406169123-196311771-1336019075=:33671 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Hi Charles, =0AI believe you would already have bin-log configured, is that= right? If not, you need to. =0ASecondly, If you think the bin-log generate= d for the entire stack of databases/schemas is too big, you may want to res= trict it using "binlog-do-db" BUT that may create problem if you have any D= MLs which run in the below manner: =0Amysql> use db1;=0Amysql> update db2.t= b2 .... =0AYou may be surprised to find that this update will not be record= ed in master's bin-log if you have set "binlog-do-db=3Ddb2". =0ATo sum it u= p, if you're not very sure, simply enable bin-log on master and use "replic= ate-do-table" on slave. So in one word response to your question, no! =0AHo= pe that helps! =0AAlso, please=C2=A0reply to all so the people, helping you= , know about the status of your problem.=0A=C2=A0=0A=C2=A0=0ARegards,=0A=0A= =0A=0A________________________________=0A From: "Brown, Charles" =0ATo: Nitin Mehta =0ASent: Thursday, May 3, 2012= 9:27 AM=0ASubject: RE: using the bin-log approach on the master side, how = can I accomplish my replication objectives=0A =0A=0AHello Nitin,=0AHelp Me= !=C2=A0 Using your approach, do I have to put anything on =C2=A0the master = =E2=80=9Cmy.cnf=E2=80=9D.=0A=C2=A0=0AThanks=0A=C2=A0=0A=C2=A0=0AFrom:Nitin = Mehta [mailto:ntnmht@stripped] =0ASent: Wednesday, May 02, 2012 10:51 PM= =0ATo: Brown, Charles; Rick James; a.smith@stripped; mysql@stripped= m=0ASubject: Re: using the bin-log approach on the master side, how can I a= ccomplish my replication objectives=0A=C2=A0=0AI guess, it only makes thing= s even more simple.=0A=C2=A0=0AYou should use "replicate-do-table=3Ddb1.tb1= " and so one=C2=A0in slave's cnf to ensure that only this particular table = gets replicated. However, all the databases on master will get bin-logged a= nd you may or may not want to do that.=0A=C2=A0=0ASo making it even simpler= :=0A=C2=A0=0Aon the slave:=0A=C2=A0=0Areplicate-do-table=3Ddb1.tb1=0Areplic= ate-do-table=3Ddb2.tb2=0Areplicate-do-table=3Ddb3.tb3=0AYou might want to h= ave a look at :=0Ahttp://dev.mysql.com/doc/refman/5.5/en/replication-option= s-slave.html#option_mysqld_replicate-do-table=0Ahttp://dev.mysql.com/doc/re= fman/5.5/en/replication-rules.html=0A=C2=A0=0AHope this helps!=0A=C2=A0 =0A= From:"Brown, Charles" =0ATo: Rick James ; "a.smith@stripped" ; "mysql@stripped" =0ASent: Thursday, May 3, 2012 8:51 AM=0ASubject: usin= g the bin-log approach on the master side, how can I accomplish my replicat= ion objectives=0A=0AHello Rick,=0A=0AI think I'll go with your recommendati= ons - but help me here a little bit. Because all look fuzzy like a brain su= rgery. So make it simple and clean for me.=0A=0A=0A=0AFor the sake of simpl= icity, here is what my master has:=0A=0ADatabase: db1=0A=0ATables: db1tb1, = db1tb2, db1tb3=0A=0A=0A=0ADatabase: db2=0A=0ATables: db2tb1, db2tb2, db2tb3= =0A=0A=0A=0ADatabase: db3=0A=0ATables: db3tb1, db3tb2, db3tb3=0A=0A=0A=0ANo= w, I would like to replicate only these tables that belong to respective da= tabases:=0A=0Adb1tb1, db2tb2, and db3tb3=0A=0A=0A=0AMy question is: using t= he bin-log approach on the master side, how can I accomplish my replication= objectives? Help me=0A=0A=0A=0ABest regards and thanks=0A=0A=0A=0A=0A=0A= =0A=0A********************************************=0AThis message is intend= ed only for the use of the Addressee and=0Amay contain information that is = PRIVILEGED and CONFIDENTIAL.=0A=0AIf you are not the intended recipient, yo= u are hereby notified=0Athat any dissemination of this communication is str= ictly prohibited.=0A=0AIf you have received this communication in error, pl= ease erase=0Aall copies of the message and its attachments and notify us=0A= immediately.=0A=0AThank you.=0A********************************************= =0A=0A =0A********************************************=0AThis message is in= tended only =0Afor the use of the Addressee and=0Amay contain information t= hat is PRIVILEGED =0Aand CONFIDENTIAL. =0AIf you are not the intended recip= ient, you are hereby notified=0Athat any =0Adissemination of this communica= tion is strictly prohibited. =0AIf you have received this communication in = error, please erase=0Aall copies =0Aof the message and its attachments and = notify us=0Aimmediately. =0AThank you.=0A**********************************= ********** --406169123-196311771-1336019075=:33671--