<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	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/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>FlexRAID</title>
	<atom:link href="http://flexraid.com/feed/" rel="self" type="application/rss+xml" />
	<link>http://flexraid.com</link>
	<description>Rethinking storage data management</description>
	<lastBuildDate>Tue, 16 Apr 2013 20:28:28 +0000</lastBuildDate>
	<language>en-US</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.5</generator>
		<item>
		<title>Duplication is dead!</title>
		<link>http://flexraid.com/duplication-is-dead/?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=duplication-is-dead</link>
		<comments>http://flexraid.com/duplication-is-dead/#comments</comments>
		<pubDate>Mon, 21 May 2012 18:33:58 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[Blogging]]></category>

		<guid isPermaLink="false">http://homepage.flexraid.com/?p=533</guid>
		<description><![CDATA[Duplication is primitive, archaic, dépassé for large storage. For the longest time data duplication through mirroring or other schemes was regarded as the safest form of redundant data protection. What reenforced that view was the fact that traditional RAID systems using parity based protection are an all-or-nothing [...]]]></description>
				<content:encoded><![CDATA[<h3>Duplication is primitive, archaic, dépassé for large storage.</h3>
<p>For the longest time data duplication through mirroring or other schemes was regarded as the safest form of redundant data protection. What reenforced that view was the fact that traditional RAID systems using parity based protection are an <strong>all-or-nothing</strong> type of deal.<br />
That is, with traditional parity based RAID systems, if the said systems are unable sustain and recover from a particular failure level then <strong>all data is lost.</strong> This chronically negative aspect of traditional RAID systems has lead to the doctrine of &#8220;RAID is not backup&#8221;.</p>
<h3>Mirroring is simple.</h3>
<p>Here is an example of a mirroring system:<br />
<a href="http://flexraid.com/wp-content/uploads/2012/05/DataProtection_02_RAID1.jpg" rel="wp-prettyPhoto[533]"><img src="/wp-content/uploads/2012/05/DataProtection_02_RAID1-300x249.jpg" alt="" title="DataProtection_02_RAID1" width="300" height="249" class="alignnone size-medium wp-image-537" /></a></p>
<p>And here is an example of a parity based system:<br />
<a href="http://flexraid.com/wp-content/uploads/2012/05/DataProtection_02_RAID5.jpg" rel="wp-prettyPhoto[533]"><img src="/wp-content/uploads/2012/05/DataProtection_02_RAID5.jpg" alt="" title="DataProtection_02_RAID5" width="700" height="275" class="alignnone size-full wp-image-541" /></a></p>
<p>As you can see, it is much simpler to implement a mirroring scheme than a parity one. Mirroring involves simply copying the data to two disks where parity based schemes involve algorithms for computing the parity and for where to write the data and parity.</p>
<h3>Looking beyond simplicity&#8230; understanding the importance of tolerance level</h3>
<p>Yes, mirroring is simple an inherently easier to make robust. However, parity based systems are just as robust when properly implemented. If all schemes have the same robustness when properly implemented, then we need to focus on the real differentiators. The biggest factor when it comes to data protection is tolerance level, which is the number of failure the system can tolerate and successfully recover from.</p>
<h3>Mirroring has a tolerance level of only 1</h3>
<p>The typical mirroring system can only tolerate a single failure as there typically only exist two copies of the data. Lose both copies and you have lost it all.</p>
<h3>Mirroring is expensive</h3>
<p>Mirroring requires double the amount of space used to store the data. This turns, for instance, a $1k system into a $2k system, and things add up really quick.</p>
<h3>Evolution in data protection</h3>
<p>Parity based schemes can be extremely cost efficient. For instance, if you have a million 2TB drives, it only take one additional 2TB drive to provide protection to all those 1 million drives.<br />
For all the benefits that parity based schemes provide, their core drawback has always been and will remain a hard pill to swallow: <strong>you lose all your data if things go wrong</strong>.</p>
<p><a href="http://flexraid.com/wp-content/uploads/2012/05/fl110h_w_sh.png" rel="wp-prettyPhoto[533]"><img src="/wp-content/uploads/2012/05/fl110h_w_sh.png" alt="" title="fl110h_w_sh" width="196" height="110" class="alignnone size-full wp-image-559" /></a><br />
We have evolved, and now comes FlexRAID to the rescue.<br />
FlexRAID gives you the benefits of parity based schemes without the risk of losing all of one&#8217;s data unless you lose every single one of your drives.<br />
FlexRAID allows you to choose and pick your protection level going from 1 to infinity.<br />
That&#8217;s right, your protection level under FlexRAID is limited only by your choice and by your own hardware.</p>
<h3>Conclusion</h3>
<p>Do no waste your time with any product that relies on duplication as a protection scheme for your precious data.<br />
Great technological progresses have been made and you should no longer be doing things the hard and expensive way.<br />
When it comes to data protection, do it the FlexRAID way. <img src='http://flexraid.com/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> </p>
]]></content:encoded>
			<wfw:commentRss>http://flexraid.com/duplication-is-dead/feed/</wfw:commentRss>
		<slash:comments>13</slash:comments>
		</item>
	</channel>
</rss>
