Commentary

George Crump
 

Don't Just Manage Your Data -- Know it

There are countless ways to manage data available to the storage manager today but most of these solutions look at data as a problem. Few take an asset view of data, understanding that it is something to be cultivated and leveraged for future use. Storage managers should do more than just manage their data, they should know it.

There are countless ways to manage data available to the storage manager today but most of these solutions look at data as a problem. Few take an asset view of data, understanding that it is something to be cultivated and leveraged for future use. Storage managers should do more than just manage their data, they should know it.Knowing your data means understanding what's inside of it, understanding its contents. Companies like CommVault, EMC, Kazeon and Index Engines all have the ability to understand and categorize the information inside of your files.

Much of the messaging being applied to this space has been around litigation readiness and response. This market, often called eDiscovery, is certainly a viable market but not very compelling to the IT manager unless they are currently being sued. These systems however, if they could be scaled more efficiently, can offer storage managers and their users access to data in a manner that would allow it to be mined for value, which would put users in a new era of IT Discovery.


More Storage Insights

White Papers

More >>

Reports

More >>

Webcasts

More >>

This could be as simple as knowing that a certain type of data exists in the environment but not being able to find it. In this scenario, a user typically recreates the data they need, as best they can, after spending the time to search for it. Imagine being able to find information, enterprise-wide, in seconds and then use that data for a new project. It could be a tremendous time saver for the individual user (not to mention the frustration) and a capacity saver for the system administrator.

Data as an asset can move beyond just time savings and become more of a problem solver. Solutions to how to solve a challenge that the organization needs to address may have already been tackled. Again, with an IT Discovery capability, that information could be found and leveraged when faced with the same problem in the future.

The challenge facing these systems is one of scale. The time it takes to inspect the environment and create an index is a real challenge for some of these systems. While many can add multiple nodes to improve performance, the amount of nodes needed for this indexing process may be prohibitive. An alternative is to leverage a process that is already in place and already moving data. For example CommVault (on its product) and Index Engines (across multiple backup products) essentially leverage the fact that the backup process is bringing the data across the network, and let the inspection tap into that data stream to perform its analysis.

In the future this analysis could be set on some other inline appliance like file virtualization or automated tiering systems. For eDiscovery to become IT Discovery scaling of the analysis needs to be addressed. The meta-data database that represents all the content stored in the enterprise must be able to be updated quickly, as a multi-day, or in some cases week long, index process is not going to work for the broader environment. IT Discovery needs the ability to refresh its information more often than that.

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