<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	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:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>The Storage Architect &#187; Switch It On</title>
	<atom:link href="http://thestoragearchitect.com/tag/switch-it-on/feed/" rel="self" type="application/rss+xml" />
	<link>http://thestoragearchitect.com</link>
	<description>Storage, Virtualisation &#38; Cloud</description>
	<lastBuildDate>Wed, 23 May 2012 22:20:49 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2.1</generator>
		<item>
		<title>Enterprise Computing: The Wide Striping Debate</title>
		<link>http://thestoragearchitect.com/2009/07/12/enterprise-computing-the-wide-striping-debate/</link>
		<comments>http://thestoragearchitect.com/2009/07/12/enterprise-computing-the-wide-striping-debate/#comments</comments>
		<pubDate>Sun, 12 Jul 2009 11:17:47 +0000</pubDate>
		<dc:creator>Chris M Evans</dc:creator>
				<category><![CDATA[GestaltIT]]></category>
		<category><![CDATA[Virtualisation]]></category>
		<category><![CDATA[EMC]]></category>
		<category><![CDATA[HDS]]></category>
		<category><![CDATA[Hu Yoshida]]></category>
		<category><![CDATA[Martin Glasborow]]></category>
		<category><![CDATA[storagebod]]></category>
		<category><![CDATA[Switch It On]]></category>
		<category><![CDATA[thin provisioning]]></category>
		<category><![CDATA[Wide Striping]]></category>

		<guid isPermaLink="false">http://thestoragearchitect.com/?p=638</guid>
		<description><![CDATA[<p>I&#8217;ve read with interest this week the posts on wide striping and the consequent expansion to thin provisioning.  Here are some of the highlights:</p> <p>First there&#8217;s Martin Glasborow&#8217;s <a rel="nofollow" href="http://storagebod.typepad.com/storagebods_blog/2009/07/wide-stripes.html" >post</a>, which discusses whether wide striping and thin provisioning should be chargeable items.  I&#8217;d go a step further than Martin and suggest that thin [...]<!--Begin ClixTrac.com Rotator Code -->
<script type="text/javascript" language="javascript" src="http://www.clixtrac.com/rotate/321"></script>
<!--End ClixTrac.com Rotator Code -->]]></description>
			<content:encoded><![CDATA[<p>I&#8217;ve read with interest this week the posts on <strong>wide striping</strong> and the consequent expansion to <strong>thin provisioning</strong>.  Here are some of the highlights:</p>
<p>First there&#8217;s Martin Glasborow&#8217;s <a rel="nofollow" href="http://storagebod.typepad.com/storagebods_blog/2009/07/wide-stripes.html" >post</a>, which discusses whether wide striping and thin provisioning should be chargeable items.  I&#8217;d go a step further than Martin and suggest that thin provisioning (TP) should also be free; after all, over time thin provisioning becomes fat provisioning without some kind of reclaim technology and there&#8217;s only value to TP with something like Zero Page Reclaim to get back those unused blocks.</p>
<p>Then there&#8217;s Hu Yoshida&#8217;s <a href="http://blogs.hds.com/hu/2009/07/overheads-for-thin-provisioning.html" >post</a> referring to the Overheads of Thin Provisioning.  In it, Hu makes a very interesting claim that wide striped LUNs have <em>&#8220;greater protection from multiple disk failures&#8221;</em>.  On this point I have to <strong>disagree</strong>.  Firstly, if a disk fails within a RAID group, then the impact on a LUN is only experienced if the subsequent failure is also in the same RAID group.  <em>This is a fact whether then LUN is wide striped or not</em>.  For wide striped LUNs which are spread across multiple RAID groups, there&#8217;s <strong>more</strong> chance of a failure because a double disk failure could occur within <strong>any</strong> of the RAID groups supporting the presentation of that LUN.</p>
<p>In addition, wide striping has more <strong>impact</strong> if a failure occurs.  One benefit of having LUNs created from a single RAID group is that the impact of that RAID group failing is limited to only those LUNs.  Imagine a 300GB 3+1 RAID group divided into 18x 50GB LUNs.  Failure of that RAID group impacts only the 18 LUNs.  So, wide stripe across 10 RAID groups &#8211; now the impact of <strong>any</strong> RAID group failure is <strong>180</strong> LUNs.  Remember that&#8217;s <strong>any</strong> RAID group failure, which is much more likely as we have more RAID groups on which every LUN is dependent.</p>
<p>Finally there&#8217;s EMC and their free Virtual Provisioning &#8211; free that is on <strong>new</strong> purchases, not existing DMX-4 deployments.  While laudible, this offering is less generous compared to <a href="http://www.hds.com/go/free-storage-virtualization/" >HDS&#8217; Switch It On</a> promotion which offers free UVM, Dynamic Provisioning (first 10TB only) and Tiered Storage Manager on <strong>existing</strong> USP-V deployments.  </p>
<p>Wide striping and thin provisioning are clearly becoming features where vendors are looking to differentiate their products.  This must be vindication for the likes of 3Par who&#8217;ve had these features from day 1.</p>
<p>P.S.  You can find two EMC blogger references to the free Virtual Provisioning <a rel="nofollow" href="http://thestorageanarchist.typepad.com/weblog/2009/07/2015-challenge-accepted-free-vp.html" >here</a> and <a rel="nofollow" href="http://storagezilla.typepad.com/storagezilla/2009/07/virtual-provisioning-for-symm-included-at-no-extra-charge.html" >here</a>.</p>
]]></content:encoded>
			<wfw:commentRss>http://thestoragearchitect.com/2009/07/12/enterprise-computing-the-wide-striping-debate/feed/</wfw:commentRss>
		<slash:comments>12</slash:comments>
		</item>
		<item>
		<title>Enterprise Computing: HDS Switches On Virtualisation For Free</title>
		<link>http://thestoragearchitect.com/2009/04/22/enterprise-computing-hds-switches-on-virtualisation-for-free/</link>
		<comments>http://thestoragearchitect.com/2009/04/22/enterprise-computing-hds-switches-on-virtualisation-for-free/#comments</comments>
		<pubDate>Wed, 22 Apr 2009 06:16:50 +0000</pubDate>
		<dc:creator>Chris M Evans</dc:creator>
				<category><![CDATA[Uncategorized]]></category>
		<category><![CDATA[dynamic provisioning]]></category>
		<category><![CDATA[HDP]]></category>
		<category><![CDATA[HDS]]></category>
		<category><![CDATA[Switch It On]]></category>
		<category><![CDATA[Universal Volume Manager]]></category>
		<category><![CDATA[Virtualisation]]></category>

		<guid isPermaLink="false">http://thestoragearchitect.com/?p=484</guid>
		<description><![CDATA[<p><a href="http://thestoragearchitect.com/2009/04/22/enterprise-computing-hds-switches-on-virtualisation-for-free/switch-it-on/" rel="attachment wp-att-501" ></a>There&#8217;s no doubting <a href="http://www.hds.com/index.html" >HDS</a>&#8216; Universal Volume Manager (<a href="http://www.hds.com/products/storage-software/universal-volume-manager.html" >UVM</a>), aka external storage virtualisation is a cool product.  I&#8217;ve used it many times &#8211; it does the job.  However, the main drawback to using the product for me was always cost (I mentioned this only a few weeks ago [...]<!--Begin ClixTrac.com Rotator Code -->
<script type="text/javascript" language="javascript" src="http://www.clixtrac.com/rotate/321"></script>
<!--End ClixTrac.com Rotator Code -->]]></description>
			<content:encoded><![CDATA[<p><a href="http://thestoragearchitect.com/2009/04/22/enterprise-computing-hds-switches-on-virtualisation-for-free/switch-it-on/" rel="attachment wp-att-501" ><img class="alignright size-full wp-image-501" title="switch-it-on" src="http://thestoragearchitect.files.wordpress.com/2009/04/switch-it-on.jpg" alt="switch-it-on" width="245" height="76" /></a>There&#8217;s no doubting <a href="http://www.hds.com/index.html" >HDS</a>&#8216; Universal Volume Manager (<a href="http://www.hds.com/products/storage-software/universal-volume-manager.html" >UVM</a>), aka external storage virtualisation is a cool product.  I&#8217;ve used it many times &#8211; it does the job.  However, the main drawback to using the product for me was always cost (I mentioned this only a few weeks ago on <a href="http://thestoragearchitect.com/2009/01/24/enterprise-computing-using-usp-for-migrations/" >this post</a>).  Well, now that&#8217;s changed; until the end of this year, HDS are offering UVM for free.  See the announcement <a href="http://www.hds.com/corporate/press-analyst-center/press-releases/2009/gl090422.html" >here</a>.  HDS are calling it their &#8220;Switch It On&#8221; campaign.</p>
<p>OK, free isn&#8217;t quite free &#8211; there are a few caveats.  Customers have to pay for maintenance, but other than that, there&#8217;s no charge for using UVM on current USP-V deployments.  In addition, customers can &#8220;super-size&#8221; the offer and also get Hitachi Tiered Storage Manager (<a href="http://www.hds.com/products/storage-software/hitachi-tiered-storage-manager.html" >HTSM</a>), Hitachi In-System Replication and limited access to Hitachi Dynamic Provisioning (<a href="http://www.hds.com/products/storage-software/hitachi-dynamic-provisioning.html" >HDP</a>) all for free.</p>
<p>It is unlikely HDS are doing this out of some altruistic concern for their customers.  Clearly they see benefits in driving more business by offering these licences at no cost.  So how can customers benefit?</p>
<p><strong>Traditional Approach</strong></p>
<p>Traditionally, UVM is seen as a tool to manage the migration process or get data into a USP and there&#8217;s no question that UVM can be used for these purposes.  Typically, here are some of the costs associated with migration:</p>
<ul>
<li><strong>Staff Resource Costs</strong> &#8211; migrations take time and effort to plan.  The longer they take, the more cost is incurred with change control, planning, co-ordination with other teams and on actually performing the migration, which is typically performed out of hours.</li>
<li><strong>Software Costs</strong> &#8211; migrations may require specific software products or tools (e.g UVM or TDMF).</li>
</ul>
<p>Here are some of the constraints on migration work:</p>
<ul>
<li>Limited downtime on servers.</li>
<li>Data to be migrated out of hours or within certain time frames.</li>
<li>No host tools (like volume managers) to perform migrations.</li>
<li>Data migrations are required to disparate locations.</li>
<li>Data integrity and synchronicity must be maintained (e.g. replicated data must be consistent if an outage occurred during the migration process.</li>
</ul>
<p>The tradeoff with UVM has always been the cost of the UVM licence compared to the savings which could be made on the above issues by using the product.  For example, UVM could be used to virtualise an entire array (or arrays) behind a USP-V in a single weekend.  Consecutive weekends can then be used to migrate into the USP.  This controlled approach (a) enables the storage managers to perform the migration, freeing up the host teams (b) allows the storage managers to load balance migrations into the USP-V (c) monitor performance as migrations occur (d) enable target servers to be immediately upgraded to new code/driver levels which may not have been supported previously on the older arrays.</p>
<p><strong>Lateral Thinking</strong></p>
<p>Getting UVM for free enables some more lateral thinking:</p>
<ul>
<li><strong>Example 1: Migrate out of the USP</strong>.  There are lots of examples of moving data into a USP, but what about moving it out?  If you&#8217;ve purchased a USP and it&#8217;s fully populated with disk and full, how do you save money?  Well, one option is to get a UVM licence and migrate non-critical (and perhaps non-production) data to an externalised array at a lower cost.  Previously this could only be commercially viable if the reduced cost of the external array covered the cost of the UVM licence.  Now there&#8217;s no need to worry.</li>
<li><strong>Example 2: Migrate in and De-Dupe.</strong>  With UVM and HDP, external storage arrays can be migrated into the USP and placed on thin provisioned volumes. HDP Zero Page Reclaim removes the &#8220;empty&#8221; blocks of data during this process.  For certain data profiles, this could provide signficant savings.</li>
<li><strong>Example 3: A Free Datacentre Migration Tool.</strong>  Imagine you&#8217;ve got to move data on arrays not currently replicated &#8211; but that data needs to reside in another location.  If a pair of USPs are available, why not virtualise the source and target arrays and use the USP to move the data between the two sites?  This could save purchasing replication licences for an array or resolve a problem where replication isn&#8217;t possible from certain hardware.</li>
<li><strong>Example 4: Implement a 3DC Solution.</strong>  How about using the USP-V as a three datacentre solution?  Here&#8217;s how it works; two USP-Vs are used to replicate data synchronously between two local sites.  The target devices are actually virtualised across a fabric to a third site using UVM.  In this way, data can be moved to a third site without requiring a third copy of data.</li>
</ul>
<p>With free software, the options are only limited by imagination.  If HDS are prepared to offer software for free then there&#8217;s no excuse not to use it.</p>
]]></content:encoded>
			<wfw:commentRss>http://thestoragearchitect.com/2009/04/22/enterprise-computing-hds-switches-on-virtualisation-for-free/feed/</wfw:commentRss>
		<slash:comments>5</slash:comments>
		</item>
	</channel>
</rss>

