<?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: Data Domain Brags About File Locks</title>
	<atom:link href="http://www.drunkendata.com/?feed=rss2&#038;p=1798" rel="self" type="application/rss+xml" />
	<link>http://www.drunkendata.com/?p=1798</link>
	<description>A blog for storage administrators and data managers.</description>
	<lastBuildDate>Fri, 23 Jul 2010 14:27:46 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.1</generator>
	<item>
		<title>By: Administrator</title>
		<link>http://www.drunkendata.com/?p=1798&#038;cpage=1#comment-18302</link>
		<dc:creator>Administrator</dc:creator>
		<pubDate>Thu, 03 Jul 2008 14:39:39 +0000</pubDate>
		<guid isPermaLink="false">http://www.drunkendata.com/?p=1798#comment-18302</guid>
		<description>Thanks for the response, Jered. I think you may have gotten Permabit a discriminator for its product:

&quot;With every sale, Permabit promises to provide an expert witness should any litigation arise around the use of our technology.&quot;  Add it to your sales contract and its golden.

Your whitepaper on compliance would make an interesting read.  How does it measure up to EMC&#039;s paid for whitepaper saying that Centera is compliant.  As previously blogged here, there is a page and a half disclaimer by the company that wrote that one saying that the paper does not replace competent legal counsel and that your experience with the courts may be quite different than what is represented in the paper.

By the way, I agree that RAID 5 alone is not sufficient to protect data in the manner required by many regs.

Happy 4th to you and yours.</description>
		<content:encoded><![CDATA[<p>Thanks for the response, Jered. I think you may have gotten Permabit a discriminator for its product:</p>
<p>&#8220;With every sale, Permabit promises to provide an expert witness should any litigation arise around the use of our technology.&#8221;  Add it to your sales contract and its golden.</p>
<p>Your whitepaper on compliance would make an interesting read.  How does it measure up to EMC&#8217;s paid for whitepaper saying that Centera is compliant.  As previously blogged here, there is a page and a half disclaimer by the company that wrote that one saying that the paper does not replace competent legal counsel and that your experience with the courts may be quite different than what is represented in the paper.</p>
<p>By the way, I agree that RAID 5 alone is not sufficient to protect data in the manner required by many regs.</p>
<p>Happy 4th to you and yours.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jered</title>
		<link>http://www.drunkendata.com/?p=1798&#038;cpage=1#comment-18301</link>
		<dc:creator>Jered</dc:creator>
		<pubDate>Thu, 03 Jul 2008 13:50:10 +0000</pubDate>
		<guid isPermaLink="false">http://www.drunkendata.com/?p=1798#comment-18301</guid>
		<description>Jon,

[quote] Deduplication has NOT yet been subjected to the acid test of litigation.  Nor has lossy compression to my knowledge. [/quote]

Permabit&#039;s systems are used in the field for the archive of critical data, including data subject to the SEC 17a-4 rule.  While I don&#039;t know if any specific cases, I&#039;m quite certain data stored on our storage, incorporating deduplication technology, has been subject to litigation discovery.  The integrity of the deduplicated data has never been called into question.

Also, deduplication is more along the lines of lossless, not lossy, compression.   But, even for lossy compression, audio recorded onto portable devices that record in the MP3 format has definitely been used without problem in court.

[quote] Does Permabit provide any assurances to its customers that legal hassles  will not result from deduplicating files? [/quote]

For our customers with SEC 17a-4 requirements, we assist in the process of filing a letter describing the archiving system and technologies; in doing so the customer can receive a &quot;no action&quot; letter indicating that the SEC does not believe they are in violation of the rules.  (This is not quite the same as saying they are not in violation of the rules, a matter on which the SEC does not opine.)

In the event of litigation, I would be happy to be an expert witness to explain the integrity of the recording process.  We also have an independent report from Compliant Systems Consulting LLC, finding that Permabit Enterprise Archive satisfies regulatory compliance requirements.

[quote] Call it FUD, but I wonder if this is simply just a discussion that you would prefer not to be had at this juncture. I welcome a legal opinion on this matter [/quote]

You could get an attorney&#039;s opinion, if you really value that.  You could probably get contradictory ones for that matter.  What does matter is if deduplication is even considered an area to try to attack in a legal discovery case, and evidence is that it is not.

There are far more dangerous areas we should be concerned about if we&#039;re looking for legal opinions.  For example, should it be acceptable for companies to use RAID 5 to protect important data, given how vulnerable that is to data loss with modern, high-capacity drives?

[quote] If the question exists, and to many of my financial clients it most certainly does, why not get it out in the open and address it? [/quote]

Consider it addressed. :-)  Have a great Fourth of July!

Regards,
Jered Floyd
CTO, Permabit Technology Corp.</description>
		<content:encoded><![CDATA[<p>Jon,</p>
<p>[quote] Deduplication has NOT yet been subjected to the acid test of litigation.  Nor has lossy compression to my knowledge. [/quote]</p>
<p>Permabit&#8217;s systems are used in the field for the archive of critical data, including data subject to the SEC 17a-4 rule.  While I don&#8217;t know if any specific cases, I&#8217;m quite certain data stored on our storage, incorporating deduplication technology, has been subject to litigation discovery.  The integrity of the deduplicated data has never been called into question.</p>
<p>Also, deduplication is more along the lines of lossless, not lossy, compression.   But, even for lossy compression, audio recorded onto portable devices that record in the MP3 format has definitely been used without problem in court.</p>
<p>[quote] Does Permabit provide any assurances to its customers that legal hassles  will not result from deduplicating files? [/quote]</p>
<p>For our customers with SEC 17a-4 requirements, we assist in the process of filing a letter describing the archiving system and technologies; in doing so the customer can receive a &#8220;no action&#8221; letter indicating that the SEC does not believe they are in violation of the rules.  (This is not quite the same as saying they are not in violation of the rules, a matter on which the SEC does not opine.)</p>
<p>In the event of litigation, I would be happy to be an expert witness to explain the integrity of the recording process.  We also have an independent report from Compliant Systems Consulting LLC, finding that Permabit Enterprise Archive satisfies regulatory compliance requirements.</p>
<p>[quote] Call it FUD, but I wonder if this is simply just a discussion that you would prefer not to be had at this juncture. I welcome a legal opinion on this matter [/quote]</p>
<p>You could get an attorney&#8217;s opinion, if you really value that.  You could probably get contradictory ones for that matter.  What does matter is if deduplication is even considered an area to try to attack in a legal discovery case, and evidence is that it is not.</p>
<p>There are far more dangerous areas we should be concerned about if we&#8217;re looking for legal opinions.  For example, should it be acceptable for companies to use RAID 5 to protect important data, given how vulnerable that is to data loss with modern, high-capacity drives?</p>
<p>[quote] If the question exists, and to many of my financial clients it most certainly does, why not get it out in the open and address it? [/quote]</p>
<p>Consider it addressed. <img src='http://www.drunkendata.com/wp-includes/images/smilies/icon_smile.gif' alt=':-)' class='wp-smiley' />   Have a great Fourth of July!</p>
<p>Regards,<br />
Jered Floyd<br />
CTO, Permabit Technology Corp.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Administrator</title>
		<link>http://www.drunkendata.com/?p=1798&#038;cpage=1#comment-18300</link>
		<dc:creator>Administrator</dc:creator>
		<pubDate>Wed, 02 Jul 2008 22:53:24 +0000</pubDate>
		<guid isPermaLink="false">http://www.drunkendata.com/?p=1798#comment-18300</guid>
		<description>Hi Jered,

I am not disagreeing with any of your points from a technical standpoint. I don&#039;t think that storage admins should decide what is important from a business perspective, deleting as they see fit electronic files of the company. But, you have made my point as well. Letting the IT guy field technology like de-dupe and expose all files to it, without a full understanding of the legal ramifications of doing so, is equally foolhardy.

Deduplication has NOT yet been subjected to the acid test of litigation. Nor has lossy compression to my knowledge.

What you claim about dedupe may be 100% true technically. That doesn&#039;t have anything to do with the law, however.

How many people turn to the courts for justice? Their interpretation of fair and just is often quite different from the interpretation applied by the court based on case law and precedents.

Does Permabit provide any assurances to its customers that legal hassles will not result from deduplicating files? Are you offering your services as an expert witness or proffering your corporate attorneys to catch the legal bullet aimed at your customer if the need arises?  Will you pay whatever penalties or fines that may accrue?  Does your warranty or maintenance agreement so state?

Call it FUD, but I wonder if this is simply just a discussion that you would prefer not to be had at this juncture. I welcome a legal opinion on this matter and think that someone in the dedupe business ought to get just such an opinion in writing from a judge or the American Bar Association or somebody authoritative. Until that happens, we are all engaging in speculation that probably goes well beyond our areas of expertise.

If the question exists, and to many of my financial clients it most certainly does, why not get it out in the open and address it?</description>
		<content:encoded><![CDATA[<p>Hi Jered,</p>
<p>I am not disagreeing with any of your points from a technical standpoint. I don&#8217;t think that storage admins should decide what is important from a business perspective, deleting as they see fit electronic files of the company. But, you have made my point as well. Letting the IT guy field technology like de-dupe and expose all files to it, without a full understanding of the legal ramifications of doing so, is equally foolhardy.</p>
<p>Deduplication has NOT yet been subjected to the acid test of litigation. Nor has lossy compression to my knowledge.</p>
<p>What you claim about dedupe may be 100% true technically. That doesn&#8217;t have anything to do with the law, however.</p>
<p>How many people turn to the courts for justice? Their interpretation of fair and just is often quite different from the interpretation applied by the court based on case law and precedents.</p>
<p>Does Permabit provide any assurances to its customers that legal hassles will not result from deduplicating files? Are you offering your services as an expert witness or proffering your corporate attorneys to catch the legal bullet aimed at your customer if the need arises?  Will you pay whatever penalties or fines that may accrue?  Does your warranty or maintenance agreement so state?</p>
<p>Call it FUD, but I wonder if this is simply just a discussion that you would prefer not to be had at this juncture. I welcome a legal opinion on this matter and think that someone in the dedupe business ought to get just such an opinion in writing from a judge or the American Bar Association or somebody authoritative. Until that happens, we are all engaging in speculation that probably goes well beyond our areas of expertise.</p>
<p>If the question exists, and to many of my financial clients it most certainly does, why not get it out in the open and address it?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jered</title>
		<link>http://www.drunkendata.com/?p=1798&#038;cpage=1#comment-18299</link>
		<dc:creator>Jered</dc:creator>
		<pubDate>Wed, 02 Jul 2008 18:40:22 +0000</pubDate>
		<guid isPermaLink="false">http://www.drunkendata.com/?p=1798#comment-18299</guid>
		<description>Jon,

The point you ought to be focusing on is &quot;trusted operators can manage files and space as required&quot;.  This is 100% in violation of rules like SEC 17a-4.  A trusted admin can&#039;t be allowed to delete the files, period -- retained is retained.

As for whether or not deduplication affects data integrity for things like discovery, claiming it does is FUD plain and simple.  As I responded in your dedupe questionnaire:

Dedupe does not change data any more than compression changes data, or traditional file systems change data. Plain old LZW compression gives you a different output bitstream than what went in, with redundant parts removed. Conventional file systems break up files into blocks and scatter those blocks across one or more disks, requiring complicated algorithms to retrieve and return the data. Dedupe is no different. Nonrepudiation requirements are satisfied by the reliability and immutability of the system as a whole, deduplicating or not.

Jered Floyd
CTO, Permabit Technology Corp.</description>
		<content:encoded><![CDATA[<p>Jon,</p>
<p>The point you ought to be focusing on is &#8220;trusted operators can manage files and space as required&#8221;.  This is 100% in violation of rules like SEC 17a-4.  A trusted admin can&#8217;t be allowed to delete the files, period &#8212; retained is retained.</p>
<p>As for whether or not deduplication affects data integrity for things like discovery, claiming it does is FUD plain and simple.  As I responded in your dedupe questionnaire:</p>
<p>Dedupe does not change data any more than compression changes data, or traditional file systems change data. Plain old LZW compression gives you a different output bitstream than what went in, with redundant parts removed. Conventional file systems break up files into blocks and scatter those blocks across one or more disks, requiring complicated algorithms to retrieve and return the data. Dedupe is no different. Nonrepudiation requirements are satisfied by the reliability and immutability of the system as a whole, deduplicating or not.</p>
<p>Jered Floyd<br />
CTO, Permabit Technology Corp.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Administrator</title>
		<link>http://www.drunkendata.com/?p=1798&#038;cpage=1#comment-18294</link>
		<dc:creator>Administrator</dc:creator>
		<pubDate>Tue, 01 Jul 2008 14:40:23 +0000</pubDate>
		<guid isPermaLink="false">http://www.drunkendata.com/?p=1798#comment-18294</guid>
		<description>Unfortunately, both Congress and the regulatory bodies have a tendency to push out rules and regulations without a) any sort of detailed implementation guide or b) any sort of certification authority.  You don&#039;t know if a technology will bite you in the tuccus until a legal case establishes a precedent.

When EMC said that Centera was compliance certified, I asked the same question you are asking.  Who certified it?  I was told that they simply sent a letter to the SEC describing the product and did not hear back for 30 days (probably because the letter went to a dead letter office and there was no one there who certifies anything).  Their contention was that silence equals consent, which is not a valid legal tenet from what I have been told.  So, bottom line, it is bullshit.

Now, we have de-duplication providers arguing, in this case, that they have locks to hold data for specified intervals, wrapping themselves in compliance, when it remains to be seen whether de-duplicated files will pass muster with the Man in any case.

We can&#039;t just throw a blanket over the issue and hope it will go away.  It is important to repeat that many financials are going to great pains to segregate data from de-dupe that fall under the aegis of regulations.  That seems, to some degree, to defeat the purpose of de-dupe altogether.

That ain&#039;t FUD, it&#039;s just what folks are doing.</description>
		<content:encoded><![CDATA[<p>Unfortunately, both Congress and the regulatory bodies have a tendency to push out rules and regulations without a) any sort of detailed implementation guide or b) any sort of certification authority.  You don&#8217;t know if a technology will bite you in the tuccus until a legal case establishes a precedent.</p>
<p>When EMC said that Centera was compliance certified, I asked the same question you are asking.  Who certified it?  I was told that they simply sent a letter to the SEC describing the product and did not hear back for 30 days (probably because the letter went to a dead letter office and there was no one there who certifies anything).  Their contention was that silence equals consent, which is not a valid legal tenet from what I have been told.  So, bottom line, it is bullshit.</p>
<p>Now, we have de-duplication providers arguing, in this case, that they have locks to hold data for specified intervals, wrapping themselves in compliance, when it remains to be seen whether de-duplicated files will pass muster with the Man in any case.</p>
<p>We can&#8217;t just throw a blanket over the issue and hope it will go away.  It is important to repeat that many financials are going to great pains to segregate data from de-dupe that fall under the aegis of regulations.  That seems, to some degree, to defeat the purpose of de-dupe altogether.</p>
<p>That ain&#8217;t FUD, it&#8217;s just what folks are doing.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: MJ2784</title>
		<link>http://www.drunkendata.com/?p=1798&#038;cpage=1#comment-18293</link>
		<dc:creator>MJ2784</dc:creator>
		<pubDate>Tue, 01 Jul 2008 12:03:51 +0000</pubDate>
		<guid isPermaLink="false">http://www.drunkendata.com/?p=1798#comment-18293</guid>
		<description>In the end, I think that it comes down to case law.  (Note: I am not a lawyer.) The risk being run is that a lawsuit is brought up and the plaintiff&#039;s attorney claims that the storage subsystem used by the plaintiff changed the data and questions the validity of data provided in the case.  Now is this really a valid concern?  Who knows, probably not, but the result will then be complex legal wranglings where one of the main issues on trial becomes whether the data presented by the storage subsystem is 100% identical to what was originally written.

The plaintiff will throw out all the points they can to try to discredit the storage device and win the case.  In the case of the DD, they will use the argument that the technology is based on hashing which has a mathematical probability of hash collision and data corruption.  Yes, the likelihood may be small, but it is still there and they will use it.

The more complex the technology gets the more difficult it can be to prove the reliability which is one of the reasons why there may be more more concerns about subfile dedupe as compared to Single Instance Storage or CAS devices.


While many of the plaintiffs points may be misleading or just plain wrong, it will cost substantial time and money to defend the claims.  This is why Jon is suggesting that a legal opinion be considered.  If IT saves $ by implementing the solution, but opens themselves to these legal challenges, does the purchase make sense?  There is no clearcut answer and it depends on the individual company and industry.

To close the loop on the case, if the case is won by the defendant then the court must have acknowledged that the storage system was accurate and the device then has court precedence for its accuracy.  This means then that future lawsuits will have a difficult arguing the same point because the court will now have case law supporting the storage solution.

In the end, end users should understand the implication of this technology before purchasing and specifically the legal ramifications.  The best place to get feedback on the latter point is someone with legal expertise.</description>
		<content:encoded><![CDATA[<p>In the end, I think that it comes down to case law.  (Note: I am not a lawyer.) The risk being run is that a lawsuit is brought up and the plaintiff&#8217;s attorney claims that the storage subsystem used by the plaintiff changed the data and questions the validity of data provided in the case.  Now is this really a valid concern?  Who knows, probably not, but the result will then be complex legal wranglings where one of the main issues on trial becomes whether the data presented by the storage subsystem is 100% identical to what was originally written.</p>
<p>The plaintiff will throw out all the points they can to try to discredit the storage device and win the case.  In the case of the DD, they will use the argument that the technology is based on hashing which has a mathematical probability of hash collision and data corruption.  Yes, the likelihood may be small, but it is still there and they will use it.</p>
<p>The more complex the technology gets the more difficult it can be to prove the reliability which is one of the reasons why there may be more more concerns about subfile dedupe as compared to Single Instance Storage or CAS devices.</p>
<p>While many of the plaintiffs points may be misleading or just plain wrong, it will cost substantial time and money to defend the claims.  This is why Jon is suggesting that a legal opinion be considered.  If IT saves $ by implementing the solution, but opens themselves to these legal challenges, does the purchase make sense?  There is no clearcut answer and it depends on the individual company and industry.</p>
<p>To close the loop on the case, if the case is won by the defendant then the court must have acknowledged that the storage system was accurate and the device then has court precedence for its accuracy.  This means then that future lawsuits will have a difficult arguing the same point because the court will now have case law supporting the storage solution.</p>
<p>In the end, end users should understand the implication of this technology before purchasing and specifically the legal ramifications.  The best place to get feedback on the latter point is someone with legal expertise.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: IndyTgrFan</title>
		<link>http://www.drunkendata.com/?p=1798&#038;cpage=1#comment-18290</link>
		<dc:creator>IndyTgrFan</dc:creator>
		<pubDate>Tue, 01 Jul 2008 01:16:01 +0000</pubDate>
		<guid isPermaLink="false">http://www.drunkendata.com/?p=1798#comment-18290</guid>
		<description>You miss the point.  

What I&#039;m trying to figure out is WHO gets to say what is or isn&#039;t &quot;compliant&quot;?  And WHY?  

I&#039;m not all knowing but I&#039;ve never been made aware of some overarching entity that specifically tests and certifies technology for &quot;compliance&quot;.   Without this, as I asked above, isn&#039;t everything left up to broad interpretation (or you could call it ambiguity).  

Does such an entity exist?</description>
		<content:encoded><![CDATA[<p>You miss the point.  </p>
<p>What I&#8217;m trying to figure out is WHO gets to say what is or isn&#8217;t &#8220;compliant&#8221;?  And WHY?  </p>
<p>I&#8217;m not all knowing but I&#8217;ve never been made aware of some overarching entity that specifically tests and certifies technology for &#8220;compliance&#8221;.   Without this, as I asked above, isn&#8217;t everything left up to broad interpretation (or you could call it ambiguity).  </p>
<p>Does such an entity exist?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Administrator</title>
		<link>http://www.drunkendata.com/?p=1798&#038;cpage=1#comment-18289</link>
		<dc:creator>Administrator</dc:creator>
		<pubDate>Mon, 30 Jun 2008 18:59:20 +0000</pubDate>
		<guid isPermaLink="false">http://www.drunkendata.com/?p=1798#comment-18289</guid>
		<description>What do you propose I do, Indy?  Leave the questions unanswered?  I would consider that to be a huge diservice to readers even if it would get me projects with de-dupe vendors.

EMC calls CENTERA &quot;compliance certified&quot; -- which it obviously is not.  I have ranted about this point here, even challenging their paid analyst defense of the product, and have incurred the wrath of Hopkinton on exactly the same grounds as you are now criticizing my attack on de-dupe.

We should at least try to have legal provide an opinion before we deploy stuff that has specific legal ramifications.  As long as de-dupe is just being used with backups and an original version of data is hanging around, I couldn&#039;t care less what you put in the de-dupe repository.  However, when the vendor represents the solution as a compliance solution, I have to ask about its compliance features, don&#039;t I?</description>
		<content:encoded><![CDATA[<p>What do you propose I do, Indy?  Leave the questions unanswered?  I would consider that to be a huge diservice to readers even if it would get me projects with de-dupe vendors.</p>
<p>EMC calls CENTERA &#8220;compliance certified&#8221; &#8212; which it obviously is not.  I have ranted about this point here, even challenging their paid analyst defense of the product, and have incurred the wrath of Hopkinton on exactly the same grounds as you are now criticizing my attack on de-dupe.</p>
<p>We should at least try to have legal provide an opinion before we deploy stuff that has specific legal ramifications.  As long as de-dupe is just being used with backups and an original version of data is hanging around, I couldn&#8217;t care less what you put in the de-dupe repository.  However, when the vendor represents the solution as a compliance solution, I have to ask about its compliance features, don&#8217;t I?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: IndyTgrFan</title>
		<link>http://www.drunkendata.com/?p=1798&#038;cpage=1#comment-18288</link>
		<dc:creator>IndyTgrFan</dc:creator>
		<pubDate>Mon, 30 Jun 2008 15:14:46 +0000</pubDate>
		<guid isPermaLink="false">http://www.drunkendata.com/?p=1798#comment-18288</guid>
		<description>Words like &quot;compliance&quot; and &quot;regulatory&quot;  and &quot;legal entitity&quot; seem to get thrown around in articles like this.   You say that this isn&#039;t meant to Fan FUD yet how could it be construed any differently?  

What are the compliance requirements that people should be worried about?  And which &quot;regulatory&quot; agency is responsible for testing the technologies and certifiying them?   It seems to me that a &quot;requirement&quot; that doesn&#039;t have some &quot;regulated&quot; methodology established for &quot;certifying&quot; acceptable technologies is at best a hollow document that allows vendors to twist and manipulate their interpretation for their purposes and at worse a scare tactic re: LEGAL RAMIFICATIONS!!!

I would guess that without the above in place a good lawyer could just as easily rip to shreds the &quot;requirements document&quot;.   

Haven&#039;t these &quot;compliance&quot; issues been what EMC has used for years to convince companies to lock themselves and their data into the Centerra Platform and it&#039;s WORM?  Doesn&#039;t this technology offer a &quot;single instancing&quot;?  Why hasn&#039;t the issue been raised before now?  

Thoughts?</description>
		<content:encoded><![CDATA[<p>Words like &#8220;compliance&#8221; and &#8220;regulatory&#8221;  and &#8220;legal entitity&#8221; seem to get thrown around in articles like this.   You say that this isn&#8217;t meant to Fan FUD yet how could it be construed any differently?  </p>
<p>What are the compliance requirements that people should be worried about?  And which &#8220;regulatory&#8221; agency is responsible for testing the technologies and certifiying them?   It seems to me that a &#8220;requirement&#8221; that doesn&#8217;t have some &#8220;regulated&#8221; methodology established for &#8220;certifying&#8221; acceptable technologies is at best a hollow document that allows vendors to twist and manipulate their interpretation for their purposes and at worse a scare tactic re: LEGAL RAMIFICATIONS!!!</p>
<p>I would guess that without the above in place a good lawyer could just as easily rip to shreds the &#8220;requirements document&#8221;.   </p>
<p>Haven&#8217;t these &#8220;compliance&#8221; issues been what EMC has used for years to convince companies to lock themselves and their data into the Centerra Platform and it&#8217;s WORM?  Doesn&#8217;t this technology offer a &#8220;single instancing&#8221;?  Why hasn&#8217;t the issue been raised before now?  </p>
<p>Thoughts?</p>
]]></content:encoded>
	</item>
</channel>
</rss>
