MySQL 5.6 Replication Utilities Tutorial d4mer MySQL August 21st, 2017 6 Comments 94 views MySQL Replication Utilities Tutorial. Learn how to use MySQL 5.6 and the MySQL Utilities to setup, monitor and manage your MySQL replication topology. Original source Link to this post! Tags database, mysql, mysql tutorial, open source, oracle, replication, software Share : tweet Previous Next About the : d4mer Related Posts MySQL Tutorial 1 – Remove Duplicate Rows from MySQL Table September 23rd, 2017 (5) MySQL UPDATE Tutorial September 23rd, 2017 [Tutorial #01]Install ProFTPD with Virtual Host and MySQL (Debian/Linux) September 22nd, 2017 MySQL UNION Tutorial | 9 September 22nd, 2017 MySQL tutorial 5 create table example in mysql September 22nd, 2017 Docker Tutorial: Backing Up and Restoring MySQL and WordPress in Docker September 21st, 2017 6 Comments Dallas Bluth August 21, 2017 at 12:39Log in to Reply What about the config file parameters that need to be setup before the replication can begin? Gayan Lakshan August 21, 2017 at 12:39Log in to Reply how to get(open) "bill@utils1:~mysql" and "bill@utils2:~mysql" please help. peace angel August 21, 2017 at 12:39Log in to Reply Nice one Rob Silver August 21, 2017 at 12:39Log in to Reply I liked it but though it oversimplified some things. For example the instructor used the root user a lot which in practical practice is a huge security no no.Also the example did not explain how different configurations or states of the slaves would be effected. For example can I assume as I have that this tool replicates every database and every table or replicable Storage Engines ?What would happen if I was missing any tables in each of the databases would that effectively copy over just the updates and inserts from the time replication begins or would it synchronize each and all tables?? For example if I were replicating a single database innoworld and I only had City table in my slaves and all tables in my master what would happen? Would those first checks have failed or would the tables be copied to sync up the tables?My first thought is no syncing up of tables I must have all the tables defined and only transactions starting when the slaves are started are handled.Still it would be good to understand how the failover utility works internally which it presumably does by keeping track of all the information you shared in those preceding commands. Still those file position issues appear to be handled – where are they handled in the actual mysqlreplicate command?Is that where the master.info information is essentially handled?and the CHANGE TO MASTER commands automatically created and executed in each slave using the original master? Ojee2 August 21, 2017 at 12:39Log in to Reply I think this demo is really confusing with the same names for each server and different ports. Ivan Tu August 21, 2017 at 12:39Log in to Reply Great demo, thanks Andrew Leave A Comment Click here to cancel reply. You must be logged in to post a comment.