Commentary

George Crump
 

Making Storage Management Easier

As we discussed in our last entry no matter how easy the storage protocol or storage system you select at some point someone is going to have to interact with the storage itself. It may be a problem that needs to be resolved or it may be a need to provision a new server but something will come up. In most mid-sized data centers managing storage is no one's full time job. It is something that is dealt with as the situation arises. This interrupt driven style of storage management is not ideal but it is reality.

As we discussed in our last entry no matter how easy the storage protocol or storage system you select at some point someone is going to have to interact with the storage itself. It may be a problem that needs to be resolved or it may be a need to provision a new server but something will come up. In most mid-sized data centers managing storage is no one's full time job. It is something that is dealt with as the situation arises. This interrupt driven style of storage management is not ideal but it is reality.The goal of the interrupt driven storage manager is to solve the problem and then get back to their real job as fast as possible. We find that there are two steps that can be taken that can help accomplish this goal. In this entry we will discuss the first step which deals with system selection and the second is selecting the right management tool, which we will discuss in an upcoming entry.

Most decision makers when selecting a storage solution will consider ease of implementation, ease of expansion and ease of operation, all of which are very important to keeping storage management time to a minimum. One consideration that seems to often be overlooked is how far will the system take you? Meaning if the organization grows and expands when will you need new or additional storage systems for IT to help support that growth? You don't want to be in a situation where you have five or six separate storage systems supporting the business. If you do storage will almost certainly become a full time job by potentially multiple people.


More Storage Insights

White Papers

More >>

Reports

More >>

Webcasts

More >>

Look instead for either a system that has all the capacity and performance you are going to need to cover the next few years of storage demands either by having that capability built in up front or one that can be expanded to meet those future demands. This does not mean having a collection of separate storage systems that can all be managed by some sort of unifying application that the vendor provides. Most of these provide a unified view but individual operations means managing and configuring each individual storage system.

For many mid-sized or smaller data centers consolidating to one storage system is a reasonable goal. For some mid-sized and larger data centers covering all your storage needs with one system may not be feasible. Not every system can do everything. However, keeping the number of systems to two or three, at the most, should be achievable for all but the very largest data centers.

The payback of having one system, assuming it meets the other criteria of implementation and operation ease, is less time managing storage. When troubleshooting a problem, looking for available capacity for that new VM or deciding which file server that new user should be attached to, if there is only one place to look it becomes a very simple decision.

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