1.规划
1.1服务器环境规划
负载服务器master及WEB服务器1真实IP：10.10.195.53
负载服务器backup及WEB服务器2真实IP：10.10.195.190
负载服务器虚拟ip：10.10.195.212
1.2软件环境规划
操作系统：RedHatEnterpriseLinuxServerrelease5.6(Tikanga)
keepalived：keepalived-1.2.19
Java：jdk-1.7.0_79
Tomcat：apache-tomcat-7.0.64
2.负载服务器配置
这里只叙述如何安装配置keepalived，至于java以及tomcat的安装及配置，这里不赘述。
2.1安装keepalived
[~]tar-zxvfkeepalived-1.2.19.tar.gz
[~]cdkeepalived-1.2.19
[keepalived-1.2.19]./configure--prefix=/usr/local/keepalived--disable-fwmark
#(如果直接输入./configure有可能报错：configure:error:NoSO_MARKdeclarationinheaders)
[keepalived-1.2.19]make
[keepalived-1.2.19]makeinstall
2.2配置keepalived服务
[keepalived-1.2.19]cp/usr/local/keepalived/sbin/keepalived/usr/sbin/
[keepalived-1.2.19]cp/usr/local/keepalived/etc/sysconfig/keepalived/etc/sysconfig/
[keepalived-1.2.19]cp/usr/local/keepalived/etc/rc.d/init.d/keepalived/etc/init.d/
[keepalived-1.2.19]mkdir/etc/keepalived
[keepalived-1.2.19]cp/usr/local/keepalived/etc/keepalived/keepalived.conf/etc/keepalived/
[keepalived-1.2.19]chkconfig--addkeepalived
[keepalived-1.2.19]chkconfigkeepalivedon
重启\启动\关闭\查看状态keepalived
servicekeepalivedrestart
servicekeepalivedstart
servicekeepalivedstop
servicekeepalivedstatus
2.3配置keepalived.conf文件
[~]mv/etc/keepalived/keepalived.conf/etc/keepalived/keepalived.conf.bak
[~]vi/etc/keepalived//keepalived.conf
主备机的keepalived.conf文件大致相同，只是注意红色标注的地方。
主机配置：
global_defs{
router_idNodeA
}
vrrp_scriptchk_http_port{
script"/opt/tomcat.pid"
interval5
weight2
}
vrrp_instanceVI_1{
stateMASTER
interfaceeth0
virtual_router_id52
priority150
advert_int1
authentication{
auth_typePASS
auth_pass1111
}
track_script{
chk_http_port
}
virtual_ipaddress{
10.10.195.212
}
}
备机配置：
global_defs{
router_idNodeB
}
vrrp_scriptchk_http_port{
script"/opt/tomcat.pid"
interval5
weight2
}
vrrp_instanceVI_1{
stateBACKUP
interfaceeth0
virtual_router_id52
priority100
advert_int1
authentication{
auth_typePASS
auth_pass1111
}
track_script{
chk_http_port
}
virtual_ipaddress{
10.10.195.212
}
}
2.4配置/opt/tomcat.pid
#!/bin/bash
#description:checktomcatserviceanddecidewhetherstopthekeepalivedornot
#editedbyzzh:2015-10-14
CATALINA_HOME=/users/shr/apache-tomcat-7.0.64
JAVA_HOME=/users/shr/util/JavaDir/jdk
exportCATALINA_HOME
exportJAVA_HOME
psax--width=1000|grep"org.apache.catalina.startup.Bootstrapstart"|grep-v"grep"|awk'{printf$1""}'|wc|awk'{print$2}'>tomcat_process_count.txt
readline< tomcat_process_count.txt
start_tomcat=$CATALINA_HOME/bin/startup.sh
if[${line}-lt1]
then
echo-n"===Startingtomcat===:"
${start_tomcat}
#:sudoservicetomcatstart
echo"===tomcatstartok.==="
sleep3
#checkthetomcatstatus.
psax--width=1000|grep"org.apache.catalina.startup.Bootstrapstart"|grep-v"grep"|awk'{printf$1""}'|wc|awk'{print$2}'>tomcat_process_count.txt
readline2< tomcat_process_count.txt
if[${line2}-lt1]
then
sudoservicekeepalivedstop
fi
fi
rmtomcat_process_count.txt
#shellend.
3.日志查看
3.1正常启动
输入tail-f/var/log/messages查看启动keepalived日志：
(MASTER：10.10.195.53)
Sep2915:49:16shrKeepalived[5536]:StartingKeepalivedv1.2.19(09/21,2015)
Sep2915:49:16shrKeepalived_healthcheckers[5538]:NetlinkreflectorreportsIP10.10.195.53added
Sep2915:49:16shrKeepalived_healthcheckers[5538]:NetlinkreflectorreportsIP10.10.195.53added
Sep2915:49:16shrKeepalived_healthcheckers[5538]:RegisteringKernelnetlinkreflector
Sep2915:49:16shrKeepalived_healthcheckers[5538]:RegisteringKernelnetlinkcommandchannel
Sep2915:49:16shrKeepalived_healthcheckers[5538]:Openingfile'/etc/keepalived/keepalived.conf'.
Sep2915:49:16shrKeepalived_healthcheckers[5538]:Configurationisusing:6572Bytes
Sep2915:49:16shrKeepalived[5537]:StartingHealthcheckchildprocess,pid=5538
Sep2915:49:16shrKeepalived_healthcheckers[5538]:UsingLinkWatchkernelnetlinkreflector...
Sep2915:49:16shrKeepalived_vrrp[5539]:NetlinkreflectorreportsIP10.10.195.53added
Sep2915:49:16shrKeepalived_vrrp[5539]:NetlinkreflectorreportsIP10.10.195.53added
Sep2915:49:16shrKeepalived[5537]:StartingVRRPchildprocess,pid=5539
Sep2915:49:16shrKeepalived_vrrp[5539]:RegisteringKernelnetlinkreflector
Sep2915:49:16shrKeepalived_vrrp[5539]:RegisteringKernelnetlinkcommandchannel
Sep2915:49:16shrKeepalived_vrrp[5539]:RegisteringgratuitousARPsharedchannel
Sep2915:49:16shrKeepalived_vrrp[5539]:Openingfile'/etc/keepalived/keepalived.conf'.
Sep2915:49:16shrKeepalived_vrrp[5539]:Configurationisusing:36541Bytes
Sep2915:49:16shrKeepalived_vrrp[5539]:UsingLinkWatchkernelnetlinkreflector...
Sep2915:49:16shrKeepalived_vrrp[5539]:VRRPsockpool:[ifindex(2),proto(112),unicast(0),fd(10,11)]
Sep2915:49:17shrKeepalived_vrrp[5539]:VRRP_Instance(VI_1)TransitiontoMASTERSTATE
Sep2915:49:17shrKeepalived_vrrp[5539]:VRRP_Instance(VI_1)Receivedlowerprioadvert,forcingnewelection
Sep2915:49:18shrKeepalived_vrrp[5539]:VRRP_Instance(VI_1)EnteringMASTERSTATE
Sep2915:49:18shrKeepalived_vrrp[5539]:VRRP_Instance(VI_1)settingprotocolVIPs.
Sep2915:49:18shrKeepalived_vrrp[5539]:VRRP_Instance(VI_1)SendinggratuitousARPsoneth0for10.10.195.212
Sep2915:49:18shrKeepalived_vrrp[5539]:NetlinkreflectorreportsIP10.10.195.212added
Sep2915:49:18shrKeepalived_healthcheckers[5538]:NetlinkreflectorreportsIP10.10.195.212added
Sep2915:49:23shrKeepalived_vrrp[5539]:VRRP_Instance(VI_1)SendinggratuitousARPsoneth0for10.10.195.212
(BACKUP:10.10.195.190)
Sep2915:46:25server1Keepalived[18218]:StartingKeepalivedv1.2.19(09/25,2015)
Sep2915:46:25server1Keepalived_healthcheckers[18220]:NetlinkreflectorreportsIP10.10.195.190added
Sep2915:46:25server1Keepalived_healthcheckers[18220]:NetlinkreflectorreportsIP10.10.195.190added
Sep2915:46:25server1Keepalived_healthcheckers[18220]:RegisteringKernelnetlinkreflector
Sep2915:46:25server1Keepalived_healthcheckers[18220]:RegisteringKernelnetlinkcommandchannel
Sep2915:46:25server1Keepalived_healthcheckers[18220]:Openingfile'/etc/keepalived/keepalived.conf'.
Sep2915:46:25server1Keepalived_healthcheckers[18220]:Configurationisusing:6682Bytes
Sep2915:46:25server1Keepalived[18219]:StartingHealthcheckchildprocess,pid=18220
Sep2915:46:25server1Keepalived[18219]:StartingVRRPchildprocess,pid=18221
Sep2915:46:25server1Keepalived_vrrp[18221]:NetlinkreflectorreportsIP10.10.195.190added
Sep2915:46:25server1Keepalived_vrrp[18221]:NetlinkreflectorreportsIP10.10.195.190added
Sep2915:46:25server1Keepalived_healthcheckers[18220]:UsingLinkWatchkernelnetlinkreflector...
Sep2915:46:25server1Keepalived_vrrp[18221]:RegisteringKernelnetlinkreflector
Sep2915:46:25server1Keepalived_vrrp[18221]:RegisteringKernelnetlinkcommandchannel
Sep2915:46:25server1Keepalived_vrrp[18221]:RegisteringgratuitousARPsharedchannel
Sep2915:46:25server1Keepalived_vrrp[18221]:Openingfile'/etc/keepalived/keepalived.conf'.
Sep2915:46:25server1Keepalived_vrrp[18221]:Configurationisusing:36651Bytes
Sep2915:46:25server1Keepalived_vrrp[18221]:UsingLinkWatchkernelnetlinkreflector...
Sep2915:46:25server1Keepalived_vrrp[18221]:VRRP_Instance(VI_1)EnteringBACKUPSTATE
Sep2915:46:25server1Keepalived_vrrp[18221]:VRRPsockpool:[ifindex(2),proto(112),unicast(0),fd(10,11)]
3.2主备切换
l当在主机(MASTER：10.10.195.53)中输入sudoservicekeepalivedstop，此时就会进行主备切换，主机切换成备机。
主机(MASTER：10.10.195.53)输出如下
Oct1413:25:09shrKeepalived_vrrp[26683]:VRRP_Instance(VI_1)sending0priority
Oct1413:25:09shrKeepalived_vrrp[26683]:VRRP_Instance(VI_1)removingprotocolVIPs.
Oct1413:25:09shrKeepalived_healthcheckers[26682]:NetlinkreflectorreportsIP10.10.195.212removed
Oct1413:25:09shrKeepalived[26681]:StoppingKeepalivedv1.2.19(09/21,2015)
备机(BACKUP:10.10.195.190)输出如下
Oct1413:19:58server1Keepalived_vrrp[30890]:VRRP_Instance(VI_1)TransitiontoMASTERSTATE
Oct1413:19:59server1Keepalived_vrrp[30890]:VRRP_Instance(VI_1)EnteringMASTERSTATE
Oct1413:19:59server1Keepalived_vrrp[30890]:VRRP_Instance(VI_1)settingprotocolVIPs.
Oct1413:19:59server1Keepalived_vrrp[30890]:VRRP_Instance(VI_1)SendinggratuitousARPsoneth0for10.10.195.212
Oct1413:19:59server1Keepalived_healthcheckers[30889]:NetlinkreflectorreportsIP10.10.195.212added
Oct1413:19:59server1Keepalived_vrrp[30890]:NetlinkreflectorreportsIP10.10.195.212added
Oct1413:20:04server1Keepalived_vrrp[30890]:VRRP_Instance(VI_1)SendinggratuitousARPsoneth0for10.10.195.212
l当在主机(MASTER：10.10.195.53)中输入sudoservicekeepalivedstart,此时就会切换成主机。备机(BACKUP:10.10.195.190)输出如下信息：
Oct1413:25:11server1Keepalived_vrrp[30890]:VRRP_Instance(VI_1)Receivedhigherprioadvert
Oct1413:25:11server1Keepalived_vrrp[30890]:VRRP_Instance(VI_1)EnteringBACKUPSTATE
Oct1413:25:11server1Keepalived_vrrp[30890]:VRRP_Instance(VI_1)removingprotocolVIPs.
Oct1413:25:11server1Keepalived_healthcheckers[30889]:NetlinkreflectorreportsIP10.10.195.212removed
Oct1413:25:11server1Keepalived_vrrp[30890]:NetlinkreflectorreportsIP10.10.195.212removed
4.查看虚拟ip
可以通过ipaddshow命令查看添加的虚拟ip：
[shr@shrbin]$ipaddshow
1:lo:mtu16436qdiscnoqueue
link/loopback00:00:00:00:00:00brd00:00:00:00:00:00
inet127.0.0.1/8scopehostlo
2:eth0:mtu1500qdiscpfifo_fastqlen1000
link/ether00:0c:29:6b:f2:a8brdff:ff:ff:ff:ff:ff
inet10.10.195.53/24brd10.10.195.255scopeglobaleth0
inet10.10.195.212/32scopeglobaleth0
5.常见错误
5.1常见错误一：
/var/log/messageshasthousandsoferrorslikethis:
Jun2809:18:32rustKeepalived_vrrp:receiveaninvalidipnumbercount
associatedwithVRID!
Jun2809:18:32rustKeepalived_vrrp:bogusVRRPpacketreceivedoneth0!!!
Jun2809:18:32rustKeepalived_vrrp:VRRP_Instance(VI_1)Droppingreceived
VRRPpacket...
Thebackupdirectorstartsup,butdoesn'tlistenonthevirtualaddresses
atall.Its/var/log/messageshasthousandsoferrorslikethis:
Jun2806:25:05styeKeepalived_vrrp:receiveaninvalidipnumbercount
associatedwithVRID!
Jun2806:25:05styeKeepalived_vrrp:bogusVRRPpacketreceivedoneth0!!!
Jun2806:25:05styeKeepalived_vrrp:VRRP_Instance(VI_1)ignoringreceived
advertisment...
解决方法：
改变配置文件/etc/keepalived/keepalived.conf中virtual_router_id为另一个值即可。
(changedthevridtoanothernumberanditworkedfine).
5.2常见错误二：
主机执行到VRRP_Instance(VI_1)EnteringBACKUPSTATE之后没有执行VRRP_Instance(VI_1)settingprotocolVIPs。
解决方法：
可能是配置文件keepalived.conf中{左边没有空格。
附
linux添加tomcat服务
在/etc/init.d中输入sudovimtomcat
脚本具体内容如下：
#!/bin/bash
#chkconfig:23451090
#description:StartsandStopsthetomcatdaemon
#editedbyZZH:2015-10-14
CATALINA_HOME=/users/shr/apache-tomcat-7.0.64
JAVA_HOME=/users/shr/util/JavaDir/jdk
exportCATALINA_HOME
exportJAVA_HOME
start_tomcat=$CATALINA_HOME/bin/startup.sh
stop_tomcat=$CATALINA_HOME/bin/shutdown.sh
if[!-f$CATALINA_HOME/bin/catalina.sh]
then
echo"===Tomcatisnotavailable.==="
exit
fi
start()
{
echo-n"===Startingtomcat===:"
${start_tomcat}
echo"===tomcatstartok.==="
}
stop()
{
echo-n"===Shuttingdowntomcat===:"
${stop_tomcat}
echo"===tomcatstopok.==="
}
status()
{
psax--width=1000|grep"org.apache.catalina.startup.Bootstrapstart"|grep-v"grep"|awk'{printf$1""}'|wc|awk'{print$2}'>tomcat_process_count.txt
readline< tomcat_process_count.txt
rmtomcat_process_count.txt
if[$line-gt0]
then
echo-n"tomcat(pid="
psax--width=1000|grep"org.apache.catalina.startup.Bootstrapstart"|grep-v"grep"|awk'{printf$1""}'|awk'{print$1}'>tomcat_process_pid.txt
readpid< tomcat_process_pid.txt
rmtomcat_process_pid.txt
echo-n$pid
echo-n")isrunning..."
echo
else
echo"tomcatisstopped"
fi
}
case"$1"in
start)
start
;;
stop)
stop
;;
restart)
stop
sleep1
start
;;
status)
status
;;
*)
echo"Usage:$0{start|stop|restart}"
exit1
esac
exit0
#shellend.
在终端输入:
sudochmod755tomcat
sudochkconfig--addtomcat
tomcat启动servicetomcatstart
tomcat关闭servicetomcatstop
tomcat重启servicetomcatrestart
tomcat状态查看servicetomcatstatus

什么是MySQL的双机热备？mysql的双机热备是怎样的一种机制呢？今天给大家介绍如何正确操作mysql的双机热备。
以下的文章主要是介绍实现MySQL双机热备的实际操作步骤，浏览此文希望会给你带来一些帮助在此方面。以下就好似文章的主要内容。
MySQL数据库与php搭配是实现MySQL双机热备的最佳组合，其原理主要是通过对日志的更新,用MySQL数据库(和PHP搭配之最佳组合)的SELECT的文件来操作相关功能，备机实时抓取主机的更新日志。
当然这只是其原理，实际上并不需要我们自己去处理日志，明白了原理，实施就比较容易理解了。
这样，在主机端需要开一个账号，这个账号是备机用来抓取主机的更新日志。需要有文件访问权限，在早期，刚开始实现MySQL双机热备时，就是用的文件权限。
从MySQL(和PHP搭配之最佳组合)4开始，添加了一个专门的权限，用来做热备，这个权限本质应该还是文件读取权限，但是应该只能用来读取日志，防止一些漏洞。
对于客户端来说，就是设置这个账号，密码，主服务器地址，还有要同步的数据库名。这只是单向的，再配置一个对等的同步通道，就支持双向的热备了。
通过热备，还可以备端从主端load全部数据。这个在同步出错时可以使用。load权限是一个单独的MySQL(和PHP搭配之最佳组合)权限,这样跟热备有关的MySQL(和PHP搭配之最佳组合)的权限有2个，日志抓取和数据载入(REPLICATIONSLAVE,REPLICATIONCLIENT)
在服务器端开备份账号
在服务器端打开日志功能
这样，MySQL(和PHP搭配之最佳组合)会在数据目录放置pa这个库的更新日志。等待备机来抓取。
客户端设置:
/etc/MySQL(和PHP搭配之最佳组合)/my.cnf
master-host=192.168.1.1
master-user=backup
master-password=12345
master-port=3306
master-connect-retry=60
replicate-do-db=pa客户端会到服务器抓取pa库的更新日志，来更新本地的pa库。
几个跟热备有关的MySQL(和PHP搭配之最佳组合)命令:(需要在MySQL(和PHP搭配之最佳组合)命令行界面或query)
stopslave#停止同步
startslave#开始同步，从日志终止的位置开始更新。
SETSQL_LOG_BIN=0|1#主机端运行，需要super权限，用来开停日志，随意开停，会造成主机从机数据不一致，造成错误
SETGLOBALSQL_SLAVE_SKIP_COUNTER=n#客户端运行，用来跳过几个事件，只有当同步进程出现错误而停止的时候才可以执行。
RESETMASTER#主机端运行,清除所有的日志，这条命令就是原来的FLUSHMASTER
RESETSLAVE#从机运行，清除日志同步位置标志，并重新生成master.info
虽然重新生成了master.info,但是并不起用，最好，将从机的MySQL(和PHP搭配之最佳组合)进程重启一下，
LOADTABLEtblnameFROMMASTER#从机运行，从主机端重读指定的表的数据，每次只能读取一个，受timeout时间限制，需要调整timeout时间。执行这个命令需要同步账号有reload和super权限。以及对相应的库有select权限。如果表比较大，要增加NET_read_timeout和net_write_timeout的值
LOADDATAFROMMASTER#从机执行，从主机端重新读入所有的数据。执行这个命令需要同步账号有reload和super权限。以及对相应的库有select权限。如果表比较大，要增加net_read_timeout和net_write_timeout的值
CHANGEMASTERTOmaster_def_list#在线改变一些主机设置，多个用逗号间隔,比如
下面是Q&A时间:
MySQL双机热备怎么配置？照上面再配置一个反向的更新就行了。
不用担心本机的更改会回环回来，因为server_id就是识别这个用的.
多机热备怎么做,几台MySQL(和PHP搭配之最佳组合)服务器就像首尾相连的蛇,组成一个环装,就可以了,而且还可以作几个单向的更新,用以分担select这样的读取操作的压力。
以上就是我们所要介绍的关于mysql双机热备的问题，希望能给大家一定的帮助。

如何实现华为防火墙双机热备负载分担



各位大佬，这个拓扑模型能实现防火墙双机热备负载均衡吗，做了好久没做出来，基础知识实在有限，大佬们能指点一下吗

帮忙配置一下

之前我们已经搭建好了MyCat管理的PXC集群以及replication集群
MyCat实现PXC集群负载均衡以及replication集群读写分离
为了实现高可用，我们接下来需要在MyCat中间件之前使用Keepalived实现双机热备
一.Keepalived如何实现双机热备？
为了实现高可用，我们使用keepalived来实现双机热备。
其主要工作原理是，在MyCat容器上面使用keepalived来生成一个虚拟IP地址。
连接数据库的时候不实用MyCat的IP地址，而是使用keepalived的虚拟IP地址。
在我们构建的双keepalived+MyCat方案中，两个keepalived争抢节点连接，
抢到之后该节点变为master节点，另一个节点变成backup节点。
同时master节点开始向外发布广播，如果master节点宕机，那么广播就会停止，
此时backup收不到广播，就会去获得节点连接，实现双机热备。
因为在Keepalived一方面把MyCat端口的请求映射到swarm集群中的虚拟IP。
但是在swarm集群外部，我们是没有办法访问到swarm集群的，因此需要在宿主机上安装keepalived，然后把宿主机的某个端口映射到swarm集群中的虚拟IP中的端口。
这样才可以实现双机热备
二.Keepalived在Docker容器的配置
首先，因为keepalived端口发送广播是VRRP协议的，因此需要centos7先支持VRRP协议。
vrrp在Docker上面的配置如下：
{

state 	Mater			##这里配置keepalived节点的地位 master代表主节点，backup代表备用节点，如果两个都设置为master，那么两个节点在开始连接的时候会竞争

interface 	docker_gwbridge      ##dokcer_gwbridge指docker虚拟机的网卡

virtual_route_id  	51    ##这里指多个keepalived连接时的路由号，必须保持一致

priority   	100      ##分配权重

advert_int 	1        ##表示1S没有接受到master的VRRP广播就开始竞争节点

autnentication {		

​		auth_type  		PASS					##表示使用密码方式来链接

​		auth_pass  		123456

}

virtual_ipaddress{				##映射的虚拟IP

​				172.18.0.201

}

}

三.Keepalived在宿主机的配置
这里因为Keepalived是安装在宿主机上面，因此我们需要把宿主机上面配置上虚拟IP跟上面相似

state 	Mater			##这里配置keepalived节点的地位 master代表主节点，backup代表备用节点，如果两个都设置为master，那么两个节点在开始连接的时候会竞争

interface 	docker_gwbridge      ##dokcer_gwbridge指docker虚拟机的网卡

virtual_route_id  	61    ##这里跟上面的路由号不一样

priority   	100      ##分配权重

advert_int 	1        ##表示1S没有接受到master的VRRP广播就开始竞争节点

autnentication {		

​		auth_type  		PASS					##表示使用密码方式来链接

​		auth_pass  		123456

}

virtual_ipaddress{				##映射的虚拟IP

​				192.168.99.150   ##注意 这是宿主机的虚拟IP

}


但是呢 因为我们需要映射到Docker的某些端口上，因此比上面我们需要多配置一些
{

virtual_server 192.168.99.150  8066{

​		delay_loop   	3 

​		lb_algo		rr

​		lb_kind 	   NAT

​		persistence 	 timeout  50

​		protocol      TCP

​		real_reserver 	 172.18.0.201.8066{  ##虚拟IP接受到请求之后，把IP转发到真正的IP

​			weight     1

​			}

}

virtual_server 192.168.99.150  9066{

​		delay_loop   	3 

​		lb_algo		rr

​		lb_kind 	   NAT

​		persistence 	 timeout  50

​		protocol      TCP

​		real_reserver 	 172.18.0.201.9066{  ##虚拟IP接受到请求之后，把IP转发到真正的IP

​			weight     1

​			}

}

}

这里我们可以看到，在宿主机上的keepalived把宿主机上的两个虚拟端口转发到Docker上的两个keepalived节点上面。这里我们的配置就完成了。