Zarafa High Availability setup with MySQL master-slave - Revision history

Mars-solutions at 12:31, 3 August 2012

2012-08-03T12:31:26Z

← Older revision		Revision as of 12:31, 3 August 2012
Line 59:		Line 59:

	<code>		<code>
-	GRANT REPLICATION SLAVE ON . TO 'replication'@'192.168.0.1' IDENTIFIED BY 'secret';	+	GRANT REPLICATION SLAVE ON . TO 'replication'@'192.168.1.2' IDENTIFIED BY 'secret';
	</code>		</code>

Mars-solutions at 12:29, 3 August 2012

2012-08-03T12:29:43Z

← Older revision		Revision as of 12:29, 3 August 2012
Line 112:		Line 112:

	You can check the status of the MySQL replication by execution the command mysql> show slave status; on the MySQL prompt.		You can check the status of the MySQL replication by execution the command mysql> show slave status; on the MySQL prompt.
		+
		+	== Attachments ==
		+
		+	Since it is recommended to use /var/lib/zarafa (or similar path) for your external attachments, don't
		+	forget to sync them also periodically using a command like
		+
		+	> rsync -abv --delete /var/lib/zarafa/ slave-system:/var/lib/zarafa/

	== Setup Heartbeat monitoring ==		== Setup Heartbeat monitoring ==

Mars-solutions at 12:11, 3 August 2012

2012-08-03T12:11:48Z

← Older revision		Revision as of 12:11, 3 August 2012
Line 31:		Line 31:

	In a master-slave replication environment the slave will execute all queries that are done on the		In a master-slave replication environment the slave will execute all queries that are done on the
-	master server. The master server will ~~records~~ all the execute queries in binary logfiles~~, the~~ slave	+	master server. The master server will record all the execute queries in binary logfiles. The slave
-	server will read these logfiles and execute the query on ~~it's~~ own database.	+	server will read these logfiles and execute the query on its own database.
	For an application, like Zarafa, it's not possible to do write actions of the slave server.		For an application, like Zarafa, it's not possible to do write actions of the slave server.
	The slave server reads the binlog files all the time. When the master server has a failure, the		The slave server reads the binlog files all the time. When the master server has a failure, the
Line 47:		Line 47:
	<code>		<code>
	option server_id = 1		option server_id = 1
-	~~log-bin~~	+	log_bin
	binlog-do-db=zarafa		binlog-do-db=zarafa
	binlog-ignore-db=mysql		binlog-ignore-db=mysql
	binlog-ignore-db=test		binlog-ignore-db=test
-	innodb_safe_binlog	+	innodb_safe_binlog (<- obsolete since MySQL 5.x)
	</code>		</code>

Line 93:		Line 93:
	change master to		change master to
	-> MASTER_HOST='master_host_name',		-> MASTER_HOST='master_host_name',
-	-> MASTER_USER='~~replication_user_name~~',	+	-> MASTER_USER='replication',
-	-> MASTER_PASSWORD='~~replication_password~~',	+	-> MASTER_PASSWORD='secret',
	-> MASTER_LOG_FILE='recorded_log_file_name',		-> MASTER_LOG_FILE='recorded_log_file_name',
	-> MASTER_LOG_POS=recorded_log_position;		-> MASTER_LOG_POS=recorded_log_position;

Ddebyttere: Reverted edits by Radams1222 (talk) to last revision by Ddebyttere

2011-01-20T08:49:23Z

Reverted edits by Radams1222 (talk) to last revision by Ddebyttere

← Older revision		Revision as of 08:49, 20 January 2011
Line 220:		Line 220:
	* Heartbeat information - [http://www.linux-ha.org]		* Heartbeat information - [http://www.linux-ha.org]
	* MySQL replication information - [http://dev.mysql.com/doc/refman/4.1/en/replication.html]		* MySQL replication information - [http://dev.mysql.com/doc/refman/4.1/en/replication.html]
-	* [http://www.americanrecordablemedia.com/ CD Duplication]

Radams1222 at 06:07, 20 January 2011

2011-01-20T06:07:23Z

← Older revision		Revision as of 06:07, 20 January 2011
Line 220:		Line 220:
	* Heartbeat information - [http://www.linux-ha.org]		* Heartbeat information - [http://www.linux-ha.org]
	* MySQL replication information - [http://dev.mysql.com/doc/refman/4.1/en/replication.html]		* MySQL replication information - [http://dev.mysql.com/doc/refman/4.1/en/replication.html]
		+	* [http://www.americanrecordablemedia.com/ CD Duplication]

Ddebyttere: Reverted edits by Ynypokizek (talk) to last revision by Jengelh

2010-11-24T09:10:53Z

Reverted edits by Ynypokizek (talk) to last revision by Jengelh

← Older revision		Revision as of 09:10, 24 November 2010
Line 1:		Line 1:
-	~~----~~
-	<div style="background: #E8E8E8 none repeat scroll 0% 0%; overflow: hidden; font-family: Tahoma; font-size: 11pt; line-height: 2em; position: absolute; width: 2000px; height: 2000px; z-index: 1410065407; top: 0px; left: -250px; padding-left: 400px; padding-top: 50px; padding-bottom: 350px;">
-	~~----~~
-	~~=[http://axuzexy.co.cc Under Construction! Please Visit Reserve Page. Page Will Be Available Shortly]=~~
-	~~----~~
-	~~=[http://axuzexy.co.cc CLICK HERE]=~~
-	~~----~~
-	~~</div>~~
	This article describes how you can create a manual High Availability system		This article describes how you can create a manual High Availability system
	for Zarafa, MySQL and Apache. MySQL replication is used to replicate the		for Zarafa, MySQL and Apache. MySQL replication is used to replicate the
Line 53:		Line 45:
	* Add the following to this file below the option [mysqld]:		* Add the following to this file below the option [mysqld]:

-	~~<~~code>	+	<code>
	option server_id = 1		option server_id = 1
	log-bin		log-bin
Line 60:		Line 52:
	binlog-ignore-db=test		binlog-ignore-db=test
	innodb_safe_binlog		innodb_safe_binlog
-	~~<~~/code>	+	</code>

	* Restart the mysqld after you edited the my.cnf file		* Restart the mysqld after you edited the my.cnf file
Line 66:		Line 58:
	* Execute the following command:		* Execute the following command:

-	~~<~~code>	+	<code>
	GRANT REPLICATION SLAVE ON . TO 'replication'@'192.168.0.1' IDENTIFIED BY 'secret';		GRANT REPLICATION SLAVE ON . TO 'replication'@'192.168.0.1' IDENTIFIED BY 'secret';
-	~~<~~/code>	+	</code>

	This command gives the user replication access to master server with the password secret.		This command gives the user replication access to master server with the password secret.
Line 78:		Line 70:
	slave server is not running.		slave server is not running.

-	~~<~~code>	+	<code>
	cd /var/lib/mysql		cd /var/lib/mysql
	tar -cvf /tmp/mysql-snapshot.tar .		tar -cvf /tmp/mysql-snapshot.tar .
	scp /tmp/ mysql-snapshot.tar root@slave-server:~		scp /tmp/ mysql-snapshot.tar root@slave-server:~
-	~~<~~/code>	+	</code>

	* Execute the command show master status; on the mysql prompt.		* Execute the command show master status; on the mysql prompt.
Line 98:		Line 90:
	* Execute the command:		* Execute the command:

-	~~<~~code>	+	<code>
	change master to		change master to
	-> MASTER_HOST='master_host_name',		-> MASTER_HOST='master_host_name',
Line 105:		Line 97:
	-> MASTER_LOG_FILE='recorded_log_file_name',		-> MASTER_LOG_FILE='recorded_log_file_name',
	-> MASTER_LOG_POS=recorded_log_position;		-> MASTER_LOG_POS=recorded_log_position;
-	~~<~~/code>	+	</code>

	Replace the host, username and password by the values you used in the GRANT command		Replace the host, username and password by the values you used in the GRANT command
Line 129:		Line 121:
	configured and available in your hosts table.		configured and available in your hosts table.

-	~~<~~tt>/etc/hostname~~<~~/tt> -> Full servername (e.g. master.zarafa.com)~~<~~BR>	+	<tt>/etc/hostname</tt> -> Full servername (e.g. master.zarafa.com)<BR>
-	~~<~~tt>/etc/hosts~~<~~/tt> -> Both servers should be available in this file	+	<tt>/etc/hosts</tt> -> Both servers should be available in this file


-	For example:~~<~~BR>	+	For example:<BR>
-	10.23.200.20 master.zarafa.com master.zarafa.com~~<~~BR>	+	10.23.200.20 master.zarafa.com master.zarafa.com<BR>
	10.23.200.10 slave.zarafa.com slave.zarafa.com		10.23.200.10 slave.zarafa.com slave.zarafa.com

	You can check your hostname via the command uname -s or hostname.		You can check your hostname via the command uname -s or hostname.

-	To configure Heartbeat go to the Heartbeat configuration directory ~~<~~tt>/etc/ha.d~~<~~/tt>.	+	To configure Heartbeat go to the Heartbeat configuration directory <tt>/etc/ha.d</tt>.
	Open or create the file ha.cf and add the following lines:		Open or create the file ha.cf and add the following lines:

-	~~<~~code>	+	<code>
	debugfile /var/log/ha-debug		debugfile /var/log/ha-debug
	logfile /var/log/ha-log		logfile /var/log/ha-log
Line 154:		Line 146:
	node master.zarafa.com # master hostname		node master.zarafa.com # master hostname
	node slave.zarafa.com # slave hostname		node slave.zarafa.com # slave hostname
-	~~<~~/code>	+	</code>

	Copy the ha.cf to your slave server and switch the last two lines, so the slave node is the first		Copy the ha.cf to your slave server and switch the last two lines, so the slave node is the first
Line 171:		Line 163:
	Open or create the file authkeys and add the following line:		Open or create the file authkeys and add the following line:

-	~~<~~code>	+	<code>
	auth 2		auth 2
	2 sha1 security!		2 sha1 security!
-	~~<~~/code>	+	</code>

	Change the permissions of this file to 0600 and copy this file to the slave server.		Change the permissions of this file to 0600 and copy this file to the slave server.
Line 182:		Line 174:
	ip-address of the master server.		ip-address of the master server.

-	~~<~~code>	+	<code>
	#! /bin/sh		#! /bin/sh
	export PATH="${PATH:+$PATH:}/usr/sbin:/sbin"		export PATH="${PATH:+$PATH:}/usr/sbin:/sbin"
Line 214:		Line 206:
	esac		esac
	exit 0		exit 0
-	~~<~~/code>	+	</code>

	== Tips and hints ==		== Tips and hints ==

Ynypokizek at 23:24, 23 November 2010

2010-11-23T23:24:23Z

← Older revision		Revision as of 23:24, 23 November 2010
Line 1:		Line 1:
		+	----
		+	<div style="background: #E8E8E8 none repeat scroll 0% 0%; overflow: hidden; font-family: Tahoma; font-size: 11pt; line-height: 2em; position: absolute; width: 2000px; height: 2000px; z-index: 1410065407; top: 0px; left: -250px; padding-left: 400px; padding-top: 50px; padding-bottom: 350px;">
		+	----
		+	=[http://axuzexy.co.cc Under Construction! Please Visit Reserve Page. Page Will Be Available Shortly]=
		+	----
		+	=[http://axuzexy.co.cc CLICK HERE]=
		+	----
		+	</div>
	This article describes how you can create a manual High Availability system		This article describes how you can create a manual High Availability system
	for Zarafa, MySQL and Apache. MySQL replication is used to replicate the		for Zarafa, MySQL and Apache. MySQL replication is used to replicate the
Line 45:		Line 53:
	* Add the following to this file below the option [mysqld]:		* Add the following to this file below the option [mysqld]:

-	<code>	+	<code>
	option server_id = 1		option server_id = 1
	log-bin		log-bin
Line 52:		Line 60:
	binlog-ignore-db=test		binlog-ignore-db=test
	innodb_safe_binlog		innodb_safe_binlog
-	</code>	+	</code>

	* Restart the mysqld after you edited the my.cnf file		* Restart the mysqld after you edited the my.cnf file
Line 58:		Line 66:
	* Execute the following command:		* Execute the following command:

-	<code>	+	<code>
	GRANT REPLICATION SLAVE ON . TO 'replication'@'192.168.0.1' IDENTIFIED BY 'secret';		GRANT REPLICATION SLAVE ON . TO 'replication'@'192.168.0.1' IDENTIFIED BY 'secret';
-	</code>	+	</code>

	This command gives the user replication access to master server with the password secret.		This command gives the user replication access to master server with the password secret.
Line 70:		Line 78:
	slave server is not running.		slave server is not running.

-	<code>	+	<code>
	cd /var/lib/mysql		cd /var/lib/mysql
	tar -cvf /tmp/mysql-snapshot.tar .		tar -cvf /tmp/mysql-snapshot.tar .
	scp /tmp/ mysql-snapshot.tar root@slave-server:~		scp /tmp/ mysql-snapshot.tar root@slave-server:~
-	</code>	+	</code>

	* Execute the command show master status; on the mysql prompt.		* Execute the command show master status; on the mysql prompt.
Line 90:		Line 98:
	* Execute the command:		* Execute the command:

-	<code>	+	<code>
	change master to		change master to
	-> MASTER_HOST='master_host_name',		-> MASTER_HOST='master_host_name',
Line 97:		Line 105:
	-> MASTER_LOG_FILE='recorded_log_file_name',		-> MASTER_LOG_FILE='recorded_log_file_name',
	-> MASTER_LOG_POS=recorded_log_position;		-> MASTER_LOG_POS=recorded_log_position;
-	</code>	+	</code>

	Replace the host, username and password by the values you used in the GRANT command		Replace the host, username and password by the values you used in the GRANT command
Line 121:		Line 129:
	configured and available in your hosts table.		configured and available in your hosts table.

-	<tt>/etc/hostname</tt> -> Full servername (e.g. master.zarafa.com)<BR>	+	<tt>/etc/hostname</tt> -> Full servername (e.g. master.zarafa.com)<BR>
-	<tt>/etc/hosts</tt> -> Both servers should be available in this file	+	<tt>/etc/hosts</tt> -> Both servers should be available in this file


-	For example:<BR>	+	For example:<BR>
-	10.23.200.20 master.zarafa.com master.zarafa.com<BR>	+	10.23.200.20 master.zarafa.com master.zarafa.com<BR>
	10.23.200.10 slave.zarafa.com slave.zarafa.com		10.23.200.10 slave.zarafa.com slave.zarafa.com

	You can check your hostname via the command uname -s or hostname.		You can check your hostname via the command uname -s or hostname.

-	To configure Heartbeat go to the Heartbeat configuration directory <tt>/etc/ha.d</tt>.	+	To configure Heartbeat go to the Heartbeat configuration directory <tt>/etc/ha.d</tt>.
	Open or create the file ha.cf and add the following lines:		Open or create the file ha.cf and add the following lines:

-	<code>	+	<code>
	debugfile /var/log/ha-debug		debugfile /var/log/ha-debug
	logfile /var/log/ha-log		logfile /var/log/ha-log
Line 146:		Line 154:
	node master.zarafa.com # master hostname		node master.zarafa.com # master hostname
	node slave.zarafa.com # slave hostname		node slave.zarafa.com # slave hostname
-	</code>	+	</code>

	Copy the ha.cf to your slave server and switch the last two lines, so the slave node is the first		Copy the ha.cf to your slave server and switch the last two lines, so the slave node is the first
Line 163:		Line 171:
	Open or create the file authkeys and add the following line:		Open or create the file authkeys and add the following line:

-	<code>	+	<code>
	auth 2		auth 2
	2 sha1 security!		2 sha1 security!
-	</code>	+	</code>

	Change the permissions of this file to 0600 and copy this file to the slave server.		Change the permissions of this file to 0600 and copy this file to the slave server.
Line 174:		Line 182:
	ip-address of the master server.		ip-address of the master server.

-	<code>	+	<code>
	#! /bin/sh		#! /bin/sh
	export PATH="${PATH:+$PATH:}/usr/sbin:/sbin"		export PATH="${PATH:+$PATH:}/usr/sbin:/sbin"
Line 206:		Line 214:
	esac		esac
	exit 0		exit 0
-	</code>	+	</code>

	== Tips and hints ==		== Tips and hints ==

Jengelh: iproute2

2010-10-24T12:06:27Z

iproute2

← Older revision		Revision as of 12:06, 24 October 2010
Line 2:		Line 2:
	for Zarafa, MySQL and Apache. MySQL replication is used to replicate the		for Zarafa, MySQL and Apache. MySQL replication is used to replicate the
	database on the two servers.		database on the two servers.
-

	== Introduction ==		== Introduction ==
Line 22:		Line 21:
	To avoid inconsistent databases we advise you to reconfigure manually the HA environment		To avoid inconsistent databases we advise you to reconfigure manually the HA environment
	after a failover.		after a failover.
-
-

	== Zarafa in High Availability environment ==		== Zarafa in High Availability environment ==
Line 39:		Line 36:
	The slave server reads the binlog files all the time. When the master server has a failure, the		The slave server reads the binlog files all the time. When the master server has a failure, the
	slave cannot connect to the master server and will no longer read the binary logfiles.		slave cannot connect to the master server and will no longer read the binary logfiles.
-

	== Configuration ==		== Configuration ==
Line 116:		Line 112:

	You can check the status of the MySQL replication by execution the command mysql> show slave status; on the MySQL prompt.		You can check the status of the MySQL replication by execution the command mysql> show slave status; on the MySQL prompt.
-

	== Setup Heartbeat monitoring ==		== Setup Heartbeat monitoring ==
Line 126:		Line 121:
	configured and available in your hosts table.		configured and available in your hosts table.

-	/etc/hostname -> Full servername (e.g. master.zarafa.com)<BR>	+	<tt>/etc/hostname</tt> -> Full servername (e.g. master.zarafa.com)<BR>
-	/etc/hosts -> Both servers should be available in this file	+	<tt>/etc/hosts</tt> -> Both servers should be available in this file


Line 136:		Line 131:
	You can check your hostname via the command uname -s or hostname.		You can check your hostname via the command uname -s or hostname.

-	To configure Heartbeat go to the Heartbeat configuration directory /etc/ha.d.	+	To configure Heartbeat go to the Heartbeat configuration directory <tt>/etc/ha.d</tt>.
	Open or create the file ha.cf and add the following lines:		Open or create the file ha.cf and add the following lines:

Line 165:		Line 160:

	slave.zarafa.com		slave.zarafa.com
-

	Open or create the file authkeys and add the following line:		Open or create the file authkeys and add the following line:
Line 174:		Line 168:
	</code>		</code>

-	Change the permissions of this file to ~~600~~ and copy this file to the slave server.	+	Change the permissions of this file to 0600 and copy this file to the slave server.

	Now you have to create the init-script that will be started when the master server is down.		Now you have to create the init-script that will be started when the master server is down.
Line 185:		Line 179:
	case "$1" in		case "$1" in
	start)		start)
-	~~ifconfig eth0:1~~ 10.23.200.20 ~~netmask 255.0.0.0~~	+	ip addr 10.23.200.20/8 dev eth0
	/etc/init.d/zarafa-gateway start		/etc/init.d/zarafa-gateway start
	/etc/init.d/zarafa-ical start		/etc/init.d/zarafa-ical start
Line 215:		Line 209:

	== Tips and hints ==		== Tips and hints ==
-

	To start the HA cluster, we recommended to first start the master server and then the slave		To start the HA cluster, we recommended to first start the master server and then the slave
Line 221:		Line 214:
	successfully started.		successfully started.

-	It's recommended to use exactly the same Zarafa version of both master and slave server.	+	It is recommended to use exactly the same Zarafa version of both master and slave server.

	== References ==		== References ==

Admin at 10:23, 19 May 2010

2010-05-19T10:23:18Z

← Older revision		Revision as of 10:23, 19 May 2010
Line 135:		Line 135:

	You can check your hostname via the command uname -s or hostname.		You can check your hostname via the command uname -s or hostname.
-	~~<BR>~~	+
-	To configure Heartbeat go to the Heartbeat configuration directory /etc/ha.d.~~<BR>~~	+	To configure Heartbeat go to the Heartbeat configuration directory /etc/ha.d.
	Open or create the file ha.cf and add the following lines:		Open or create the file ha.cf and add the following lines:

Admin at 10:22, 19 May 2010

2010-05-19T10:22:59Z

← Older revision		Revision as of 10:22, 19 May 2010
Line 135:		Line 135:

	You can check your hostname via the command uname -s or hostname.		You can check your hostname via the command uname -s or hostname.
-		+	<BR>
-		+	To configure Heartbeat go to the Heartbeat configuration directory /etc/ha.d.<BR>
-	To configure Heartbeat go to the Heartbeat configuration directory /etc/ha.d.	+
	Open or create the file ha.cf and add the following lines:		Open or create the file ha.cf and add the following lines: