<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Set up MySQL database replication</title>
	<atom:link href="http://www.ghacks.net/2009/04/09/set-up-mysql-database-replication/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.ghacks.net/2009/04/09/set-up-mysql-database-replication/</link>
	<description>A technology blog covering software, mobile phones, gadgets, security, the Internet and other relevant areas.</description>
	<lastBuildDate>Wed, 25 Nov 2009 10:02:41 -0600</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.6</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Pier-Olivier P. Côté</title>
		<link>http://www.ghacks.net/2009/04/09/set-up-mysql-database-replication/#comment-719031</link>
		<dc:creator>Pier-Olivier P. Côté</dc:creator>
		<pubDate>Fri, 10 Apr 2009 21:58:33 +0000</pubDate>
		<guid isPermaLink="false">http://www.ghacks.net/?p=11853#comment-719031</guid>
		<description>DATABASE REPLICATION IS NOT A BACKUP, you should always have a backup policy although replication is usefull it doesn&#039;t cover everything and I think its article mislead people at the beginning:

&quot;But backing up a database and being able to use that backup depends upon the back up being always up to date. There is a method that ensures you will always have an up to date backup.&quot;

Replication is not a backup policy. A mistyped DELETE statement will be replicated on the slave too, and you could end up with two, perfectly synchronized, empty databases. Replication can help protect against hardware failure though.  (http://www.databasejournal.com/features/mysql/article.php/3355201/Database-Replication-in-MySQL.htm)

You&#039;ve been warned.</description>
		<content:encoded><![CDATA[<p>DATABASE REPLICATION IS NOT A BACKUP, you should always have a backup policy although replication is usefull it doesn&#8217;t cover everything and I think its article mislead people at the beginning:</p>
<p>&#8220;But backing up a database and being able to use that backup depends upon the back up being always up to date. There is a method that ensures you will always have an up to date backup.&#8221;</p>
<p>Replication is not a backup policy. A mistyped DELETE statement will be replicated on the slave too, and you could end up with two, perfectly synchronized, empty databases. Replication can help protect against hardware failure though.  (<a href="http://www.databasejournal.com/features/mysql/article.php/3355201/Database-Replication-in-MySQL.htm" rel="nofollow">http://www.databasejournal.com/features/mysql/article.php/3355201/Database-Replication-in-MySQL.htm</a>)</p>
<p>You&#8217;ve been warned.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
