<?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: iSCSI Scavengers &#8211; The Vultures Circle and The Hyenas Pick at Scraps</title>
	<atom:link href="http://thesantechnologist.com/?feed=rss2&#038;p=148" rel="self" type="application/rss+xml" />
	<link>http://thesantechnologist.com/?p=148</link>
	<description>A Storage Technology Blog by a Technologist</description>
	<lastBuildDate>Mon, 26 Oct 2009 04:20:58 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.1</generator>
	<item>
		<title>By: John</title>
		<link>http://thesantechnologist.com/?p=148&#038;cpage=1#comment-336</link>
		<dc:creator>John</dc:creator>
		<pubDate>Wed, 08 Oct 2008 21:40:24 +0000</pubDate>
		<guid isPermaLink="false">http://thesantechnologist.com/?p=148#comment-336</guid>
		<description>It&#039;s a joke that DataCore thinks they are going to pick off what is almost a purely HP channel, and even a bigger joke that they think they have a comparative technology. The LeftHand channel program is going to get better, not worse with HP.

Some DataCore technical facts:

DataCore runs on Windows as an application, whereas LeftHand’s NSMs are integrated and thoroughly tested storage systems. Microsoft has certified LeftHand as a storage solution, but not DataCore; they are only certified as an application running on Windows. 

DataCore is also struggling to get certified by VMware and other virtualization software companies. They do little if any integration with the hardware, which means customers have to mange the hardware with the hardware supplier’s management, separately from the DataCore SAN software management, which introduces the complexity of 2 points of management. 

Since they don’t do complete integration and testing with the underlying server hardware, there are often unknown incompatibilities or problems with things like disk controller firmware. If you think about it, the customers are actually doing the testing for them, which is really scary. 

DataCore also achieves their performance by using the server DRAM as write cache. Imagine the Windows O/S hanging due to a bad driver, memory being corrupted from the DataCore application, etc., etc. These and many other similar circumstances can cause complete data loss. 

Due to envy of LeftHand and other scale-out architectures, DataCore started marketing “N+1 Grid Scalability”, which is a misnomer. It is nothing more than mirroring between 2 DataCore servers. From a performance scalability standpoint, multiple DataCore servers can’t read and write to the same volume, which limits the performance of any given volume to a single server’s I/O capability. Data protection and fault tolerance is also entirely dependent on the underlying storage connected to the DataCore server.

If you consider DataCore’s technical shortfalls and company history, this may not be the ideal partner you want to replace LeftHand with.</description>
		<content:encoded><![CDATA[<p>It&#8217;s a joke that DataCore thinks they are going to pick off what is almost a purely HP channel, and even a bigger joke that they think they have a comparative technology. The LeftHand channel program is going to get better, not worse with HP.</p>
<p>Some DataCore technical facts:</p>
<p>DataCore runs on Windows as an application, whereas LeftHand’s NSMs are integrated and thoroughly tested storage systems. Microsoft has certified LeftHand as a storage solution, but not DataCore; they are only certified as an application running on Windows. </p>
<p>DataCore is also struggling to get certified by VMware and other virtualization software companies. They do little if any integration with the hardware, which means customers have to mange the hardware with the hardware supplier’s management, separately from the DataCore SAN software management, which introduces the complexity of 2 points of management. </p>
<p>Since they don’t do complete integration and testing with the underlying server hardware, there are often unknown incompatibilities or problems with things like disk controller firmware. If you think about it, the customers are actually doing the testing for them, which is really scary. </p>
<p>DataCore also achieves their performance by using the server DRAM as write cache. Imagine the Windows O/S hanging due to a bad driver, memory being corrupted from the DataCore application, etc., etc. These and many other similar circumstances can cause complete data loss. </p>
<p>Due to envy of LeftHand and other scale-out architectures, DataCore started marketing “N+1 Grid Scalability”, which is a misnomer. It is nothing more than mirroring between 2 DataCore servers. From a performance scalability standpoint, multiple DataCore servers can’t read and write to the same volume, which limits the performance of any given volume to a single server’s I/O capability. Data protection and fault tolerance is also entirely dependent on the underlying storage connected to the DataCore server.</p>
<p>If you consider DataCore’s technical shortfalls and company history, this may not be the ideal partner you want to replace LeftHand with.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
