CentOS 6.3下MySQL主主互备架构配置
MySQL主主互备结构是基于mysql增量日志基础上的,区别于主从复制结构.在主主复制结构中,两台服务器的任何一台上面的数据库存发生
MySQL主主互备结构是基于mysql增量日志基础上的,区别于主从复制结构.
在主主复制结构中,两台服务器的任何一台上面的数据库存发生了改变都会同步到另一台服务器上,这个改变是基于sql语句的改变,如果删除系统数据库源文件或删除后新创建同名MYSQL表实现同步则无效。这样两台服务器互为主从,并且都能向外提供服务,这就比使用主从复制具有更好的性能.
接下来我将使用两个相同的环境来实现这个效果:
系统环境:CentOS6.3
数据库: mysql-5.6.10
安装配置mysql(略)
1.主1 mysql配置:(192.168.7.201)
删除之前遗留bin日志
# rm -rf /usr/local/mysql/log/bin*
修改mysql配置文件:
# vi /etc/my.cnf
添加:
-----------------
# Replication Master Server 1
# bin日志路径
log-bin = /usr/local/mysql/log/bin.log
# 服务器ID号
server-id = 1
# 忽略mysql数据库复制
binlog-ignore-db=mysql
# 每次增长2
auto-increment-increment = 2
# 设置自动增长的字段的偏移量,即初始值为2
auto-increment-offset = 1
------------
# mysql -u root -p123456
在主1上为主2添加同步帐号
> grant replication slave on *.* to 'slave'@'192.168.7.249' identified by '123456';
将主1的数据库表全部备份,并发送到主2服务器上。
# /usr/local/mysql/bin/mysqldump -u root -p123456 --opt --skip-lock-tables --flush-logs --all-database > /root/allbak.sql
# cd ~
# scp allbak.sql root@192.168.7.249:/root
重启服务
# service mysqld restart
# mysql -u root -p123456;
配置连接到主2服务器(注意这步一定要在主2添加账户后执行)
> stop slave;
> change master to master_host='192.168.7.249',master_user='slave',master_password='123456';
> start slave;
2.主2 mysql配置(192.168.7.249)
删除之前遗留bin日志
# rm -rf /usr/local/mysql/log/bin*
修改mysql配置文件:
# vi /etc/my.cnf
添加:
--------------------
# Replication Master Server 2
# bin日志路径
log-bin = /usr/local/mysql/log/bin.log
server-id=2
# 忽略mysql数据库复制
replicate-ignore-db=mysql
# 每次增长2
auto-increment-increment = 2
# 设置自动增长的字段的偏移量,即初始值为2
auto-increment-offset = 2
---------------------
# mysql -u root -p123456
在主2上为主1添加同步帐号
> grant replication slave on *.* to 'slave'@'192.168.7.201' identified by '123456';
恢复主1的数据库到主2
#/usr/local/mysql/bin/mysql -u root -p123456
重启服务
# service mysqld restart
# mysql -u root -p123456;
配置连接到主1服务器
> stop slave;
> change master to master_host='192.168.7.201',master_user='slave',master_password='123456';
> start slave;
最后分别登陆两台服务器mysql后台查看主主备份连接状态
# mysql -u root -p123456;
> show slave status\G;
搜索这三行,如下则主主互备配置成功
Slave_IO_State: Waiting for master to send event
Slave_IO_Running: Yes
Slave_SQL_Running: Yes
当主1的数据库增加,删除,改变数据时,,主2也会同步更新。
当主2的数据库增加,删除,改变数据时,主1也会同步更新。
这样就可以配合keepalived实现数据库双机热备+数据同步互备,大大提高了MYSQL的可靠性和安全性。
Keepalived+MySQL互备

Hot AI Tools

Undresser.AI Undress
AI-powered app for creating realistic nude photos

AI Clothes Remover
Online AI tool for removing clothes from photos.

Undress AI Tool
Undress images for free

Clothoff.io
AI clothes remover

Video Face Swap
Swap faces in any video effortlessly with our completely free AI face swap tool!

Hot Article

Hot Tools

Notepad++7.3.1
Easy-to-use and free code editor

SublimeText3 Chinese version
Chinese version, very easy to use

Zend Studio 13.0.1
Powerful PHP integrated development environment

Dreamweaver CS6
Visual web development tools

SublimeText3 Mac version
God-level code editing software (SublimeText3)

Hot Topics

Full table scanning may be faster in MySQL than using indexes. Specific cases include: 1) the data volume is small; 2) when the query returns a large amount of data; 3) when the index column is not highly selective; 4) when the complex query. By analyzing query plans, optimizing indexes, avoiding over-index and regularly maintaining tables, you can make the best choices in practical applications.

InnoDB's full-text search capabilities are very powerful, which can significantly improve database query efficiency and ability to process large amounts of text data. 1) InnoDB implements full-text search through inverted indexing, supporting basic and advanced search queries. 2) Use MATCH and AGAINST keywords to search, support Boolean mode and phrase search. 3) Optimization methods include using word segmentation technology, periodic rebuilding of indexes and adjusting cache size to improve performance and accuracy.

Yes, MySQL can be installed on Windows 7, and although Microsoft has stopped supporting Windows 7, MySQL is still compatible with it. However, the following points should be noted during the installation process: Download the MySQL installer for Windows. Select the appropriate version of MySQL (community or enterprise). Select the appropriate installation directory and character set during the installation process. Set the root user password and keep it properly. Connect to the database for testing. Note the compatibility and security issues on Windows 7, and it is recommended to upgrade to a supported operating system.

The difference between clustered index and non-clustered index is: 1. Clustered index stores data rows in the index structure, which is suitable for querying by primary key and range. 2. The non-clustered index stores index key values and pointers to data rows, and is suitable for non-primary key column queries.

MySQL is an open source relational database management system. 1) Create database and tables: Use the CREATEDATABASE and CREATETABLE commands. 2) Basic operations: INSERT, UPDATE, DELETE and SELECT. 3) Advanced operations: JOIN, subquery and transaction processing. 4) Debugging skills: Check syntax, data type and permissions. 5) Optimization suggestions: Use indexes, avoid SELECT* and use transactions.

MySQL supports four index types: B-Tree, Hash, Full-text, and Spatial. 1.B-Tree index is suitable for equal value search, range query and sorting. 2. Hash index is suitable for equal value searches, but does not support range query and sorting. 3. Full-text index is used for full-text search and is suitable for processing large amounts of text data. 4. Spatial index is used for geospatial data query and is suitable for GIS applications.

In MySQL database, the relationship between the user and the database is defined by permissions and tables. The user has a username and password to access the database. Permissions are granted through the GRANT command, while the table is created by the CREATE TABLE command. To establish a relationship between a user and a database, you need to create a database, create a user, and then grant permissions.

MySQL and MariaDB can coexist, but need to be configured with caution. The key is to allocate different port numbers and data directories to each database, and adjust parameters such as memory allocation and cache size. Connection pooling, application configuration, and version differences also need to be considered and need to be carefully tested and planned to avoid pitfalls. Running two databases simultaneously can cause performance problems in situations where resources are limited.
