mysql復制:把一個數據庫實例上所有改變復制到另外一個數據庫庫服務器實例的過程

特點:

1.沒有改變就無所謂復制 ;改變是復制的根本與數據源

2.所有的改變:是指可以復制全部改變,也可以復制部分改變 可以在全部改變中根據業務需求選擇部分庫和部分表的復制

復制的場景：

1.數據庫容災

2.需求：創建一個從數據服務器，做數據的測試和分析

3.負載均衡

4.復制時高可用架構方案的基礎

mysql高可用架構特點

1.數據庫故障的檢測與排除

2.主從數據庫的切換

3.數據的備份和保護

mysql高可用架構常用方案

1.雙主 自動/手工 切換

2.Altas,opneproxy讀寫分離方案

3.MMM架構

4.MHA架構

5.DRDB高可用架構

6.mycat高可用分片架構

7.mysql NDB cluster集群架構

8.percona xtradb cluster(pxc)集群架構

9.mysql fabric高可用架構

mysql復制配置

同步復制步驟

1. 配置master服務器

2. 配置slave實例

3. 配置slave的復制連接到master

1.配置master服務

log-bin=/var/lib/mysql/binlog/mysql-bin.log(打開二進制文件及二進制文件的位置,注意是 是文件 不是文件夾 mysql-bin是二進制日志的開頭格式 ,注意binlog目錄對mysql用戶的權限)

server-id=108 (服務器唯一標識,必須設置,如果沒設置，可通過 進入mysql 后 show binlog events in 'mysql-bin.000001'; 查看)

mysql> show binlog events in 'mysql-bin.000001';+------------------+-----+-------------+-----------+-------------+---------------------------------------+

| Log_name | Pos | Event_type | Server_id | End_log_pos | Info |

+------------------+-----+-------------+-----------+-------------+---------------------------------------+

| mysql-bin.000001 | 4 | Format_desc | 1 | 120 | Server ver: 5.6.35-log, Binlog ver: 4 |

+------------------+-----+-------------+-----------+-------------+---------------------------------------+

設置完重啟mysql服務

mysql>show binary logs;+------------------+-----------+

| Log_name | File_size |

+------------------+-----------+

| mysql-bin.000001 | 143 |

| mysql-bin.000002 | 120 |

+------------------+-----------+mysql> show binlog events in 'mysql-bin.000002';+------------------+-----+-------------+-----------+-------------+---------------------------------------+

| Log_name | Pos | Event_type | Server_id | End_log_pos | Info |

+------------------+-----+-------------+-----------+-------------+---------------------------------------+

| mysql-bin.000002 | 4 | Format_desc | 108 | 120 | Server ver: 5.6.35-log, Binlog ver: 4 |

+------------------+-----+-------------+-----------+-------------+---------------------------------------+mysql>show master status;+------------------+----------+--------------+------------------+-------------------+

| File | Position | Binlog_Do_DB | Binlog_Ignore_DB | Executed_Gtid_Set |

+------------------+----------+--------------+------------------+-------------------+

| mysql-bin.000002 | 120 | | | |

+------------------+----------+--------------+------------------+-------------------+

master的/etc/my.cnf 示例

[mysqld]

datadir=/var/lib/mysql

socket=/var/lib/mysql/mysql.sock

log-bin=/var/lib/mysql/binlog/mysql-bin.log

server-id=108# Disabling symbolic-links is recommended to prevent assorted security risks

symbolic-links=0# Recommendedinstandard MySQL setup

sql_mode=NO_ENGINE_SUBSTITUTION,STRICT_TRANS_TABLES

[mysqld_safe]

log-error=/var/log/mysqld.log

pid-file=/var/run/mysqld/mysqld.pid

explicit_defaults_for_timestamp=true

2.從庫的配置 my.cnf里

server-id=251

開啟從庫進程

start slave ;

如果有警告

show warnings;

3.配置slave連接到master的復制

在主庫上創建一個復制權限的賬號

grant replication slave on *.* to rep@'%' identified by 'rep123456';

flushprivileges;

在從服務器mysql里執行

change masterto master_host='192.168.1.250',

master_port=3306,

master_user='rep',

master_password='rep123456',

master_log_file='mysql-bin.000003',

master_log_pos=106;

master_log_file 表示從哪個二進制文件開始,master_log_pos 表示從哪個位置開始

比如我做測試的主庫是 192.168.1.250 從庫是192.168.1.251

查看從庫狀態

show slave status\G

Slave_IO_State:

Master_Host:192.168.1.250Master_User: rep

Master_Port:3306Connect_Retry:60Master_Log_File: mysql-bin.000003Read_Master_Log_Pos:106Relay_Log_File: mysqld-relay-bin.000001Relay_Log_Pos:4Relay_Master_Log_File: mysql-bin.000003Slave_IO_Running: No

Slave_SQL_Running: No

Replicate_Do_DB:

Replicate_Ignore_DB:

Replicate_Do_Table:

Replicate_Ignore_Table:

Replicate_Wild_Do_Table:

Replicate_Wild_Ignore_Table:

Last_Errno:0Last_Error:

Skip_Counter:0Exec_Master_Log_Pos:106Relay_Log_Space:106Until_Condition: None

Until_Log_File:

Until_Log_Pos:0Master_SSL_Allowed: No

Master_SSL_CA_File:

Master_SSL_CA_Path:

Master_SSL_Cert:

Master_SSL_Cipher:

Master_SSL_Key:

Seconds_Behind_Master:NULLMaster_SSL_Verify_Server_Cert: No

Last_IO_Errno:0Last_IO_Error:

Last_SQL_Errno:0Last_SQL_Error:

View Code

主要參數

Slave_IO_Running: No

Slave_SQL_Running: No

開啟從庫進程

start slave ;

show slave status\G

這時 ：

Slave_IO_Running: Yes

Slave_SQL_Running: Yes

表示配置成功了，在主庫相應表里插入數據,從庫也會有！

如果出現

slave have equal MySQL Server UUIDs

到 /var/lib/mysql/auto.cnf

修改?server-uuid

總結

以上是生活随笔為你收集整理的mysql复制架构迁移到pxc_mysql复制(高可用架构方案的基础)的全部內容，希望文章能夠幫你解決所遇到的問題。

如果覺得生活随笔網站內容還不錯，歡迎將生活随笔推薦給好友。