Purgemasterlogsto 'binlog. 100'; this command is very careful to delete binary logs that are useless to the primary database.
MySQL version: 4.1
Environment introduction: master database 192.168.0.205 slave database 192.168.0.206
1. create/etc/my. cnf in the master database and modify the key value in [mysqld] to increase
Server-id = 1
Log-bin = binlog_name
2. add users to the master database to read logs from the master database.
Grant replication slave, reload, super on *. * to 'Slave '@ '192. 168.0.206 'identified by '20140901'
3. connect the slave database to the master database for testing.
/Opt/mysql/bin/mysql-u slave-p-h 192.168.0.205
4. stop the slave database, modify the slave database/etc/my. cnf, and add the following options:
[Mysqld] server-id = 2 master-host = 192.168.0.205 master-user = slave master-password = 123456
5. start slave database for master-slave database data synchronization
/Opt/mysql/share/mysql start
/Opt/mysql/bin/mysql-u root-p
Mysql> load data from master;
Note: You can use the database to import the data or use the directory to test the data in this step.
6. perform the test:
Create a table in the master database,
Mysql> create database sampdb; mysql> create table new (name char (20), phone char (20); mysql> insert into new ('ABC, '123 ');
Open the slave database and check:
/Opt/mysql/bin/mysql-u root-p mysql> show database; mysql sampdb test mysql> use sampdb; mysql> show tables; new
The master database is successfully created.
7. commands related to the master/slave database:
Slave stop; slave start; start to stop the slave database.
Show slave status \ G; displays the binary log of the primary database that is being read from the database.
Purge master logs to 'binlog. 100'; this command is very careful to delete binary log files that are useless to the master database. If it is deleted by mistake, the slave database cannot be automatically updated.
Change master; modify the parameter usage on the server.
(T115)