Doubt Regd. Circular Replication In Mysql
Hi all, Today i set up a circular replication between three nodes A,B C successfully. I expect whatever writes on A will propagated to B then Propagated to C because the structure is like below :- A - B - C - A I created a sample table stag in test database in A and insert few records that are also replicated to B but not to C. Now when i created the same table in C , it shows errors in show slave status\G output in A node. I needed this setup because all these servers are in different colos so that whatever writes to any node would replicated to others also for one database. I followed the below link for setting this circular replication :- http://www.howtoforge.com/setting-up-master-master-replication-on-four-nodes-with-mysql-5-on-debian-etch-p2 Is it possible to achieve whatever i needed or i need to create Multi Master set up 2 nodes only. Thanks
RE: Doubt Regd. Circular Replication In Mysql
Sounds like you're missing the following in your my.cnf on server B (probably all of them): replicate-same-server-id = 0 log-slave-updates While you're checking, might as well as make sure your auto-increment settings are in there and correct also. -Original Message- From: Adarsh Sharma [mailto:eddy.ada...@gmail.com] Sent: Monday, September 24, 2012 10:23 AM To: mysql@lists.mysql.com Subject: Doubt Regd. Circular Replication In Mysql Hi all, Today i set up a circular replication between three nodes A,B C successfully. I expect whatever writes on A will propagated to B then Propagated to C because the structure is like below :- A - B - C - A I created a sample table stag in test database in A and insert few records that are also replicated to B but not to C. Now when i created the same table in C , it shows errors in show slave status\G output in A node. I needed this setup because all these servers are in different colos so that whatever writes to any node would replicated to others also for one database. I followed the below link for setting this circular replication :- http://www.howtoforge.com/setting-up-master-master-replication-on-four-nodes-with-mysql-5-on-debian-etch-p2 Is it possible to achieve whatever i needed or i need to create Multi Master set up 2 nodes only. Thanks Notice: This communication may contain privileged and/or confidential information. If you are not the intended recipient, please notify the sender by email, and immediately delete the message and any attachments without copying or disclosing them. LBI may, for any reason, intercept, access, use, and disclose any information that is communicated by or through, or which is stored on, its networks, applications, services, and devices. -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql
RE: Doubt Regd. Circular Replication In Mysql
replicate-same-server-id = 0 keeps MySQL from replicating binary log entries from itself. For instance, here's a rough overview: You write to Server A. Server A writes that to its binary log. Server B reads Server A's binary log and completes the same thing. Because log-slave-updates is enabled, Server B writes it to its own binary log. Server C reads Server B's binary log and completes the same thing. Again, with log-slave-updates enabled, Server C writes it to its own binary log. Server A reads Server C's binary log. Here's where the issue starts. Without replicate-same-server-id = 0, Server A will complete the insert/update/delete as it reads it from Server C's binary log. However, this query originated from Server A, so it's just going to do it again. Then it's again replicated to Server B, Server C, and so on. This can create a loop and/or break replication. For instance, if you drop a table on A. It replicates across, and back to A. Replication will error out because when it tries to drop the same table again, it already doesn't exist. You need replicate-same-server-id = 0 set so that it knows not to execute any binary log entries with its own server ID. From: Adarsh Sharma [mailto:eddy.ada...@gmail.com] Sent: Monday, September 24, 2012 10:39 AM To: Stillman, Benjamin Subject: Re: Doubt Regd. Circular Replication In Mysql Yes I fixed , but i solve the issue by enabling log-slave-updates only Why we use the below parameter :- replicate-same-server-id = 0 Ya i configured auto-increment settings properly. Thanks Thanks On Mon, Sep 24, 2012 at 8:03 PM, Stillman, Benjamin bstill...@limitedbrands.commailto:bstill...@limitedbrands.com wrote: Sounds like you're missing the following in your my.cnf on server B (probably all of them): replicate-same-server-id = 0 log-slave-updates While you're checking, might as well as make sure your auto-increment settings are in there and correct also. -Original Message- From: Adarsh Sharma [mailto:eddy.ada...@gmail.commailto:eddy.ada...@gmail.com] Sent: Monday, September 24, 2012 10:23 AM To: mysql@lists.mysql.commailto:mysql@lists.mysql.com Subject: Doubt Regd. Circular Replication In Mysql Hi all, Today i set up a circular replication between three nodes A,B C successfully. I expect whatever writes on A will propagated to B then Propagated to C because the structure is like below :- A - B - C - A I created a sample table stag in test database in A and insert few records that are also replicated to B but not to C. Now when i created the same table in C , it shows errors in show slave status\G output in A node. I needed this setup because all these servers are in different colos so that whatever writes to any node would replicated to others also for one database. I followed the below link for setting this circular replication :- http://www.howtoforge.com/setting-up-master-master-replication-on-four-nodes-with-mysql-5-on-debian-etch-p2 Is it possible to achieve whatever i needed or i need to create Multi Master set up 2 nodes only. Thanks Notice: This communication may contain privileged and/or confidential information. If you are not the intended recipient, please notify the sender by email, and immediately delete the message and any attachments without copying or disclosing them. LBI may, for any reason, intercept, access, use, and disclose any information that is communicated by or through, or which is stored on, its networks, applications, services, and devices.
Re: Doubt Regd. Circular Replication In Mysql
Hello Benjamin, On 9/24/2012 10:52 AM, Stillman, Benjamin wrote: replicate-same-server-id = 0 keeps MySQL from replicating binary log entries from itself. For instance, here's a rough overview: You write to Server A. Server A writes that to its binary log. Server B reads Server A's binary log and completes the same thing. Because log-slave-updates is enabled, Server B writes it to its own binary log. Server C reads Server B's binary log and completes the same thing. Again, with log-slave-updates enabled, Server C writes it to its own binary log. Server A reads Server C's binary log. Here's where the issue starts. Without replicate-same-server-id = 0, Server A will complete the insert/update/delete as it reads it from Server C's binary log. However, this query originated from Server A, so it's just going to do it again. Then it's again replicated to Server B, Server C, and so on. This can create a loop and/or break replication. For instance, if you drop a table on A. It replicates across, and back to A. Replication will error out because when it tries to drop the same table again, it already doesn't exist. You need replicate-same-server-id = 0 set so that it knows not to execute any binary log entries with its own server ID. Not true. Replication, by default, operates with --replicate-same-server-id=0. The only time you need to change it to a 1 is for certain recovery scenarios. We added this variable specifically to allow for exceptions to the rule that every server in a replication chain (or ring) must have their own, unique, --server-id value. It's not required for normal operations. In fact we recommend you do not set it at all. Each server will automatically ignore any event that originates from a server with the same --server-id setting unless you specifically set --replicate-same-server-id=1 . Regards -- Shawn Green MySQL Principal Technical Support Engineer Oracle USA, Inc. - Hardware and Software, Engineered to Work Together. Office: Blountville, TN -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql
Re: Doubt Regd. Circular Replication In Mysql
I stand corrected and apologize. Numerous multi-master setup descriptions I've read have said to set this (including the one linked in the original question). However, as you said, the entry in the manual clearly says it defaults to 0. Learn something new every day. Thanks Shawn. On Sep 24, 2012, at 2:05 PM, Shawn Green shawn.l.gr...@oracle.com wrote: replicate-same-server-id = 0 Notice: This communication may contain privileged and/or confidential information. If you are not the intended recipient, please notify the sender by email, and immediately delete the message and any attachments without copying or disclosing them. LBI may, for any reason, intercept, access, use, and disclose any information that is communicated by or through, or which is stored on, its networks, applications, services, and devices. -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql
RE: Doubt Regd. Circular Replication In Mysql
Don't use circular replication with more than 2 servers. If one of your 3 crashes and cannot be recovered, you will have a nightmare on your hands to fix the broken replication. -Original Message- From: Stillman, Benjamin [mailto:bstill...@limitedbrands.com] Sent: Monday, September 24, 2012 11:56 AM To: Shawn Green Cc: mysql@lists.mysql.com Subject: Re: Doubt Regd. Circular Replication In Mysql I stand corrected and apologize. Numerous multi-master setup descriptions I've read have said to set this (including the one linked in the original question). However, as you said, the entry in the manual clearly says it defaults to 0. Learn something new every day. Thanks Shawn. On Sep 24, 2012, at 2:05 PM, Shawn Green shawn.l.gr...@oracle.com wrote: replicate-same-server-id = 0 Notice: This communication may contain privileged and/or confidential information. If you are not the intended recipient, please notify the sender by email, and immediately delete the message and any attachments without copying or disclosing them. LBI may, for any reason, intercept, access, use, and disclose any information that is communicated by or through, or which is stored on, its networks, applications, services, and devices. -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql
Re: Doubt Regd. Circular Replication In Mysql
Agreed with your point Rick, right now i am maintaining my datadir logging in my EBS volumes so if any of the instance goes down ,we will launch new instance use the existing EBS volumes and start replication again. I think it will start automatically from the point where it goes down and start replicating again. Can we use any other prevention for automating the failover. Thanks On Tue, Sep 25, 2012 at 12:41 AM, Rick James rja...@yahoo-inc.com wrote: Don't use circular replication with more than 2 servers. If one of your 3 crashes and cannot be recovered, you will have a nightmare on your hands to fix the broken replication. -Original Message- From: Stillman, Benjamin [mailto:bstill...@limitedbrands.com] Sent: Monday, September 24, 2012 11:56 AM To: Shawn Green Cc: mysql@lists.mysql.com Subject: Re: Doubt Regd. Circular Replication In Mysql I stand corrected and apologize. Numerous multi-master setup descriptions I've read have said to set this (including the one linked in the original question). However, as you said, the entry in the manual clearly says it defaults to 0. Learn something new every day. Thanks Shawn. On Sep 24, 2012, at 2:05 PM, Shawn Green shawn.l.gr...@oracle.com wrote: replicate-same-server-id = 0 Notice: This communication may contain privileged and/or confidential information. If you are not the intended recipient, please notify the sender by email, and immediately delete the message and any attachments without copying or disclosing them. LBI may, for any reason, intercept, access, use, and disclose any information that is communicated by or through, or which is stored on, its networks, applications, services, and devices. -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql
Replication on MySQL databases
Good day all I am hoping that someone can perhaps help me with some resources or info. I need to go to a meeting in the next hour and was requested this morning to research possible load balancing options for MySQL database. What is currently running is a website (balanced over a couple of web servers all connecting to the same database) using apacje and jdk. 2 MySQL databases running as Masler/Slave replication with all reads and writes going to the master and the slave being used for data exports and failover if required. The websites are rather busy and during times of high load the master server takes some strain. The Databases are being to new upgraded hardware soon, including a database upgrade. The idea is that they also want to introduce load balancing for the MySQL databases in order to manage the high load situations. Any help would be appreciated as google has not yet turned up any sufficient info for me in this short time I had been given. Regards Machiel
Re: Replication on MySQL databases
If your sites are busy with *writes*, you're kind of stuck. Replication means that every write that happens on one side, also MUST happen on the other side, so you win nothing. Well, you win a little delay on half of your writes, which is, to most people, really a downside, not an upside. Your best bet in that scenario would be horizontal partitioning, that is, put part of your tables on a second cluster. This entails quite some changes to your application, though, and a hefty analysis of what tables you NEVER use together in a single query. Can be quite the bugger to implement :-) Keep in the back of your mind (but never tell management) that you *can* actually use federated tables for accessing remote tables, but there's plenty of drawbacks to that. If you're talking mostly reads, you have more options. Even then, though, it is best if your application is keenly aware of what's going on, as you have no guarantee about the time it takes for an insert to replicate to all your slaves - your application shouldn't panic if it can't immediately see the data it just wrote. Other people here will undoubtedly tell you about MMM - I keep hearing that that's pretty good, but I (still) have no personal experience with it, myself. On Thu, Nov 4, 2010 at 10:04 AM, Machiel Richards machi...@rdc.co.zawrote: Good day all I am hoping that someone can perhaps help me with some resources or info. I need to go to a meeting in the next hour and was requested this morning to research possible load balancing options for MySQL database. What is currently running is a website (balanced over a couple of web servers all connecting to the same database) using apacje and jdk. 2 MySQL databases running as Masler/Slave replication with all reads and writes going to the master and the slave being used for data exports and failover if required. The websites are rather busy and during times of high load the master server takes some strain. The Databases are being to new upgraded hardware soon, including a database upgrade. The idea is that they also want to introduce load balancing for the MySQL databases in order to manage the high load situations. Any help would be appreciated as google has not yet turned up any sufficient info for me in this short time I had been given. Regards Machiel -- Bier met grenadyn Is als mosterd by den wyn Sy die't drinkt, is eene kwezel Hy die't drinkt, is ras een ezel
Re: Replication on MySQL databases
Thank you for the quick response just to answer one of the things here, the load is mostly reads as writes only happen in batches every so often. When I am saying reads I am talking of up to 2000-5000 concurrently at any given time during high load. -Original Message- From: Johan De Meersman vegiv...@tuxera.be To: Machiel Richards machi...@rdc.co.za Cc: mysql mailing list mysql@lists.mysql.com Subject: Re: Replication on MySQL databases Date: Thu, 4 Nov 2010 10:21:11 +0100 If your sites are busy with *writes*, you're kind of stuck. Replication means that every write that happens on one side, also MUST happen on the other side, so you win nothing. Well, you win a little delay on half of your writes, which is, to most people, really a downside, not an upside. Your best bet in that scenario would be horizontal partitioning, that is, put part of your tables on a second cluster. This entails quite some changes to your application, though, and a hefty analysis of what tables you NEVER use together in a single query. Can be quite the bugger to implement :-) Keep in the back of your mind (but never tell management) that you *can* actually use federated tables for accessing remote tables, but there's plenty of drawbacks to that. If you're talking mostly reads, you have more options. Even then, though, it is best if your application is keenly aware of what's going on, as you have no guarantee about the time it takes for an insert to replicate to all your slaves - your application shouldn't panic if it can't immediately see the data it just wrote. Other people here will undoubtedly tell you about MMM - I keep hearing that that's pretty good, but I (still) have no personal experience with it, myself. On Thu, Nov 4, 2010 at 10:04 AM, Machiel Richards machi...@rdc.co.za wrote: Good day all I am hoping that someone can perhaps help me with some resources or info. I need to go to a meeting in the next hour and was requested this morning to research possible load balancing options for MySQL database. What is currently running is a website (balanced over a couple of web servers all connecting to the same database) using apacje and jdk. 2 MySQL databases running as Masler/Slave replication with all reads and writes going to the master and the slave being used for data exports and failover if required. The websites are rather busy and during times of high load the master server takes some strain. The Databases are being to new upgraded hardware soon, including a database upgrade. The idea is that they also want to introduce load balancing for the MySQL databases in order to manage the high load situations. Any help would be appreciated as google has not yet turned up any sufficient info for me in this short time I had been given. Regards Machiel -- Bier met grenadyn Is als mosterd by den wyn Sy die't drinkt, is eene kwezel Hy die't drinkt, is ras een ezel
Re: Replication on MySQL databases
Classic scenario where MMM will be your best bet. Check out http://mysql-mmm.org for more information. Setup two masters and 2 or more slaves for full High Availability. It scales extremely well if your application is read-heavy (which most applications are). If you need help implementing this, I work for OpenQuery and we do this kind of setup almost on a weekly basis. Check out the website in the signature and let me/us know if you need our professional help. Otherwise: feel free to ask questions here :) kind regards, On Thu, Nov 4, 2010 at 17:26, Machiel Richards machi...@rdc.co.za wrote: Thank you for the quick response just to answer one of the things here, the load is mostly reads as writes only happen in batches every so often. When I am saying reads I am talking of up to 2000-5000 concurrently at any given time during high load. -- Walter Heck Engineer @ Open Query (http://openquery.com) Exceptional services for MariaDB and MySQL at a fixed budget -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql?unsub=arch...@jab.org
Re: Replication of MySQL Stored Procedure
SP generally goes as per the database you have created. Set you binlog off while creating for the sql. sql_log_bin is the variable to do it. On Tue, Jun 8, 2010 at 1:01 AM, Sabika Gmail sabika.makhd...@gmail.comwrote: I already have mysql in the replicate wild ingore table. I am running mysql 5.1.40sp1 Could it be a bug? On Jun 7, 2010, at 8:30 AM, Rolando Edwards redwa...@logicworks.net wrote: I think this is normal because stored procedures live in mysql.proc. You would have to filter out mysql.proc by adding this to /etc/my.cnf replicate-ignore-table=mysql.proc Rolando A. Edwards MySQL DBA (CMDBA) 155 Avenue of the Americas, Fifth Floor New York, NY 10013 212-625-5307 (Work) 201-660-3221 (Cell) AIM Skype : RolandoLogicWorx redwa...@logicworks.net http://www.linkedin.com/in/rolandoedwards -Original Message- From: Sabika Gmail [mailto:sabika.makhd...@gmail.com] Sent: Monday, June 07, 2010 11:14 AM To: mysql@lists.mysql.com Subject: Replication of MySQL Stored Procedure Hi! I have a database in the wild ignore table as table.%. Recently I created a store procedure on it and it replicated. Does any one know if this is normal bahvior? If I wanted to make sure store procedures do not replicate, what should I do? -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/mysql?unsub=redwa...@logicworks.net -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/mysql?unsub=sureshkumar...@gmail.com -- Thanks Suresh Kuna MySQL DBA
Re: Replication of MySQL Stored Procedure
I think even if you ignore the mysql database from replication and set Is_Deterministic = YES then your stored procedures will be replicated. Please set it to NO if you do not wish the stored procedures will not be replicated. You can set this in mysql.proc table. -- Regards, Manasi Save On Mon, 7 Jun 2010 12:31:13 -0700, Sabika Gmail wrote: I already have mysql in the replicate wild ingore table. I am running mysql 5.1.40sp1 Could it be a bug? On Jun 7, 2010, at 8:30 AM, Rolando Edwards redwa...@logicworks.net wrote: I think this is normal because stored procedures live in mysql.proc. You would have to filter out mysql.proc by adding this to /etc/my.cnf replicate-ignore-table=mysql.proc Rolando A. Edwards MySQL DBA (CMDBA) 155 Avenue of the Americas, Fifth Floor New York, NY 10013 212-625-5307 (Work) 201-660-3221 (Cell) AIM Skype : RolandoLogicWorx redwa...@logicworks.net http://www.linkedin.com/in/rolandoedwards -Original Message- From: Sabika Gmail [mailto:sabika.makhd...@gmail.com] Sent: Monday, June 07, 2010 11:14 AM To: mysql@lists.mysql.com Subject: Replication of MySQL Stored Procedure Hi! I have a database in the wild ignore table as table.%. Recently I created a store procedure on it and it replicated. Does any one know if this is normal bahvior? If I wanted to make sure store procedures do not replicate, what should I do? -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/mysql?unsub=redwa...@logicworks.net -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/mysql?unsub=manasi.s...@artificialmachines.com -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql?unsub=arch...@jab.org
Replication of MySQL Stored Procedure
Hi! I have a database in the wild ignore table as table.%. Recently I created a store procedure on it and it replicated. Does any one know if this is normal bahvior? If I wanted to make sure store procedures do not replicate, what should I do? -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql?unsub=arch...@jab.org
RE: Replication of MySQL Stored Procedure
I think this is normal because stored procedures live in mysql.proc. You would have to filter out mysql.proc by adding this to /etc/my.cnf replicate-ignore-table=mysql.proc Rolando A. Edwards MySQL DBA (CMDBA) 155 Avenue of the Americas, Fifth Floor New York, NY 10013 212-625-5307 (Work) 201-660-3221 (Cell) AIM Skype : RolandoLogicWorx redwa...@logicworks.net http://www.linkedin.com/in/rolandoedwards -Original Message- From: Sabika Gmail [mailto:sabika.makhd...@gmail.com] Sent: Monday, June 07, 2010 11:14 AM To: mysql@lists.mysql.com Subject: Replication of MySQL Stored Procedure Hi! I have a database in the wild ignore table as table.%. Recently I created a store procedure on it and it replicated. Does any one know if this is normal bahvior? If I wanted to make sure store procedures do not replicate, what should I do? -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql?unsub=redwa...@logicworks.net -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql?unsub=arch...@jab.org
Re: Replication of MySQL Stored Procedure
I already have mysql in the replicate wild ingore table. I am running mysql 5.1.40sp1 Could it be a bug? On Jun 7, 2010, at 8:30 AM, Rolando Edwards redwa...@logicworks.net wrote: I think this is normal because stored procedures live in mysql.proc. You would have to filter out mysql.proc by adding this to /etc/my.cnf replicate-ignore-table=mysql.proc Rolando A. Edwards MySQL DBA (CMDBA) 155 Avenue of the Americas, Fifth Floor New York, NY 10013 212-625-5307 (Work) 201-660-3221 (Cell) AIM Skype : RolandoLogicWorx redwa...@logicworks.net http://www.linkedin.com/in/rolandoedwards -Original Message- From: Sabika Gmail [mailto:sabika.makhd...@gmail.com] Sent: Monday, June 07, 2010 11:14 AM To: mysql@lists.mysql.com Subject: Replication of MySQL Stored Procedure Hi! I have a database in the wild ignore table as table.%. Recently I created a store procedure on it and it replicated. Does any one know if this is normal bahvior? If I wanted to make sure store procedures do not replicate, what should I do? -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql?unsub=redwa...@logicworks.net -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql?unsub=arch...@jab.org
Replication between MySQL 3.23.58 and MySQL 5.1.46
Hi, Does anyone know of any issues if we try to replicate data from MySQL database version 3.23.58 and MySQL 5.1.46 ? Cheers Neil
Re: Replication between MySQL 3.23.58 and MySQL 5.1.46
HI Neil, first I dont know if you can do it. As a basic rule if not same version, Master version should always be older than slave, but I am afraid binary log format is too different from 3.23 to 5.1 If you have problems with direct replication In your case I would suggest a couple of solutions. - upgrade 3.23 to 4.1 and then setup replication from 4.1 to 5.14) - setup a chain replication with intermediate versions like: 3.23--4.1--5.1 Just a couple of ideas. You should not have big problems in upgrading 3--4, if you want some idea on how to do it let me know. Claudio 2010/5/5 Tompkins Neil neil.tompk...@googlemail.com Hi, Does anyone know of any issues if we try to replicate data from MySQL database version 3.23.58 and MySQL 5.1.46 ? Cheers Neil -- Claudio
Re: Using Replication in mySQL version 5
Tompkins Neil wrote: Hi We are looking to upgrade our version of mySQL to the latest version of mySQL 5. One of the main features we are going to think about using is replication for our website data. Basically we have 2 websites located in the UK and US which share similar information, and we are going to be using replication as a way of keeping the data up to date and in sync. Based on your experiences, is there anything we should be aware of before investigating this route and putting it into practice ? I've had to take servers out for bad raid-controllers, bad ram, bad mobos. Disks have been the least of my problems. So make sure your architecture tolerates the ability to take members of your pool out without load-spiking the remaining members. And if you're doing filesystem snapshots from a master to a replicant, you will have to either have policy or extra servers available to maintain your uptime when you interrupt the master to flush all the tables, sync the filesystem and do an LVM snapshot. Innodb would require a shutdown. Don't forget that LVM snapshots are copy-on-write, so when that master comes back up and starts processing modifying tables, you'll get amazing system load on a busy system as your file system starts madly copying extents into the snapshot volume. Define a procedure for junior staff how to properly down and up a pool member. Like, if you get a disk-full on one member, and it borks replication, what's the step-by-step for a) determining if replication can re-establish after you do a FLUSH LOGS, b) under what conditions do you have to re-copy all data from one master to another because your replication window has expired and your logs have gotten flushed. Your replication binlogs get really big if you're pushing large materialized views regularly via replication, or your servers have fast disks, not enough size to handle a more than a weekend or whole day (for example) of neglect. Define a procedure for checking your my.cnf files for correct auto-increment-* settings and server-id settings. Junior staff, and even senior staff rarely add more members to the pool, so these settings are often mistaken during a midnight maintenance hour. Procedure for adding members and changing master replication settings is very important. Often your DBA is not racking and changing the equipment. Make sure that you have a good understanding of what kind of capacity you're growing at. I started a project with two four-core boxes with plenty of 15krpm disk and when they got into production, they regularly spiked to load 20 and 30. Not pretty. Not only had my old architecture refused traffic to lighten the load, my new architecture didn't. My data set was growing so fast my sort-buffer settings for the old servers were too small for new servers. I ended up with four DL380s with 8 cores per box. I really had to scramble to get more servers in there. The addition of two more read-only members really helped, and backups handled by replication to an off-site replicant. Another load capacity warning: if your traffic is very spiky, and you get high-load conditions, I've seen reset/dropped connections and also plain old connection timeouts. So if you have RAM for 1024 connections, you prolly can't service 1024 connections when you've got table contention and connections from your web-nodes just start failing. If they fail for too long, then you have to do some FLUSH HOSTS to reset connection attempt counters. I don't know what your application does, but I certainly monitor replication lag. Load spikes can certainly increase lag. I've had to move from single instances of mysql to mysqld_multi and separate databases by replication rate. Your monitoring should also track sql threads. You might need to define procedure on how to deal with pooling-out members that fall too far behind in replication. I've written an iptables script to block webnode connections but allow sql pool member connections. I use this to take a member out to run table repairs or to lighten the load while it does replication catch-up. WAN connectivity for replication is interesting! I did site-to-site transfer using stunnel. I had to negotiate weird Cisco 5502 VPN behavior. Copying gigs of myisam files between sites would knock over my vpn so I had to rate-limit using rsync --bwlimit. Bursting bandwidth charges were still brutal, though. Later, we ended up configuring CBQ (search freshmeat.net for cbq-init) on my backup replicant to limit bandwidth so it wouldn't provoke bursting charges. Jed -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Re: Using Replication in mySQL version 5
Date: Mon, 17 Nov 2008 10:16:16 + From: Tompkins Neil [EMAIL PROTECTED] Subject: Using Replication in mySQL version 5 We are looking to upgrade our version of mySQL to the latest version of mySQL 5. One of the main features we are going to think about using is replication for our website data. Basically we have 2 websites ... hm, I can't tell you much yet, my first few experiences are: - it works. :) - be aware of auto_increment values, until now I found two possible sources of error relating to this, causing a 'duplicate entry for key...' error: 1. if u insert a row on slave-server only, auto_increment happens, and master-server is one behind, resulting in the 'duplicate entry' error on next insert on master-server. 2. we're replicating a typo3-cms. typo3 mostly doesn't really delete table rows, but instead sets a 'deleted' flag. so, basically the same issue as 1.: create a typo3-record on slave only, delete it via typo3 on slave only, but row is still occupied, next insert on master will fail. topics I've still got to look into for our setup: - harddisc space requirements of master server's binary log. i think it's about the same as the databases which are being logged, plus some overhead for the sql statements. one might want to keep this in mind if you expect your database to grow large. - performance and bandwidth. u can restrict replication to individual tables (on slave side - options 'replicate-do-table', etc.), so at least in our setup it'll be just a fraction of what the webserver/mysql has to deliver to the outside world (internet). - master-master replication, both server write to the same table, replication in both directions. currently this seems to work fine, but we haven't done any real-life-load-tests yet. regards, ro -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
RE: Using Replication in mySQL version 5
You'll want an alert to page you when the replication slaves stop for an error; look for Matthew Montgomery's script; we added paging and an 'autofix' step to correct a limited number of duplicate key errors (and email when it does so); I page for other errors. We've had M-M 5.0 replication and M-S 5.1 replication configs running okay for a while -Original Message- From: Tompkins Neil [mailto:[EMAIL PROTECTED] Sent: Monday, November 17, 2008 2:16 AM To: [MySQL] Subject: Using Replication in mySQL version 5 Hi We are looking to upgrade our version of mySQL to the latest version of mySQL 5. One of the main features we are going to think about using is replication for our website data. Basically we have 2 websites located in the UK and US which share similar information, and we are going to be using replication as a way of keeping the data up to date and in sync. Based on your experiences, is there anything we should be aware of before investigating this route and putting it into practice ? Thanks, Neil -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Re: Using Replication in mySQL version 5
You will probably want to set read_only = 1 in the my.cnf on the slave so only super users can change tables. If you do partial replication, you must be sure your developers do not cross-reference schemas where one is replicated and the other is not. You will either get a replication error telling you that something doesn't exist or you won't get any error, but the slave may well get out of sync. On Mon, Nov 17, 2008 at 4:16 AM, Tompkins Neil [EMAIL PROTECTED] wrote: Hi We are looking to upgrade our version of mySQL to the latest version of mySQL 5. One of the main features we are going to think about using is replication for our website data. Basically we have 2 websites located in the UK and US which share similar information, and we are going to be using replication as a way of keeping the data up to date and in sync. Based on your experiences, is there anything we should be aware of before investigating this route and putting it into practice ? Thanks, Neil -- Jim Lyons Web developer / Database administrator http://www.weblyons.com
Using Replication in mySQL version 5
Hi We are looking to upgrade our version of mySQL to the latest version of mySQL 5. One of the main features we are going to think about using is replication for our website data. Basically we have 2 websites located in the UK and US which share similar information, and we are going to be using replication as a way of keeping the data up to date and in sync. Based on your experiences, is there anything we should be aware of before investigating this route and putting it into practice ? Thanks, Neil
Re: Replication vs. mysql-table-sync
Michael Stearne wrote: Is mysql-table-sync design to be used as a fix for when your replication is out of sync OR can it be used instead of replication? Thanks, Michael You need to use replication not mysql-table-sync for replication. mysql-table-sync is use to get it back in sync. keith -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Replication vs. mysql-table-sync
Is mysql-table-sync design to be used as a fix for when your replication is out of sync OR can it be used instead of replication? Thanks, Michael -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Replication between Mysql 4.1.8-standard and MySql 5.0
Hi Comunity, I have a problem while configuring 'Replication'. My Master Database is MySql 4.1.8-standard version, and Slave is 5.0. I want to set Replication between them. Problem here is in MySql 4.1.8-standard version the 'user' table fields are Host, User, Password, Select_priv, Insert_priv, Update_priv, Delete_priv, Create_priv, Drop_priv, Reload_priv, Shutdown_priv, Process_priv File_priv, Grant_priv, References_priv, Index_priv, Alter_priv. To enable replication as we know, we need to Grant permission to Slave mechine with appropriate permissions.I am unable to understand which field i have to Enable?, so that Replication can start. please help me! regards, bala
Re: Monitoring replication in mysql
We use a monitoring system that does TCP based checks on our various systems and can alerts us based on criteria we define. So we right shell scripts that run locally and return certain values and tie those scripts to specific TCP ports using /etc/inetd.conf and /etc/services - This is the script we use to monitor replication on every machine (it's much shorter without my excessive comments): #!/bin/sh # # # Bruce's MySQL Replication Verification Script # /usr/local/mysql/bin/mysql -e show status like 'Slave_running'; This script is then tied to a port, so any web browser or our monitoring system hits http://mysqlserver: (or whatever port you decide on) should get this: Variable_nameValue Slave_runningON From there our monitor takes that data and looks for the keyword ON, if it's there it's happy, if it matches the keyword OFF it sends an alert page and marks the instance as in warning state, any response that doesn't include ON or OFF generates a service down state and also sends pages etc... (If MySQL is running then the slave status will either be ON or OFF... If mysql isn't running the mysql client returns it's own error saying it's unable to connect). Best Regards, Bruce On 12/28/04 1:44 PM, Bruce Dembecki [EMAIL PROTECTED] wrote: Tucker, Gabriel wrote: Anil Write a script that does a slave status and check if either of the threads are running. You could further check for error numbers and descriptions. This is what we do. Gabe -Original Message- From: Anil Doppalapudi [mailto:[EMAIL PROTECTED] Sent: Tuesday, December 21, 2004 6:05 AM To: [EMAIL PROTECTED] Subject: Monitoring replication in mysql Hi, we have no of mysql replication setups in our setup. how to monitor those replication setups.my aim is if any slave goes down my script should immediately send an alert mail to me. if anybody having already developed scripts please let me know otherwise just give me an idea what to monitor in in replication setup. Thanks Anil DBA We have a script that monitors output from SHOW SLAVE STATUS, but actually had one time when replication died, but output from above command looked perfectly fine. It was due to massive table corruption, which was in turn due to filesystem corruption. Now, we have the same test running, but we also have a backup monitor which inserts a value in the master and tries to read it from all replicants. We allow an acceptable delay (5-10 minutes) before we page all admins with this backup test. Greg -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Monitoring replication in mysql
Hi, we have no of mysql replication setups in our setup. how to monitor those replication setups.my aim is if any slave goes down my script should immediately send an alert mail to me. if anybody having already developed scripts please let me know otherwise just give me an idea what to monitor in in replication setup. Thanks Anil DBA -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
RE: Monitoring replication in mysql
Anil Write a script that does a slave status and check if either of the threads are running. You could further check for error numbers and descriptions. This is what we do. Gabe -Original Message- From: Anil Doppalapudi [mailto:[EMAIL PROTECTED] Sent: Tuesday, December 21, 2004 6:05 AM To: [EMAIL PROTECTED] Subject: Monitoring replication in mysql Hi, we have no of mysql replication setups in our setup. how to monitor those replication setups.my aim is if any slave goes down my script should immediately send an alert mail to me. if anybody having already developed scripts please let me know otherwise just give me an idea what to monitor in in replication setup. Thanks Anil DBA -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED] -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Re: Monitoring replication in mysql
Tucker, Gabriel wrote: Anil Write a script that does a slave status and check if either of the threads are running. You could further check for error numbers and descriptions. This is what we do. Gabe -Original Message- From: Anil Doppalapudi [mailto:[EMAIL PROTECTED] Sent: Tuesday, December 21, 2004 6:05 AM To: [EMAIL PROTECTED] Subject: Monitoring replication in mysql Hi, we have no of mysql replication setups in our setup. how to monitor those replication setups.my aim is if any slave goes down my script should immediately send an alert mail to me. if anybody having already developed scripts please let me know otherwise just give me an idea what to monitor in in replication setup. Thanks Anil DBA We have a script that monitors output from SHOW SLAVE STATUS, but actually had one time when replication died, but output from above command looked perfectly fine. It was due to massive table corruption, which was in turn due to filesystem corruption. Now, we have the same test running, but we also have a backup monitor which inserts a value in the master and tries to read it from all replicants. We allow an acceptable delay (5-10 minutes) before we page all admins with this backup test. Greg -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
2 ways Replication in MySQL
Hi, I need to expand the database to 3 different locations. We have 3 servers in 3 cities. So far the database has been in one city and 2 others have been linked to it and worked. But sometimes for a day or more a city lost the connection to the master database and the users could not work. Now I am going to change the method to have a copy of database on each location. Each location should be able to change the data also. All tables are myISAM. I am thinking about 2 ways Replication in MySQL but as MySQL document recommended not to do it because there is no guarantee that we won't have any problem (slow connection or losing connection in a period of time). Have you ever had this kind of situation? How did you solve it? Have you ever found any problem in your solution? Thanks in advance for you advice! Mojtaba -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Re: 2 ways Replication in MySQL
Mojtaba Faridzad [EMAIL PROTECTED] wrote on 18/11/2004 13:59:21: Hi, I need to expand the database to 3 different locations. We have 3 servers in 3 cities. So far the database has been in one city and 2 others have been linked to it and worked. But sometimes for a day or more a city lost the connection to the master database and the users could not work. Now I am going to change the method to have a copy of database on each location. Each location should be able to change the data also. All tables are myISAM. I am thinking about 2 ways Replication in MySQL but as MySQL document recommended not to do it because there is no guarantee that we won't have any problem (slow connection or losing connection in a period of time). Have you ever had this kind of situation? How did you solve it? Have you ever found any problem in your solution? What you are attempting to do is inherently difficult, and I don't think any DBMS has solved it. What do you expect to happen if the links between cities are down, and the *same* row in the database is updated differently by different users? Even when the link is up, you have the possibility of a race condition if users in different places update records within a narrow window. The closest we got to this was having a master database in one place and read-only slaves in another. UPDATE commands were always sent to the master copy, and could not be done when the link was down. SELECTs were sent to the local slave and could therefore continue when the link was down. At the application level, we pipelined a few necessary but uncomplicated updates to be done when the link returned. Alec -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
RE: 2 ways Replication in MySQL
I worked on a military system that went further than this, but again required a proprietary application to perform the updates. Databases were either slave, master, of standalone. Any update transaction was logged to a file. If the master was available then If we are the master we apply the update and sent a replication update to all other databases. If we are the slave we send the transaction to the master and wait for its response. If the master was unavailable then we store the transaction until the master becomes available. At this point we apply any pending updates from the master. We then send our updates to the master an wait for a response. If the master detects a conflict between slave updates and pre applied updates then it refuses the update and sends a conflict message back to the originating slave, where it is up to the user to resolve manually. Standalone is a special version of master. It applies updates locally but remembers what the last update it received from the master was. When it is reconnected to the master the user must manually resolve conflicts and determine which, if any, of the updates should be applied to the master. When I left 14 months into the project we had the basic replication engine working but none of the conflict resolution stuff. Kevin Cowley RD Tel: 0118 902 9099 (direct line) Email: [EMAIL PROTECTED] Web: http://www.alchemetrics.co.uk The closest we got to this was having a master database in one place and read-only slaves in another. UPDATE commands were always sent to the master copy, and could not be done when the link was down. SELECTs were sent to the local slave and could therefore continue when the link was down. At the application level, we pipelined a few necessary but uncomplicated updates to be done when the link returned. Alec .com/[EMAIL PROTECTED] ** ALCHEMETRICS LIMITED (ALCHEMETRICS) Mulberry Park, Fishponds Road, Wokingham, Berkshire, RG41 2GX Tel: +44 (0) 118 902 9000Fax: +44 (0) 118 902 9001 This e-mail is confidential and is intended for the use of the addressee only. If you are not the intended recipient, you are hereby notified that you must not use, copy, disclose, otherwise disseminate or take any action based on this e-mail or any information herein. If you receive this transmission in error, please notify the sender immediately by reply e-mail or by using the contact details above and then delete this e-mail. Please note that e-mail may be susceptible to data corruption, interception and unauthorised amendment. Alchemetrics does not accept any liability for any such corruption, interception, amendment or the consequences thereof. ** -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Re: 2 ways Replication in MySQL
Thanks Alec, how is a bank system implemented? do they have just one master sever and all the other servers are slaves? you solution is not bad and I should think more about it. it's close to one of my solutions: I should convert the database to InnoDB. when a user in location A needs to update or add a new record, the program in background should lock the record in all 3 locations. if it is successful, then user in A can change the data and program should update all 3 locations. if updating has any problem, send rollback command to the other locations. I should have a commands waiting list. if update command could get through but rollback could not, after connection backed, send it to the server. then I should think about how to solve dead lock (if location A send lock to B, and C and before release the lock, connection gone. then B and C should not be locked forever : anyways, it's complicated. - Original Message - From: [EMAIL PROTECTED] To: [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Sent: Thursday, November 18, 2004 9:34 AM Subject: Re: 2 ways Replication in MySQL Mojtaba Faridzad [EMAIL PROTECTED] wrote on 18/11/2004 13:59:21: Hi, I need to expand the database to 3 different locations. We have 3 servers in 3 cities. So far the database has been in one city and 2 others have been linked to it and worked. But sometimes for a day or more a city lost the connection to the master database and the users could not work. Now I am going to change the method to have a copy of database on each location. Each location should be able to change the data also. All tables are myISAM. I am thinking about 2 ways Replication in MySQL but as MySQL document recommended not to do it because there is no guarantee that we won't have any problem (slow connection or losing connection in a period of time). Have you ever had this kind of situation? How did you solve it? Have you ever found any problem in your solution? What you are attempting to do is inherently difficult, and I don't think any DBMS has solved it. What do you expect to happen if the links between cities are down, and the *same* row in the database is updated differently by different users? Even when the link is up, you have the possibility of a race condition if users in different places update records within a narrow window. The closest we got to this was having a master database in one place and read-only slaves in another. UPDATE commands were always sent to the master copy, and could not be done when the link was down. SELECTs were sent to the local slave and could therefore continue when the link was down. At the application level, we pipelined a few necessary but uncomplicated updates to be done when the link returned. Alec -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED] -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Re: 2 ways Replication in MySQL
Thanks Kevin! that's a good method. but in this method we should not have any AUTO_INCREMENT field in tables and a master table should take care of giving a unique key. because at first we should add a record to a table then mysql gives the key. if it's a slave the master is off, then we will be in trouble (two slaves needs to add to the same table when master is off). in this case slaves cannot add any record if they don't have connection. unless I change the key and add the location to the key also (that's a big change and program should be changed also). on the other hand usually primary key is not a field that is visible for the user. then program can change the primary key if there are duplicated in master table and fix all relational tables. anyways, I am wondering how ORACLE can handle this kind of situtaion. - Original Message - From: Kevin Cowley [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Thursday, November 18, 2004 9:56 AM Subject: RE: 2 ways Replication in MySQL I worked on a military system that went further than this, but again required a proprietary application to perform the updates. Databases were either slave, master, of standalone. Any update transaction was logged to a file. If the master was available then If we are the master we apply the update and sent a replication update to all other databases. If we are the slave we send the transaction to the master and wait for its response. If the master was unavailable then we store the transaction until the master becomes available. At this point we apply any pending updates from the master. We then send our updates to the master an wait for a response. If the master detects a conflict between slave updates and pre applied updates then it refuses the update and sends a conflict message back to the originating slave, where it is up to the user to resolve manually. Standalone is a special version of master. It applies updates locally but remembers what the last update it received from the master was. When it is reconnected to the master the user must manually resolve conflicts and determine which, if any, of the updates should be applied to the master. When I left 14 months into the project we had the basic replication engine working but none of the conflict resolution stuff. Kevin Cowley RD Tel: 0118 902 9099 (direct line) Email: [EMAIL PROTECTED] Web: http://www.alchemetrics.co.uk The closest we got to this was having a master database in one place and read-only slaves in another. UPDATE commands were always sent to the master copy, and could not be done when the link was down. SELECTs were sent to the local slave and could therefore continue when the link was down. At the application level, we pipelined a few necessary but uncomplicated updates to be done when the link returned. Alec .com/[EMAIL PROTECTED] ** ALCHEMETRICS LIMITED (ALCHEMETRICS) Mulberry Park, Fishponds Road, Wokingham, Berkshire, RG41 2GX Tel: +44 (0) 118 902 9000Fax: +44 (0) 118 902 9001 This e-mail is confidential and is intended for the use of the addressee only. If you are not the intended recipient, you are hereby notified that you must not use, copy, disclose, otherwise disseminate or take any action based on this e-mail or any information herein. If you receive this transmission in error, please notify the sender immediately by reply e-mail or by using the contact details above and then delete this e-mail. Please note that e-mail may be susceptible to data corruption, interception and unauthorised amendment. Alchemetrics does not accept any liability for any such corruption, interception, amendment or the consequences thereof. ** -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED] -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Re: Offline Replication with MySQL
Thanks much... Does this work with InnoDB tables as well as MyISAM? - Original Message - From: Jeremy Zawodny [EMAIL PROTECTED] To: Mauro Marcellino [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Sent: Saturday, November 01, 2003 2:47 AM Subject: Re: Offline Replication with MySQL On Fri, Oct 31, 2003 at 01:45:09PM -0500, Mauro Marcellino wrote: I currently have systems on multiple networks that are only connected via FTP. On one network (network 1) I have replication running with one master and one slave (Both running Windows 2000 Server) On another network (network 2) I have s Sun V880 running Solaris 8 and it is only connected to network 1 via FTP. What are my options with MySQL to keep the box on netowork 2 somewhat in synch with those on network one? I know MS SQL server has something called log shipping to do updates with this scenario, does MySQL have something similar? You could FTP completed binary logs from the master and replay them on the Solaris box. It'd take a bit of scripting, but it should work. Jeremy -- Jeremy D. Zawodny | Perl, Web, MySQL, Linux Magazine, Yahoo! [EMAIL PROTECTED] | http://jeremy.zawodny.com/ MySQL 4.0.15-Yahoo-SMP: up 48 days, processed 1,806,304,337 queries (432/sec. avg) -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED] -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Re: Offline Replication with MySQL
On Mon, Nov 03, 2003 at 03:29:23PM -0500, Mauro Marcellino wrote: Thanks much... Does this work with InnoDB tables as well as MyISAM? Yes. The binlogs work for all table types. -- Jeremy D. Zawodny | Perl, Web, MySQL, Linux Magazine, Yahoo! [EMAIL PROTECTED] | http://jeremy.zawodny.com/ MySQL 4.0.15-Yahoo-SMP: up 50 days, processed 1,890,467,769 queries (429/sec. avg) -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Re: Offline Replication with MySQL
On Fri, Oct 31, 2003 at 01:45:09PM -0500, Mauro Marcellino wrote: I currently have systems on multiple networks that are only connected via FTP. On one network (network 1) I have replication running with one master and one slave (Both running Windows 2000 Server) On another network (network 2) I have s Sun V880 running Solaris 8 and it is only connected to network 1 via FTP. What are my options with MySQL to keep the box on netowork 2 somewhat in synch with those on network one? I know MS SQL server has something called log shipping to do updates with this scenario, does MySQL have something similar? You could FTP completed binary logs from the master and replay them on the Solaris box. It'd take a bit of scripting, but it should work. Jeremy -- Jeremy D. Zawodny | Perl, Web, MySQL, Linux Magazine, Yahoo! [EMAIL PROTECTED] | http://jeremy.zawodny.com/ MySQL 4.0.15-Yahoo-SMP: up 48 days, processed 1,806,304,337 queries (432/sec. avg) -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Offline Replication with MySQL
I currently have systems on multiple networks that are only connected via FTP. On one network (network 1) I have replication running with one master and one slave (Both running Windows 2000 Server) On another network (network 2) I have s Sun V880 running Solaris 8 and it is only connected to network 1 via FTP. What are my options with MySQL to keep the box on netowork 2 somewhat in synch with those on network one? I know MS SQL server has something called log shipping to do updates with this scenario, does MySQL have something similar? Please let me know if anybody has had any success with this or has any suggestions. Thanks Much!, Cheers, Mauro
help me..[replication in MySQL]
MySQL is AMAZING... I'm very interest with replication on MySQL, and after I read in the manual_doc I want to try MySQL-4.x.x. But until now this version not yet available stable release (maybe). How stable release [recomended] can I use for replication on version 4.0.0 ?? Why MySQL only support one way replication?? and how it's TODO?? Is replication MySQL only help for read query?? please explain for me Thank's very much **: sorry my language very bad rgds, indonesian boy Yahoo! Biztools - Promote your business from just $5 a month!
RE: MSSQL Transactional Replication to MySQL
Hi My DBA has created a DTS package that works between two MS SQL machines, successfully adding characters at either side of the source data on the publication. However, we have a problem when trying to replicate to MySQL. If we check the transform data box when creating the SQL Server publication, later on when it comes to creating the subscription within the same wizard, SQL Server does not give us the ODBC connection to MySQL as a subscription option. We've tried altering the succesful SQL Server subscription DTS package so that the subscription connection points towards the MySQL database subscriber instead of SQL Server, but this just leads to a muddle whereby the distributor is looking for SQL Server stored procedures on the MySQL box. Do you have any suggestions for getting around this? It seems fairly embedded in SQL Server logic - check a certain box, then don't get the option you need later on. If I was suspicious I'd say that Microsoft didn't want us to be able to transform data out of SQL Server! Cheers -- Jonathan Bedford Quoting Victor Pendleton [EMAIL PROTECTED]: In the DTS engine you can write a VB script to handle the quotations during the transfer. I replicate from MS SQL to MySQL using Java and came across the same issue. Let me know if you need any help. -Original Message- From: Jonathan Bedford [mailto:[EMAIL PROTECTED]] Sent: Monday, February 03, 2003 2:58 PM To: [EMAIL PROTECTED] Subject: MSSQL Transactional Replication to MySQL Hi Has anyone managed to get Microsoft SQL Server (2000 (SP2)) to replicate data to MySQL (3.23.49) via Microsoft heterogeneous replication MySQL ODBC Driver (3.51)? Deletions at the MS end replicate to the MySQL Successfully, BUT Insertions and updates fail, it seem to be a problem with quotes `' Both servers are running in ANSI mode and the MySQL tables are InnoDB. The trace from the MyODBC driver show that no quotes are been used around the values. Any Ideas? Jonathan - 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 - This mail sent through IMP: http://horde.org/imp/ - 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
RE: MSSQL Transactional Replication to MySQL
Hi Thanks for the information, my Microsoft SQL DBA is looking the DTS VB Script stuff. I will post the information if it works Cheers -- Jonathan Bedford Quoting Victor Pendleton [EMAIL PROTECTED]: In the DTS engine you can write a VB script to handle the quotations during the transfer. I replicate from MS SQL to MySQL using Java and came across the same issue. Let me know if you need any help. -Original Message- From: Jonathan Bedford [mailto:[EMAIL PROTECTED]] Sent: Monday, February 03, 2003 2:58 PM To: [EMAIL PROTECTED] Subject: MSSQL Transactional Replication to MySQL Hi Has anyone managed to get Microsoft SQL Server (2000 (SP2)) to replicate data to MySQL (3.23.49) via Microsoft heterogeneous replication MySQL ODBC Driver (3.51)? Deletions at the MS end replicate to the MySQL Successfully, BUT Insertions and updates fail, it seem to be a problem with quotes `' Both servers are running in ANSI mode and the MySQL tables are InnoDB. The trace from the MyODBC driver show that no quotes are been used around the values. Any Ideas? Jonathan - 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 - This mail sent through IMP: http://horde.org/imp/ - 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
MSSQL Transactional Replication to MySQL
Hi Has anyone managed to get Microsoft SQL Server (2000 (SP2)) to replicate data to MySQL (3.23.49) via Microsoft heterogeneous replication MySQL ODBC Driver (3.51)? Deletions at the MS end replicate to the MySQL Successfully, BUT Insertions and updates fail, it seem to be a problem with quotes ` Both servers are running in ANSI mode and the MySQL tables are InnoDB. The trace from the MyODBC driver show that no quotes are been used around the values. Any Ideas? Jonathan - 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
RE: MSSQL Transactional Replication to MySQL
In the DTS engine you can write a VB script to handle the quotations during the transfer. I replicate from MS SQL to MySQL using Java and came across the same issue. Let me know if you need any help. -Original Message- From: Jonathan Bedford [mailto:[EMAIL PROTECTED]] Sent: Monday, February 03, 2003 2:58 PM To: [EMAIL PROTECTED] Subject: MSSQL Transactional Replication to MySQL Hi Has anyone managed to get Microsoft SQL Server (2000 (SP2)) to replicate data to MySQL (3.23.49) via Microsoft heterogeneous replication MySQL ODBC Driver (3.51)? Deletions at the MS end replicate to the MySQL Successfully, BUT Insertions and updates fail, it seem to be a problem with quotes `' Both servers are running in ANSI mode and the MySQL tables are InnoDB. The trace from the MyODBC driver show that no quotes are been used around the values. Any Ideas? Jonathan - 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 - 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
replication in mysql
Hi All I am trying to make a replication for my database. The master and the slave both in version 3.23.41 I create user with FILE privilege and I flush all the tables and block write queries. Now I run the query SHOW MASTER STATUS and I get null in all the columns (file, position, Binlog_do_db and Binlog_ignore_db) What should I do? Thanks, Inbal - 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
Re: Replication between MySql and MS Sql Server
Look into a product called SQLPorter. http://www.realsoftstudio.com I used it once for a MySQL to MSSQL migration project, but you could go in the other direction. If I remember correctly, I think it includes a scheduling feature. -bill On Tue, Jan 21, 2003 at 01:15:01PM -, John Lodge wrote: Hello all, I wonder if anyone has set up a MySql database to mirror one running on MS Sql Server. Although this sounds like an odd requirement, I have a project where this would be extremely useful. Can anyone give me any suggestions as to where to find out more information on this subject. I have done some searching on Google and in the FAQ, and have not come up with anything that I have found useful. Any comments greatly appreciated, Thanks, John Lodge John Lodge Software Engineer Redwood Technologies Limited T +[44] (0)1344 304 344 F +[44] (0)1344 304 345 M +[44] (0)794 122 1422 E [EMAIL PROTECTED] W www.redwoodtech.com Email Disclaimer The information in this email is confidential and may be legally privileged. It is intended solely for the addressee. Access to this email by anyone else is unauthorised. If you are not the intended recipient, any disclosure, copying, distribution or any action taken or omitted to be taken in reliance on it is prohibited and may be unlawful. When addressed to our clients any opinions or advice contained in this email are subject to the limitations of Redwood Technologies Limited's standard terms and conditions of contract. - 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 - 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
Replication between MySql and MS Sql Server
Hello all, I wonder if anyone has set up a MySql database to mirror one running on MS Sql Server. Although this sounds like an odd requirement, I have a project where this would be extremely useful. Can anyone give me any suggestions as to where to find out more information on this subject. I have done some searching on Google and in the FAQ, and have not come up with anything that I have found useful. Any comments greatly appreciated, Thanks, John Lodge John Lodge Software Engineer Redwood Technologies Limited T +[44] (0)1344 304 344 F +[44] (0)1344 304 345 M +[44] (0)794 122 1422 E [EMAIL PROTECTED] W www.redwoodtech.com Email Disclaimer The information in this email is confidential and may be legally privileged. It is intended solely for the addressee. Access to this email by anyone else is unauthorised. If you are not the intended recipient, any disclosure, copying, distribution or any action taken or omitted to be taken in reliance on it is prohibited and may be unlawful. When addressed to our clients any opinions or advice contained in this email are subject to the limitations of Redwood Technologies Limited's standard terms and conditions of contract. - 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
replication of mysql on 2 different OS
hi gurus, iam facing a problem or situation that i have installed mysql 3.23.52 on Windows 2000 server..which will be my master... i want to setup my slave server which will be on RedHat Linux 7.1 with mysql 3.23.49... can anyone help me out on this Thanks in advance Ganesh Rajan - 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
re: replication of mysql on 2 different OS
On Monday 23 December 2002 13:11, Ganesh Rajan wrote: iam facing a problem or situation that i have installed mysql 3.23.52 on Windows 2000 server..which will be my master... i want to setup my slave server which will be on RedHat Linux 7.1 with mysql 3.23.49... can anyone help me out on this Replication between Windows and RedHat Linux works fine for me. How to set up replication read in the MySQL manual: http://www.mysql.com/doc/en/Replication_HOWTO.html -- For technical support contracts, goto https://order.mysql.com/?ref=ensita This email is sponsored by Ensita.net http://www.ensita.net/ __ ___ ___ __ / |/ /_ __/ __/ __ \/ /Egor Egorov / /|_/ / // /\ \/ /_/ / /__ [EMAIL PROTECTED] /_/ /_/\_, /___/\___\_\___/ MySQL AB / Ensita.net ___/ www.mysql.com - 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
Error during replication in mysql
Hello, I have implemented replication between 2 tables in MySQL since then, once in a while I see this error in the error log files Error reading packet from server: Lost connection to MySQL server during query (read_errno 134,server_errno=2013) Any ideas? Thanks.. - 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
Re: Error during replication in mysql
Vaso, Wednesday, August 28, 2002, 4:09:56 PM, you wrote: VK I have implemented replication between 2 tables in MySQL since then, VK once in a while VK I see this error in the error log files VK Error reading packet from server: Lost connection to MySQL server VK during query (read_errno 134,server_errno=2013) VK Any ideas? Check your tables with CHECK TABLE statement or myisamchk. $ perror 134 Error code 134: Unknown error 134 134 = Record was already deleted (or record file crashed) -- For technical support contracts, goto https://order.mysql.com/?ref=ensita This email is sponsored by Ensita.net http://www.ensita.net/ __ ___ ___ __ / |/ /_ __/ __/ __ \/ /Victoria Reznichenko / /|_/ / // /\ \/ /_/ / /__ [EMAIL PROTECTED] /_/ /_/\_, /___/\___\_\___/ MySQL AB / Ensita.net ___/ www.mysql.com - 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
replication-based mysql high-availability scheme..
Hey all, i'm trying to setup a system in which a slave takes over as master in the case the master dies. we're using innodb w/ databases of about 500 megs, so scp/rsyncing those every night is a pretty daunting task, not to mention we can never be sure that the secondary DB has the most recent data. so, i'm going to setup mysql a mysql slave and have it copy all of the data in that manner. theres some concerns i have though, of course. when the master dies, the slave throws in a new my.cnf and starts up as a master; thats fine. but what about when the original master comes back up? the secondary/backup database could have had INSERTs to it, so the original master must sync those. my solution is just to have the original master startup as a slave to the new master. eventually, everything will sync up. but when? how do i know, and how can i test this? when it does, id like everything to switch back. perhaps theres not a way via mysql commands/variables to do this.. is there a specific file structure i could test for? like checking file sizes/existence of files in mysql's data/ directory? also, when switching masters, what exactly is required? from searching some archives, it seems like i just need to remove master.info hostname.index, and then RESET MASTER on the master: 'a' is primary/master 'b' is secondary/slave a goes down, b restarts as a master a comes back up, rm's its master.info hostname.index files executes RESET MASTER on b starts up as a slave to dopey does this sound right? am i going to run into problems are there any other steps that should be added, particularly since we use InnoDB tables? has/is anyone else setting up similar functionality? I noticed linux-ha, but this isnt exactly what im looking for.. anybody have anything more generalized? ill share my results with the list, if i finish it in time.. thanks, -tom - 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
Replication in MySQL of InnoDb Tables
Hello, when setting up replication in MySQL, do we need to take the tar of the data dir. of the master and save it onto the slave.or when the slave comes up for the first time, it automatically loads the specified databases and tables from the master.??? And for InnoDB tables, we convert the Tables to MyIsam and then after loading, back to InnoDB but then wot abt the tables in slave...??? are they converted to InnoDB automatically using binlog or have to be done manually giving appropriate commands??? Thanx in advance, Ritu Singla - 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
Re: Replication zwischen MYSQL und MS Access 97(2000)
See www.mysqlfront.de. This program will convert Access databases to mySQL fairly painlessly. - Original Message - From: Wouter van Vliet [EMAIL PROTECTED] To: N. Ott [EMAIL PROTECTED]; [EMAIL PROTECTED] Cc: Wouter @ Witbier [EMAIL PROTECTED] Sent: Wednesday, June 12, 2002 3:26 AM Subject: RE: Replication zwischen MYSQL und MS Access 97(2000) Now for the folks who don't speak germen, I'll translate his msg: Hallo, Is there any possibitity to synchronise my Access datbase with a MySQL database? If possible automatic or by user action. While actualising between 2 access copies, there is a Conflict Manager who helps with the actualisation. Is there such a thing between MySQL and Access too? - Now that I have translated his msg, me too would like to answer. I'll be having the some problem too, in some time. Off course I know of the possibilty for both to import and export text files (CSV format or anything alike) but it would be really handy if there was a tool already for such transactions. Thanks ... -Oorspronkelijk bericht- Van: N. Ott [mailto:[EMAIL PROTECTED]] Verzonden: June 12, 2002 11:16 Aan: [EMAIL PROTECTED] Onderwerp: Replication zwischen MYSQL und MS Access 97(2000) Hallo Gibt es eine Möglichkeit meine vorhandene Access DB mit einer MYSQL DB zu syncronisieren. Das möglichst automatisch oder per Zeitauftrag. Beim aktualisieren zwischen 2 Access Replikaten kommt ein Konflict Manager zum tragen. Gibt's ähnliches zwischen MYSQL und Access auch? Mit freundlichen Grüssen Norbert Ott 86564 Brunnen E-mail:[EMAIL PROTECTED] - 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 - 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 - 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
Replication zwischen MYSQL und MS Access 97(2000)
Hallo Gibt es eine Möglichkeit meine vorhandene Access DB mit einer MYSQL DB zu syncronisieren. Das möglichst automatisch oder per Zeitauftrag. Beim aktualisieren zwischen 2 Access Replikaten kommt ein Konflict Manager zum tragen. Gibts ähnliches zwischen MYSQL und Access auch? Mit freundlichen Grüssen Norbert Ott 86564 Brunnen E-mail:[EMAIL PROTECTED] - 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
RE: Replication zwischen MYSQL und MS Access 97(2000)
Now for the folks who don't speak germen, I'll translate his msg: Hallo, Is there any possibitity to synchronise my Access datbase with a MySQL database? If possible automatic or by user action. While actualising between 2 access copies, there is a Conflict Manager who helps with the actualisation. Is there such a thing between MySQL and Access too? - Now that I have translated his msg, me too would like to answer. I'll be having the some problem too, in some time. Off course I know of the possibilty for both to import and export text files (CSV format or anything alike) but it would be really handy if there was a tool already for such transactions. Thanks ... -Oorspronkelijk bericht- Van: N. Ott [mailto:[EMAIL PROTECTED]] Verzonden: June 12, 2002 11:16 Aan: [EMAIL PROTECTED] Onderwerp: Replication zwischen MYSQL und MS Access 97(2000) Hallo Gibt es eine Möglichkeit meine vorhandene Access DB mit einer MYSQL DB zu syncronisieren. Das möglichst automatisch oder per Zeitauftrag. Beim aktualisieren zwischen 2 Access Replikaten kommt ein Konflict Manager zum tragen. Gibts ähnliches zwischen MYSQL und Access auch? Mit freundlichen Grüssen Norbert Ott 86564 Brunnen E-mail:[EMAIL PROTECTED] - 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 - 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
RE: Replication zwischen MYSQL und MS Access 97(2000)
At 11:26 12-6-2002, Wouter van Vliet shared with all of us: [...] Now that I have translated his msg, me too would like to answer. I'll be having the some problem too, in some time. Off course I know of the possibilty for both to import and export text files (CSV format or anything alike) but it would be really handy if there was a tool already for such transactions. I know there's a tool around for importing Access to Mysql through ODBC. Last time I tried it ( 2 years ago) it was buggy. These three names in Google should generate some links. This is kewl for a one time import - but not for constant replication and frankly - I fail to see the use for it. Migrate or don't. These two applications are too different to allow such operations. Thanks ... -Oorspronkelijk bericht- Van: N. Ott [mailto:[EMAIL PROTECTED]] Verzonden: June 12, 2002 11:16 Aan: [EMAIL PROTECTED] Onderwerp: Replication zwischen MYSQL und MS Access 97(2000) Hallo Gibt es eine Möglichkeit meine vorhandene Access DB mit einer MYSQL DB zu syncronisieren. Das möglichst automatisch oder per Zeitauftrag. Beim aktualisieren zwischen 2 Access Replikaten kommt ein Konflict Manager zum tragen. Gibts ähnliches zwischen MYSQL und Access auch? Mit freundlichen Grüssen Norbert Ott 86564 Brunnen E-mail:[EMAIL PROTECTED] - 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 - 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 --- Incoming mail is certified Virus Free. Checked by AVG anti-virus system (http://www.grisoft.com). Version: 6.0.370 / Virus Database: 205 - Release Date: 5-6-2002 Best regards, Melvyn Sopacua WebMaster IDG.nl _/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/ If it applies, where it applies - this email is a personal contribution and does not reflect the views of my employer IDG.nl. \_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\ - 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
Re: Replication zwischen MYSQL und MS Access 97(2000)
N. Ott wrote: Hallo Gibt es eine Möglichkeit meine vorhandene Access DB mit einer MYSQL DB zu syncronisieren. Das möglichst automatisch oder per Zeitauftrag. Beim aktualisieren zwischen 2 Access Replikaten kommt ein Konflict Manager zum tragen. Gibt's ähnliches zwischen MYSQL und Access auch? Try: http://www.accessmysql.com/ I didn't use it myself, but it promises synchronisation. A demo is available. Oliver - 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
regarding replication in mysql
Hi,
I followed the steps for two-way replication as described in the
documentation for mysql in section 4.10
We have two servers on suse linux running mysql, lets call them A and B,
considering A as the master and B as the slave
updates and inserts made at both A and B are seen on each other but the
following case doesn't work
1)The ethernet cable which connects A to the network is removed that is
the master is running but it can't see the slave.
2) INSERTS are made to B
3) A is brought back to the network
Now when it is checked for with a select statement.
some additional updates are seen on the table in A,
i.e. all the updates and inserts made on B right from the beginning are
re-entered into the table on A
e.g.
1) on B
insert into customer('ronak',24);
insert into customer ('raghu', 25);
on A
select * from Customers;
ronak 24
raghu 25
would be the output.
2)The ethernet cable of A is removed removing it from the network.
3) on B the following inserts and updates are made.
insert into customer('ramveera',23);
insert into customer('rocky',23);
4) A is bought back to the network
select * from customers.
would give
ronak 24
raghu 25
ronak 24 // added again
raghu 25 // added again
ramveera 23
rocky 23
whereas the output one would expect is
ronak 24
raghu 25
ramveera 23
rocky 23
Could anyone please suggest a solution to this.
regards,
Shivam
-
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
2 way replication in Mysql???
damn anti-spam: sql sql sql sql sql query query query Hi I have the same database twice.. I know that I can use replication to let them copy it in one way... but I would like 2 way replication so you can add records in both databases... The databases do not alway have a connection... and replication must only start when user choose so. Is this possible??? one problem would be to keep the relations ok... can the database handle this? another problem is when two people modify the same record.. two things I though of that could fix this: remember the exact changes, so if one person changes the telephonenumber of record x and another person the streetnaam of that same record x, then merge the changes. And if they modify the same column in the same record, then let one database be superior (possible to choose which one when replication starts? I don't know if my idea's make sense, but I figured that if the database could do all these things it would be possible... if it's not possible I would have to keep a log in the client program...more programming work... grt, Bram - 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
2-way replication in MySQL (sql)
Hi, everyone, This is my another question. I have one master server and one slave server now. In case that the master is down for any reason, I want the slave still accessible by clients. Is that possible in my SQL? by two way replications? This problem seems quiet complicated to me. Please give me some detail ideas or point out the resources helpful. thanks a lot, Joe Chow - 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
Re: 2-way replication in MySQL (sql)
On Fri, May 11, 2001 at 11:50:27AM -0600, Joseph Chow wrote: Hi, everyone, This is my another question. I have one master server and one slave server now. In case that the master is down for any reason, I want the slave still accessible by clients. Is that possible in my SQL? Yes. Just code your software to contact the slave if the master is dead. Jeremy -- Jeremy D. Zawodny, [EMAIL PROTECTED] Technical Yahoo - Yahoo Finance Desk: (408) 349-7878Fax: (408) 349-5454Cell: (408) 439-9951 MySQL 3.23.29: up 128 days, processed 793,208,768 queries (71/sec. avg) - 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
