MYSQLREPLICATE(1)               MySQL Utilities              MYSQLREPLICATE(1)



NAME
       mysqlreplicate - Set Up and Start Replication Between Two Servers

SYNOPSIS
       mysqlreplicate [options]

DESCRIPTION
       This utility permits an administrator to start replication from one
       server (the master) to another (the slave). The user provides login
       information for the slave and connection information for connecting to
       the master. It is also possible to specify a database to be used to
       test replication.

       The utility reports conditions where the storage engines on the master
       and the slave differ. It also reports a warning if the InnoDB storage
       engine differs on the master and slave. For InnoDB to be the same, both
       servers must be running the same "type" of InnoDB (built-in or the
       InnoDB Plugin), and InnoDB on both servers must have the same major and
       minor version numbers and enabled state.

       By default, the utility issues warnings for mismatches between the sets
       of storage engines, the default storage engine, and the InnoDB storage
       engine. To produce errors instead, use the --pedantic option, which
       requires storage engines to be the same on the master and slave.

       The -vv option displays any discrepancies between the storage engines
       and InnoDB values, with or without the --pedantic option.

       Replication can be started using one of the following strategies.

       o   Start from the current position (default)

           Start replication from the current master binary log file and
           position. The utility uses the SHOW MASTER STATUS statement to
           retrieve this information.

       o   Start from the beginning

           Start replication from the first event recorded in the master
           binary log. To do this, use the --start-from-beginning option.

       o   Start from a binary log file

           Start replication from the first event in a specific master binary
           log file. To do this, use the --master-log-file option.

       o   Start from a specific event

           Start replication from specific event coordinates (specific binary
           log file and position). To do this, use the --master-log-file and
           --master-log-pos options.
       OPTIONS.PP mysqlreplicate accepts the following command-line options:

       o   --help

           Display a help message and exit.

       o   --license

           Display license information and exit.

       o   --master=<master>

           Connection information for the master server.

           To connect to a server, it is necessary to specify connection
           parameters such as user name, host name, password, and either a
           port or socket. MySQL Utilities provides a number of ways to
           provide this information. All of the methods require specifying
           your choice via a command-line option such as --server, --master,
           --slave, etc. The methods include the following in order of most
           secure to least secure.

           o   Use login-paths from your .mylogin.cnf file (encrypted, not
               visible). Example : <login-path>[:<port>][:<socket>]

           o   Use a configuration file (unencrypted, not visible) Note:
               available in release-1.5.0. Example :
               <configuration-file-path>[:<section>]

           o   Specify the data on the command-line (unencrypted, visible).
               Example : <user>[:<passwd>]@<host>[:<port>][:<socket>]


           o   login-path (.mylogin.cnf) : <login-path>[:<port>][:<socket>]

           o   Configuration file : <configuration-file-path>[:<section>]

           o   Command-line : <user>[:<passwd>]@<host>[:<port>][:<socket>]

       o   --master-log-file=<master_log_file>

           Begin replication from the beginning of this master log file.

       o   --master-log-pos=<master_log_pos>

           Begin replication from this position in the master log file. This
           option is not valid unless --master-log-file is given.

       o   --pedantic, -p

           Fail if both servers do not have the same set of storage engines,
           the same default storage engine, and the same InnoDB storage
           engine.

       o   --rpl-user=<replication_user>

           The user and password for the replication user, in the format:
           <user>[:<password>] or <login-path>.

       o   --slave=<slave>

           Connection information for the slave server.

           To connect to a server, it is necessary to specify connection
           parameters such as user name, host name, password, and either a
           port or socket. MySQL Utilities provides a number of ways to
           provide this information. All of the methods require specifying
           your choice via a command-line option such as --server, --master,
           --slave, etc. The methods include the following in order of most
           secure to least secure.

           o   Use login-paths from your .mylogin.cnf file (encrypted, not
               visible). Example : <login-path>[:<port>][:<socket>]

           o   Use a configuration file (unencrypted, not visible) Note:
               available in release-1.5.0. Example :
               <configuration-file-path>[:<section>]

           o   Specify the data on the command-line (unencrypted, visible).
               Example : <user>[:<passwd>]@<host>[:<port>][:<socket>]


       o   --start-from-beginning, -b

           Start replication at the beginning of events logged in the master
           binary log. This option is not valid unless both --master-log-file
           and --master-log-pos are given.

       o   --ssl-ca

           The path to a file that contains a list of trusted SSL CAs.

       o   --ssl-cert

           The name of the SSL certificate file to use for establishing a
           secure connection.

       o   --ssl-cert

           The name of the SSL key file to use for establishing a secure
           connection.

       o   --ssl

           Specifies if the server connection requires use of SSL. If an
           encrypted connection cannot be established, the connection attempt
           fails. Default setting is 0 (SSL not required).

       o   --test-db=<test_database>

           The database name to use for testing the replication setup. If this
           option is not given, no testing is done, only error checking.

       o   --verbose, -v

           Specify how much information to display. Use this option multiple
           times to increase the amount of information. For example, -v =
           verbose, -vv = more verbose, -vvv = debug.

       o   --version

           Display version information and exit.
       NOTES.PP The login user for the master server must have the appropriate
       permissions to grant access to all databases, and have the ability to
       create user accounts. For example, the user account used to connect to
       the master must have the WITH GRANT OPTION privilege.

       The server IDs on the master and slave must be nonzero and unique. The
       utility reports an error if the server ID is 0 on either server or the
       same on the master and slave. Set these values before starting this
       utility.

       Mixing IP and hostnames is not recommended. The replication-specific
       utilities will attempt to compare hostnames and IP addresses as aliases
       for checking slave connectivity to the master. However, if your
       installation does not support reverse name lookup, the comparison could
       fail. Without the ability to do a reverse name lookup, the replication
       utilities could report a false negative that the slave is (not)
       connected to the master.

       For example, if you setup replication using "MASTER_HOST=ubuntu.net" on
       the slave and later connect to the slave with mysqlrplcheck and have
       the master specified as "--master=192.168.0.6" using the valid IP
       address for "ubuntu.net", you must have the ability to do a reverse
       name lookup to compare the IP (192.168.0.6) and the hostname
       (ubuntu.net) to determine if they are the same machine.

       The path to the MySQL client tools should be included in the PATH
       environment variable in order to use the authentication mechanism with
       login-paths. This will allow the utility to use the my_print_defaults
       tools which is required to read the login-path values from the login
       configuration file (.mylogin.cnf).  EXAMPLES.PP To set up replication
       between two MySQL instances running on different ports of the same host
       using the default settings, use this command:

           shell> mysqlreplicate --master=root@localhost:3306 \
                     --slave=root@localhost:3307 --rpl-user=rpl:rpl
           # master on localhost: ... connected.
           # slave on localhost: ... connected.
           # Checking for binary logging on master...
           # Setting up replication...
           # ...done.

       The following command uses --pedantic to ensure that replication
       between the master and slave is successful if and only if both servers
       have the same storage engines available, the same default storage
       engine, and the same InnoDB storage engine:

           shell> mysqlreplicate --master=root@localhost:3306 \
                     --slave=root@localhost:3307 --rpl-user=rpl:rpl -vv --pedantic
           # master on localhost: ... connected.
           # slave on localhost: ... connected.
           # master id = 2
           #  slave id = 99
           # Checking InnoDB statistics for type and version conflicts.
           # Checking storage engines...
           # Checking for binary logging on master...
           # Setting up replication...
           # Flushing tables on master with read lock...
           # Connecting slave to master...
           # CHANGE MASTER TO MASTER_HOST = [...omitted...]
           # Starting slave...
           # status: Waiting for master to send event
           # error: 0:
           # Unlocking tables on master...
           # ...done.

       The following command starts replication from the current position of
       the master (which is the default):

           shell> mysqlreplicate --master=root@localhost:3306 \
                     --slave=root@localhost:3307 --rpl-user=rpl:rpl
            # master on localhost: ... connected.
            # slave on localhost: ... connected.
            # Checking for binary logging on master...
            # Setting up replication...
            # ...done.

       The following command starts replication from the beginning of recorded
       events on the master:

           shell> mysqlreplicate --master=root@localhost:3306 \
                --slave=root@localhost:3307 --rpl-user=rpl:rpl \
                --start-from-beginning
            # master on localhost: ... connected.
            # slave on localhost: ... connected.
            # Checking for binary logging on master...
            # Setting up replication...
            # ...done.

       The following command starts replication from the beginning of a
       specific master binary log file:

           shell> mysqlreplicate --master=root@localhost:3306 \
                     --slave=root@localhost:3307 --rpl-user=rpl:rpl \
                     --master-log-file=my_log.000003
            # master on localhost: ... connected.
            # slave on localhost: ... connected.
            # Checking for binary logging on master...
            # Setting up replication...
            # ...done.

       The following command starts replication from specific master binary
       log coordinates (specific log file and position):

           shell> mysqlreplicate --master=root@localhost:3306 \
                     --slave=root@localhost:3307 --rpl-user=rpl:rpl \
                     --master-log-file=my_log.000001 --master-log-pos=96
            # master on localhost: ... connected.
            # slave on localhost: ... connected.
            # Checking for binary logging on master...
            # Setting up replication...
            # ...done.

       RECOMMENDATIONS.PP You should set read_only=1 in the my.cnf file for
       the slave to ensure that no accidental data changes, such as INSERT,
       DELETE, UPDATE, and so forth, are permitted on the slave other than
       those produced by events read from the master.

       Use the --pedantic and -vv options for setting up replication on
       production servers to avoid possible problems with differing storage
       engines.  PERMISSIONS REQUIRED.PP The users on the master need the
       following privileges: SELECT and INSERT privileges on mysql database,
       REPLICATION SLAVE, REPLICATION CLIENT and GRANT OPTION. The slave users
       need the SUPER privilege. The repl user, used as the argument for the
       --rpl-user option, is either created automatically or if it exists, it
       needs the REPLICATION SLAVE privilege.

COPYRIGHT
       Copyright (C) 2006, 2015, Oracle and/or its affiliates. All rights
       reserved.

       This documentation is free software; you can redistribute it and/or
       modify it only under the terms of the GNU General Public License as
       published by the Free Software Foundation; version 2 of the License.

       This documentation is distributed in the hope that it will be useful,
       but WITHOUT ANY WARRANTY; without even the implied warranty of
       MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
       General Public License for more details.

       You should have received a copy of the GNU General Public License along
       with the program; if not, write to the Free Software Foundation, Inc.,
       51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA or see
       http://www.gnu.org/licenses/.


SEE ALSO
       For more information, please refer to the MySQL Utilities and Fabric
       documentation, which is available online at
       http://dev.mysql.com/doc/index-utils-fabric.html

AUTHOR
       Oracle Corporation (http://dev.mysql.com/).



MySQL 1.5.6                       09/15/2015                 MYSQLREPLICATE(1)
