Commentary

George Crump
 

2010 Storage Trends Scale Out Storage

This time of year I am always asked what storage trends will take off during the next year. I often resist because it is very hard to get it right. What I try to do is see what is likely to gain traction in the coming year. Over the next few entries we will explore some of the 2010 storage trends that you ought to be paying attention to. One of those is scale out storage.

This time of year I am always asked what storage trends will take off during the next year. I often resist because it is very hard to get it right. What I try to do is see what is likely to gain traction in the coming year. Over the next few entries we will explore some of the 2010 storage trends that you ought to be paying attention to. One of those is scale out storage.Scale out storage solutions have become a popular way to balance the need to find storage solutions that are cost effective and that can scale to meet future performance demands. Scale out solutions, also called clustered or grid storage systems, work by providing the users with the ability to independently scale storage processing, capacity and bandwidth.

Scale out storage can do this by using specialized technology like that of 3PAR or by using a standard Intel Architecture like EMC's VMAX, IBM's XIV and HP's LeftHand Networks. On the NAS side companies like Isilon Systems and Symantec have similar architectures. For backup and archive there are storage companies like Permabit, ExaGrid and Sepaton. What you'll notice from this list is that scale out storage, once the domain of start ups, now has the attention of major storage manufacturers.


More Storage Insights

White Papers

More >>

Reports

More >>

Webcasts

More >>

The grid or clustering capabilities of these systems should allow all the processing and bandwidth capabilities of the storage systems to be used across the storage platform. This means that as you scale these systems you do not have a loose collection of independent storage systems that are managed by a central management interface. In a grid or clustered storage system you are dealing with one entity.

What makes these systems so appealing is their ability to buy just the capacity and performance that you need now, then add performance, capacity or bandwidth when you need it. This compares favorably to the traditional dual controller or single head environment. Once these systems reach their performance maximum they require the purchase of another system or an upgrade to a faster one. In most cases you are forced to over buy capacity and performance and hope that you don't outgrow the system too fast. In either case you may end up paying extra for capabilities that you won't need for a few more years. If you could have waited that few more years to purchase that capacity or performance it would have been less expensive.

This is not to say that the classic storage architecture is dead and should be abandoned. If a single enclosure system can provide you all the performance and capacity that you can ever foresee needing then these systems are fine and should be initially less expensive. The range that classic storage architectures can cover continues to increase as the processing power and capacity per box ride the technology wave.

Track us on Twitter: http://twitter.com/storageswiss

Subscribe to our RSS feed.

George Crump is lead analyst of Storage Switzerland, an IT analyst firm focused on the storage and virtualization segments. Find Storage Switzerland's disclosure statement here.


Related Reading




Currently we allow the following HTML tags in comments:

Single tags

These tags can be used alone and don't need an ending tag.

<br> Defines a single line break

<hr> Defines a horizontal line

Matching tags

These require an ending tag - e.g. <i>italic text</i>

<a> Defines an anchor

<b> Defines bold text

<big> Defines big text

<blockquote> Defines a long quotation

<caption> Defines a table caption

<cite> Defines a citation

<code> Defines computer code text

<em> Defines emphasized text

<fieldset> Defines a border around elements in a form

<h1> This is heading 1

<h2> This is heading 2

<h3> This is heading 3

<h4> This is heading 4

<h5> This is heading 5

<h6> This is heading 6

<i> Defines italic text

<p> Defines a paragraph

<pre> Defines preformatted text

<q> Defines a short quotation

<samp> Defines sample computer code text

<small> Defines small text

<span> Defines a section in a document

<s> Defines strikethrough text

<strike> Defines strikethrough text

<strong> Defines strong text

<sub> Defines subscripted text

<sup> Defines superscripted text

<u> Defines underlined text

InformationWeek encourages readers to engage in spirited, healthy debate, including taking us to task. However, InformationWeek moderates all comments posted to our site, and reserves the right to modify or remove any content that it determines to be derogatory, offensive, inflammatory, vulgar, irrelevant/off-topic, racist or obvious marketing/SPAM. InformationWeek further reserves the right to disable the profile of any commenter participating in said activities.

Disqus Tips To upload an avatar photo, first complete your Disqus profile. | View the list of supported HTML tags you can use to style comments. | Please read our commenting policy.
T-Shirt Giveaway T-Shirt Giveaway: Each week we're selecting one great comment from our readers. The author of the comment will receive an InformaitonWeek Community t-shirt. So get posting!
Subscribe to RSS

Resource Links