<?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/"
	xmlns:itunes="http://www.itunes.com/dtds/podcast-1.0.dtd"
	xmlns:media="http://search.yahoo.com/mrss/"
	>
<channel>
	<title>Comments on: Not perfect, but good enough</title>
	<atom:link href="http://itknowledgeexchange.techtarget.com/storage-soup/not-perfect-but-good-enough/feed/" rel="self" type="application/rss+xml" />
	<link>http://itknowledgeexchange.techtarget.com/storage-soup/not-perfect-but-good-enough/</link>
	<description>A SearchStorage.com blog.</description>
	<lastBuildDate>Tue, 14 May 2013 18:21:36 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	
	<item>
		<title>By: Chuck Hollis</title>
		<link>http://itknowledgeexchange.techtarget.com/storage-soup/not-perfect-but-good-enough/#comment-6759</link>
		<dc:creator>Chuck Hollis</dc:creator>
		<pubDate>Fri, 20 Jul 2007 18:58:16 +0000</pubDate>
		<guid isPermaLink="false">http://storage.blogs.techtarget.com/2007/07/20/not-perfect-but-good-enough/#comment-6759</guid>
		<description><![CDATA[Hi Jerome -- looking forward to your upcoming comparo on async replication!

My only suggestion would that -- in my view -- characterizing async replication as &quot;good enough&quot; probably isn&#039;t doing it justice.

For extended distances, it&#039;s the only practical option: sync replication just doesn&#039;t work.  And in high-update environments, it can offer better performance (not to mention lower line cost) than sync alternatives.

And, if you consider remote CDP as a form of async (many people do), one could argue that it offers superior functionality as compared to sync alternatives.

Again, looking forward to your comparo!]]></description>
		<content:encoded><![CDATA[<p>Hi Jerome &#8212; looking forward to your upcoming comparo on async replication!</p>
<p>My only suggestion would that &#8212; in my view &#8212; characterizing async replication as &#8220;good enough&#8221; probably isn&#8217;t doing it justice.</p>
<p>For extended distances, it&#8217;s the only practical option: sync replication just doesn&#8217;t work.  And in high-update environments, it can offer better performance (not to mention lower line cost) than sync alternatives.</p>
<p>And, if you consider remote CDP as a form of async (many people do), one could argue that it offers superior functionality as compared to sync alternatives.</p>
<p>Again, looking forward to your comparo!</p>
]]></content:encoded>
	</item>
</channel>
</rss>
