msyql主从备份的进程
发布时间：2022-01-19 13:38:23 所属栏目：MySql教程 来源：互联网
导读：这篇文章主要讲解了msyql主从备份的过程，文中的讲解内容简单清晰，易于学习与理解，下面请大家跟着小编的思路慢慢深入，一起来研究和学习msyql主从备份的过程吧！ 安装环境： rhel6.5：server1 master rhel6.5：server2 slave 安装数据库： [root@server1 m
|
这篇文章主要讲解了“msyql主从备份的过程”，文中的讲解内容简单清晰，易于学习与理解，下面请大家跟着小编的思路慢慢深入，一起来研究和学习“msyql主从备份的过程”吧！ 安装环境： rhel6.5：server1 master rhel6.5：server2 slave 安装数据库： [root@server1 mysql]# yum install -y mysql-community-client-5.7.17-1.el6.x86_64.rpm mysql-community-common-5.7.17-1.el6.x86_64.rpm mysql-community-libs-5.7.17-1.el6.x86_64.rpm mysql-community-libs-compat-5.7.17-1.el6.x86_64.rpm mysql-community-server-5.7.17-1.el6.x86_64.rpm [root@server1 ~]# vim /etc/my.cnf server-id = n 给服务器分配一个唯一的ID编号 [root@server1 ~]# /etc/init.d/mysqld start 初始化 MySQL 数据库： [确定] Installing validate password plugin: [确定] 正在启动 mysqld： [确定] [root@server1 ~]# cd /var/lib/mysql [root@server1 mysql]# cd /var/lib/mysql [root@server1 mysql]# ls auto.cnf ibdata1 mysql-bin.000002 performance_schema ca-key.pem ib_logfile0 mysql-bin.000003 private_key.pem ca.pem ib_logfile1 mysql-bin.index public_key.pem client-cert.pem ibtmp1 mysqld_safe.pid server-cert.pem client-key.pem mysql mysql.sock server-key.pem ib_bufferpool mysql-bin.000001 mysql.sock.lock sys [root@server1 mysql]# cat mysql-bin.000001 5.7.17-log[8 **4���[# �� �e�[�)�[root@server1 mysql]# ll mysql-bin.000001 -rw-r----- 1 mysql mysql 177 7月 28 14:40 mysql-bin.000001 修改slave配置文件 server-id = n给服务器分配一个唯一的ID编号 [root@server1 mysql]# grep password /var/log/mysqld.log 查看密码 [root@server1 ~]# mysql_secure_installation 初始化 server2同上 server1上授权： mysql> grant replication slave on . to cara@'172.25.35.2' identified by 'Caonimei@478'; Query OK, 0 rows affected, 1 warning (0.02 sec) mysql> flush privileges; 刷新 Query OK, 0 rows affected (0.02 sec) master授权后，slave可以远程登录 [root@server2 ~]# mysql -ucara -p -h 172.25.35.1 mysql> show databases; +--------------------+ | Database | +--------------------+ | information_schema | +--------------------+ 1 row in set (0.00 sec) master上查看： mysql> show master status; +------------------+----------+--------------+------------------+-------------------+ | File | Position | Binlog_Do_DB | Binlog_Ignore_DB | Executed_Gtid_Set | +------------------+----------+--------------+------------------+-------------------+ | mysql-bin.000004 | 843 | | | | +------------------+----------+--------------+------------------+-------------------+ 1 row in set (0.00 sec) 使 slave 与 master 建立连接，从而同步： mysql> change master to master_host='172.25.35.1',master_user='cara',master_password='Caonimei@478',master_log_file='mysql-bin.000004',master_log_pos=843; slave上查看： mysql> show databases -> ; +--------------------+ | Database | +--------------------+ | information_schema | | mysql | | performance_schema | | sys | +--------------------+ mysql> change master to master_host='172.25.35.1',master_user='cara',master_password='Caonimei@478',master_log_file='mysql-bin.000004',master_log_pos=843; [root@server2 mysql]# cd /var/lib/mysql [root@server2 mysql]# cat master.info 25mysql-bin.000004 843 172.25.35.1 cara Caonimei@478<br/" rel="nofollow">br/>mysql-bin.000004 843 172.25.35.1 cara Caonimei@478<br/3306 60 [root@server2 mysql]# cat server2-relay-bin.index ./server2-relay-bin.000001 master端 查看salve状态： mysql> show slave statusG; 1. row Slave_IO_State: Master_Host: 172.25.35.1 Master_User: cara Master_Port: 3306 Connect_Retry: 60 Master_Log_File: mysql-bin.000004 Read_Master_Log_Pos: 843 Relay_Log_File: server1-relay-bin.000001 Relay_Log_Pos: 4 Relay_Master_Log_File: mysql-bin.000004 Slave_IO_Running: No Slave_SQL_Running: No mysql> start slave;(mster和slave都需开启) Query OK, 0 rows affected (0.01 sec) mysql> show slave statusG; 1. row Slave_IO_State: Connecting to master Master_Host: 172.25.35.1 Master_User: cara Master_Port: 3306 Connect_Retry: 60 Master_Log_File: mysql-bin.000004 Read_Master_Log_Pos: 843 Relay_Log_File: server1-relay-bin.000001 Relay_Log_Pos: 4 Relay_Master_Log_File: mysql-bin.000004 Slave_IO_Running: Connecting Slave_SQL_Running: Yes （编辑：武汉站长网） 【声明】本站内容均来自网络，其相关言论仅代表作者个人观点，不代表本站立场。若无意侵犯到您的权利，请及时与联系站长删除相关内容! |
