<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:atom="http://www.w3.org/2005/Atom">
	<channel>
		<title>More Misinformation About Dedupe</title>
		<description>Discuss More Misinformation About Dedupe</description>
		<link>http://www.backupcentral.com/mr-backup-blog-mainmenu-47/13-mr-backup-blog/192-more-misinformation-about-dedupe.html</link>
		<lastBuildDate>Fri, 10 Feb 2012 11:16:40 +0000</lastBuildDate>
		<generator>JComments</generator>
		<atom:link href="http://www.backupcentral.com/component/jcomments/feed/com_content/192/10.html" rel="self" type="application/rss+xml" />
		<item>
			<title>Simple test</title>
			<link>http://www.backupcentral.com/mr-backup-blog-mainmenu-47/13-mr-backup-blog/192-more-misinformation-about-dedupe.html#comment-341</link>
			<description><![CDATA[I always use a simple test with the sales people: If I say " I want to do X", and you don't ask me at least 5 questions before you suggest something, I'm going somewhere else. And only 1 of those 5 gets to be about budget. I never trust single-answer types. Your solution may be perfect for me, but if you don't have any other answers I just can't trust your motives.]]></description>
			<dc:creator>Tom Burrell</dc:creator>
			<pubDate>Fri, 29 Aug 2008 12:18:09 +0000</pubDate>
			<guid>http://www.backupcentral.com/mr-backup-blog-mainmenu-47/13-mr-backup-blog/192-more-misinformation-about-dedupe.html#comment-341</guid>
		</item>
		<item>
			<title>Not sure DD is behind this</title>
			<link>http://www.backupcentral.com/mr-backup-blog-mainmenu-47/13-mr-backup-blog/192-more-misinformation-about-dedupe.html#comment-340</link>
			<description><![CDATA[I'm pretty sure DD pays George, and obviously George is behind it, but I doubt that DD instructed George to write this junk. Although some of their sales reps have been liable to say just about anything to win a deal, the marketing folks that would be paying George don't seem the type. They've always positioned inline as the best way. I would expect them to do so; it's the way they do it. I just don't like it when an "independent" author tells only one side of the story. There are advantages and disadvantages to both approaches, and an independent article that's trying to cover the subject should cover both.]]></description>
			<dc:creator>W. Curtis Preston</dc:creator>
			<pubDate>Thu, 28 Aug 2008 16:27:54 +0000</pubDate>
			<guid>http://www.backupcentral.com/mr-backup-blog-mainmenu-47/13-mr-backup-blog/192-more-misinformation-about-dedupe.html#comment-340</guid>
		</item>
		<item>
			<title>Give us a break DD</title>
			<link>http://www.backupcentral.com/mr-backup-blog-mainmenu-47/13-mr-backup-blog/192-more-misinformation-about-dedupe.html#comment-339</link>
			<description><![CDATA[I think it is interesting how DD is positioning themselves in the de-dupe card game now that other players have arrived at the final table. QTM, EMC, and others have DD a bit concerned and so DD must spread the word that inline is the best and post-process is the worst. After all, they have been doing it the longest and are the best at it. Aren't they? It is just too bad that so called industry experts from Byte and Switch are spreading FUD for them. Let DD do their own dirty work. They are very good at it, trust me. It is sad to think that some poor backup admin somewhere is going to read that and be totally convinced that inline is the only way to go beacause some "expert" said so in some article somewhere. "But Curtis, How do I choose the right de-dupe solution for my business with all of this mis-information?" Simple, do your homework and TEST the product with YOUR data. After all, it still comes down to "How big is it? How fast is it? How much does it cost?" Personally speaking, I like the flexibility option when it comes to de-dupe.]]></description>
			<dc:creator>kristoffae</dc:creator>
			<pubDate>Thu, 28 Aug 2008 15:36:13 +0000</pubDate>
			<guid>http://www.backupcentral.com/mr-backup-blog-mainmenu-47/13-mr-backup-blog/192-more-misinformation-about-dedupe.html#comment-339</guid>
		</item>
	</channel>
</rss>

