Dark Reading is part of the Informa Tech Division of Informa PLC

This site is operated by a business or businesses owned by Informa PLC and all copyright resides with them.Informa PLC's registered office is 5 Howick Place, London SW1P 1WG. Registered in England and Wales. Number 8860726.

News

1/13/2009
04:48 PM
George Crump
George Crump
Commentary
50%
50%

Out Of Space? Thin Provisioning Vs. Traditional Provisioning

There has been a lot written about thin provisioning and how it can optimize capacity and increase efficiency of the storage administrator. The constant response is that thin provisioning is "risky" compared with traditional hard-provisioned volumes. Is it really?

There has been a lot written about thin provisioning and how it can optimize capacity and increase efficiency of the storage administrator. The constant response is that thin provisioning is "risky" compared with traditional hard-provisioned volumes. Is it really?Thin provisioning was driven to market success by companies like 3PAR and Compellent and now just about every major storage vendor offers thin provisioning. The proposed fear about thin provisioning is what if you have over-subscribed your storage or have a sudden need for storage and suddenly find yourself without capacity?

When the "oh my, I'll run out of capacity" debate comes up, I always ask, how is this any different with hard provisioning? If you have a server with storage allocated to it and you suddenly run out of capacity, what are you going to do? Assuming it is on a SAN, you are going to stop what you are doing, hope that you have reserve capacity, and assign it to the LUN that had just run out of storage. After this you still need to run the OS provisioning tools so it will recognize that additional capacity. And, of course, hope it works like it should. Seems that it often does not.

What if you are out of your reserve? Or what if your reserve does not have the right type or speed of drive? The likelihood of this happening is just as high as you running out of capacity on a thin-provisioned system. Then what are you going to do? Unallocating capacity from an existing hard LUN is not easy and, in most cases, it is impossible. The manual process in moving this data is ugly; you more likely will live with it and just place a rush order for more capacity.

In fact, in this scenario, thinly provisioned volumes are safer. The reserve, if you will, on a thin volume already is shared. There is no allocation that needs to occur and no reassignment to be done. In fact, because the capacity is shared, the chance of you running out of space on any particular server is much lower than in the hard environment.

The hard-provisioning options are to either massively over-allocate your storage on a per-application basis or to manage and monitor your volumes in an almost draconian fashion. The first option is going to be expensive from a hard cost standpoint. The second will be expensive from a people allocation perspective. Neither option is very viable cast against the current economic situation.

The important thing is that managing this capacity with a storage system that supports thin volumes is automatic and in these times of stretched thin IT staffs, efficiency is critical.

Join us for our upcoming Web cast on Driving IT Efficiency 2.0.

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.

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
Commentary
What the FedEx Logo Taught Me About Cybersecurity
Matt Shea, Head of Federal @ MixMode,  6/4/2021
Edge-DRsplash-10-edge-articles
A View From Inside a Deception
Sara Peters, Senior Editor at Dark Reading,  6/2/2021
Register for Dark Reading Newsletters
White Papers
Video
Cartoon
Current Issue
The State of Cybersecurity Incident Response
In this report learn how enterprises are building their incident response teams and processes, how they research potential compromises, how they respond to new breaches, and what tools and processes they use to remediate problems and improve their cyber defenses for the future.
Flash Poll
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2021-34682
PUBLISHED: 2021-06-12
Receita Federal IRPF 2021 1.7 allows a man-in-the-middle attack against the update feature.
CVE-2021-31811
PUBLISHED: 2021-06-12
In Apache PDFBox, a carefully crafted PDF file can trigger an OutOfMemory-Exception while loading the file. This issue affects Apache PDFBox version 2.0.23 and prior 2.0.x versions.
CVE-2021-31812
PUBLISHED: 2021-06-12
In Apache PDFBox, a carefully crafted PDF file can trigger an infinite loop while loading the file. This issue affects Apache PDFBox version 2.0.23 and prior 2.0.x versions.
CVE-2021-32552
PUBLISHED: 2021-06-12
It was discovered that read_file() in apport/hookutils.py would follow symbolic links or open FIFOs. When this function is used by the openjdk-16 package apport hooks, it could expose private data to other local users.
CVE-2021-32553
PUBLISHED: 2021-06-12
It was discovered that read_file() in apport/hookutils.py would follow symbolic links or open FIFOs. When this function is used by the openjdk-17 package apport hooks, it could expose private data to other local users.