MySQL Database Synchronization instance demonstration

The synchronization instance of the MySQL database is demonstrated. In this experiment, the primary and secondary synchronization configuration of the MySQL database (the best combination with PHP) is not required. If it is useless, I will not talk about it much, the actual configuration steps are as follows. MySQL (the best combination with PHP) in this test is 4.1.7-standard-log. Master Operating System

The synchronization instance of the MySQL database is demonstrated. In this experiment, the primary and secondary synchronization configuration of the MySQL database (the best combination with PHP) is not required. If it is useless, I will not talk about it much, the actual configuration steps are as follows. MySQL (the best combination with PHP) in this test is 4.1.7-standard-log. Master Operating System

The synchronization instance of the MySQL database is demonstrated. In this experiment, the primary and secondary synchronization configuration of the MySQL database (the best combination with PHP) is not required. If it is useless, I will not talk about it much, the actual configuration steps are as follows. MySQL (the best combination with PHP) in this test is 4.1.7-standard-log.

The master operating system is redhat 9.0 and the slave operating system is redhat 7.3.

1. modify my. cnf on the master end and add the configuration parameters:

 
 

  
  
[MySQL (the best combination with PHP) d]
  
  
Log-bin
  
  
Server-id = 1
 
 

2. modify my. cnf on the slave side and add the configuration parameters:

 
 

  
  
log-bin 
  
  
mastermaster-host=master 
  
  
master-user=rep 
  
  
master-password=rep 
  
  
master-port=3306 
  
  
server-id=2 
 
 

The above parameters are the most basic configuration, so I will not explain them much. I will undo it to initialize the data.

1. Clear all binlogs on the master. If the existing binlogs are useful, back up them first. Then, pack all data files on the master, including ibdata files.

2. A similar method is used to clear all binlogs on the slave and copy the data file compressed package on the master to its own data file directory.

Start the master and add a rep user,

 
 

  
  
" grant all privileges on *.* to rep@% identified by 'rep'; flush privileges; ". 
 
 

Start slave and check whether the synchronization is successful.

Generally, the reason for the failure is that the binlog fails to be located after the slave connects to the master. Therefore, you need to set the binlogs of both parties to be consistent, and then stop slave; start slave.

The above content is an introduction to the synchronization instance of the MySQL database. I hope you will have some gains.