Commentary

George Crump
 

The End Of The Storage Volume

Traditional volumes have been around as long as we have had file systems, but now may be the time to pronounce the end of the storage volume. As data centers get larger and storage systems are populated with more and more physical drives they are growing into a storage manager's nightmare. There are just too many volumes of drives to be managed effectively.

Traditional volumes have been around as long as we have had file systems, but now may be the time to pronounce the end of the storage volume. As data centers get larger and storage systems are populated with more and more physical drives they are growing into a storage manager's nightmare. There are just too many volumes of drives to be managed effectively.Volumes were simple at first, there was a 1:1 relationship between servers and physical disk. However, there was a need to increase the level of protection; we started to add a second drive for mirroring or multiple drives for RAID. Now there was a 1 to many relationship between servers and drives. Next came the SAN and with it Logical Unit Numbers (LUNs). Then we had multiple servers each connecting to a volume and each of these volumes shared a LUN. Finally came server virtualization and now the storage manager has to deal with many virtual machines hosted by a cluster of physical hosts all with shared access to volumes that in turn may shared specific LUNs. Its enough to make you want to consider another career or at least become an application guy.

Companies like 3PAR, Compellent and ZFS based products like Nexenta are trying to break the volume based model to a pooled storage approach. All the storage is placed into a globally available storage pool. All the servers have access to all of the storage, you just need to tell each server how much capacity it can have and possibly what tier of storage it can use. There are no LUNs and specific volume assignments to manage.


More Storage Insights

White Papers

More >>

Reports

More >>

Webcasts

More >>

The key gain here is the elimination of the time spent by storage managers managing LUNs and volumes. A shared storage pool essentially reduces the job to one of managing global capacity and as we discuss in our article on Thin Provisioning Basics, most pooled storage systems provision capacity thinly. In actuality you are only managing used capacity.

The storage system will make decisions on what data should go where automatically. Some of these systems can self-optimize themselves to deliver better performance by moving data to the edge of hard drive platters, wide striping data or by automatically migrating between tiers of storage.

For some storage managers, losing the feeling of control of knowing exactly what data is on which drives is the biggest challenge. While most pooled storage systems will let you provision storage in the classic hard set, this data goes here method it is not ideal. Given the stack of virtual machines, physical hosts, SAN, Volumes and LUNs, the data center now deals with the classic model has become almost unmanageable. Letting the storage system do the work is a better use of the storage manager's time.

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

Subscribe to our RSS feed.

George Crump is founder of Storage Switzerland, an analyst firm focused on the virtualization and storage marketplaces. It provides strategic consulting and analysis to storage users, suppliers, and integrators. An industry veteran of more than 25 years, Crump has held engineering and sales positions at various IT industry manufacturers and integrators. Prior to Storage Switzerland, he was CTO at one of the nation's largest integrators.


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