<?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: Enterprise Computing: Netapp and Efficiency &#8211; Managing Perception</title>
	<atom:link href="http://thestoragearchitect.com/2009/03/11/enterprise-computing-netapp-and-efficiency-managing-perception/feed/" rel="self" type="application/rss+xml" />
	<link>http://thestoragearchitect.com/2009/03/11/enterprise-computing-netapp-and-efficiency-managing-perception/</link>
	<description>Storage, Virtualisation &#38; Cloud</description>
	<lastBuildDate>Mon, 21 May 2012 20:10:36 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2.1</generator>
	<item>
		<title>By: Cleanur</title>
		<link>http://thestoragearchitect.com/2009/03/11/enterprise-computing-netapp-and-efficiency-managing-perception/#comment-665</link>
		<dc:creator>Cleanur</dc:creator>
		<pubDate>Wed, 11 Mar 2009 16:33:01 +0000</pubDate>
		<guid isPermaLink="false">http://thestoragearchitect.com/?p=412#comment-665</guid>
		<description>The main problem is that Netapp continue to treat WAFL configuration like some kind of black art. They have overlapping and often conflicting best practices for features which are often spread across multiple documents.

Many of the best practices seem abiguous at best and are left to user interpretation. Most of the space hogging options are switched on by default, possibly to protect both parties from mis configuration, and many of the space savers are not actually accessible without dropping to the CLI.

Almost all of these space saving options also have a knock on effect on other features within the system. You either definately need to understand in some detail all of the potential outcomes before switching a particular feature on or off, or continually monitor to ensure things are happening as intended.

Simple and risk free it aint.</description>
		<content:encoded><![CDATA[<p>The main problem is that Netapp continue to treat WAFL configuration like some kind of black art. They have overlapping and often conflicting best practices for features which are often spread across multiple documents.</p>
<p>Many of the best practices seem abiguous at best and are left to user interpretation. Most of the space hogging options are switched on by default, possibly to protect both parties from mis configuration, and many of the space savers are not actually accessible without dropping to the CLI.</p>
<p>Almost all of these space saving options also have a knock on effect on other features within the system. You either definately need to understand in some detail all of the potential outcomes before switching a particular feature on or off, or continually monitor to ensure things are happening as intended.</p>
<p>Simple and risk free it aint.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

