Commentary

George Crump
 

The Foundation Of The Data Asset

In my last entry we discussed Making Data an Asset. This entry will focus on where that data asset should be stored. What is needed is a strong storage foundation, one that is designed to last for years, if not decades, but also one that will store that data efficiently and of course be complimentary to the enterprise class indexing that we described in our last entry.

In my last entry we discussed Making Data an Asset. This entry will focus on where that data asset should be stored. What is needed is a strong storage foundation, one that is designed to last for years, if not decades, but also one that will store that data efficiently and of course be complimentary to the enterprise class indexing that we described in our last entry.This foundation is similar to the one we described in our recent article "The Foundation of DeDupe's Next Era". The difference is that if we are looking at data as an asset as opposed to something we have to retain. To ascertain what data is worthy of being an asset we need to have our index and classifications performed across the data center by companies like Index Engines or Kazeon. Those solutions have to be enterprise in scale yet be simple to implement; a single or few appliances that can index the entire enterprise in a reasonable amount of time. Once the data has been mined, data that has value or is an asset should be stored in a vault-like storage location as soon as it becomes static.

These types of storage vaults are being provided today be companies like EMC, Nexsan, NEC and Permabit. Their goal is to be able to retain data for years, store that data efficiently and to be able to provide some sort of retention capabilities that will maintain a chain of custody on that data.


More Storage Insights

White Papers

More >>

Reports

More >>

Webcasts

More >>

Also these types of solutions must be able to be searched quickly and they must be able to move that data back into production quickly. Although tape can now be indexed, disk archives may be a more ideal storage vault for asset data. Data that is an asset will have a high probability of needing to be found and restored quickly. While indexing tape is important, index today's data that is on disk so that you can understand what data is an asset and then being able to get that data back quickly can give a company a competitive advantage.

This storage vault needs to have some of the other attributes of any other disk archive. Beyond being able to find the asset, redundancy may be the most important part of this storage vault. The archive must be able to survive through multiple component failures and still be able to deliver the data back to you. Once you have classified something as an asset, storing it just in case you need it is no longer enough. You have verified that there is a high probability that you will need it, when you do you have to make sure that you can get it back.

Once the organization realizes that there is some "gold" in the data that they are keeping, the investment to find and then store that gold becomes obvious. It allows the IT team to more easily cost justify future purchases that will benefit not just the data assets but all the data in the enterprise.

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