Commentary

Andrew Conry Murray
 

Where To Start With ILM

Last week I hosted an ILM (Information Life-cycle Management) video Web cast. One of the questions that came up was "Where do I start with ILM without much risk?" It's a good question.

Last week I hosted an ILM (Information Life-cycle Management) video Web cast. One of the questions that came up was "Where do I start with ILM without much risk?" It's a good question.First, some background. ILM recognizes that the business value of data will change over its lifetime, and that data should be moved to the most appropriate storage medium based on that value. ILM comprises a whole set of processes, policies, and technologies, including tiered storage and some form of information classification capability.

Business drivers for ILM include cutting storage costs by moving low-value data to inexpensive disk or tape as quickly as possible; meeting regulatory and legal compliance issues, such as e-discovery, with a minimum of effort and expense; and improving storage management and resource utilization.


More Software Insights

White Papers

More >>

Reports

More >>

Webcasts

More >>

So where to start? E-mail archiving is a good choice.

E-mail is a prime target for e-discovery requests, in which corporations have to cough up all relevant electronic records related to litigation. Given how much business happens via e-mail, enterprises need a system in place to ensure that messages are safely stored and searchable.

The archive means that IT gets copies of all mail (and prevents enterprising executives from deleting incriminating messages). Many archive products can provide de-duplication, full content indexing, and search. Archives also can help enforce retention and disposal policies, so that e-mail can be saved as long as required -- and then immediately gotten rid of.

Archiving also eases the strain on production storage. Mail can be moved off Exchange servers and into the archive quickly (say within 30 days). Smaller loads on Exchange servers means faster backups and snapshots.

It also means IT doesn't have to enforce mail box quotas on users. The archive essentially acts as a virtual mail box, because older mail is moved to a lower-cost storage tier, but is still available to the end user with one click. With a seemingly infinite mailbox, IT doesn't have to fight user workarounds to quotas, such as PST files that get squirreled onto local drives, file shares, or even USB drives.

All these capabilities tie back to ILM principles. At the same time, the business benefits of archiving will be a more powerful sell to executives than "archiving will assist with our ILM strategy."

Of course, an e-mail archive is only part of an ILM architecture. It doesn't address structured data in databases, or unstructured data (i.e., Word and PowerPoint files, CAD files, medical images, or the myriad content being generated inside SharePoint and other collaboration environments). I'll get to those issues in subsequent posts.


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