Commentary

George Crump
 

Thin Provisioning Key Feature Of Storage Virtualization

Thin provisioning can convince an application that is has more storage available than is actually allocated to the app.

Storage virtualization is a broad term for a series of capabilities. The core of which is disk abstraction, which we described in our first storage virtualization entry. In the next few entries we will cover some of the specific features that most storage virtualization systems provide and what the pros and cons are to each. First up is thin provisioning, one of headline features of storage virtualization.

As we describe in our Thin Provisioning White Paper this technology dynamically allocates storage capacity to a volume as it is used. Historically, most applications only use a fraction of the capacity that is assigned to them. Thin provisioning counts on this to be able to make the application think it has more capacity than may be physically installed.


More Insights

Webcasts

More >>

White Papers

More >>

Reports

More >>

For example, if you have a database application that the administrator thinks is going to need 2 TB of capacity someday, we all know if that application ever actually reaches that capacity it is not going to happen the day after it is put into production. It may take years to get anywhere close to 2TB. Also, this is purely captive storage, there is no actual data, just white space, so it can't be compressed or deduplicated. It is 2 TB just sitting there spinning, wasting money, and consuming electricity.

Thin provisioning allows you to tell the application that it has 2 TB of storage without actually hard assigning 2 TB of storage to it. Applied across a SAN of servers, thin provisioning can lead to dozens of terabytes--if not more--of capacity savings.

But there are downsides to thin provisioning.

For the most part, thin provisioning works well. But there is the chance that if there is a sudden need for storage capacity and all of it gets consumed by a particular application, it may leave the other applications with no room to grow and you have to place a rush order for more storage. Most storage systems or virtualization software provide a very detailed analysis of actual utilization, so you do have to keep an eye on the report.

There also is a potential performance impact of the storage system having to constantly allocate storage capacity to volumes on the fly. Some storage systems could have a significant performance loss if several applications start to write large amounts of new data simultaneously, bogging down the storage processor that has to handle all this on the fly allocation.

Thin provisioning may also fool storage management software. The software may not understand that the capacity being reported is thinly provisioned. This renders the software, which is designed to prevent you from running out of storage unexpectedly, useless for monitoring actual utilization.

There workarounds, including journal-based approaches as we discuss in our article "The VDI Storage Trade Off - Performance." And some storage systems have specific silicon dedicated to the management of the dynamic allocation of capacity to thin-provisioned volumes. Finally, several of the storage monitoring tools have added the ability to report on actual capacity utilization so that emergency purchases can be avoided.

The cost benefits of thin provisioning handily outweigh the risks of running out of capacity unexpectedly. The performance concerns are valid and something to pay attention to when selecting a system, but there are solutions that have worked around this as well. Thin provisioning is just one capability of the typical storage virtualization solution. In the next entry we will cover the advantages and disadvantages of Automated Tiering.

Follow Storage Switzerland on Twitter

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


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.
Subscribe to RSS

Resource Links