News
6/17/2010
08:34 AM
George Crump
George Crump
Commentary
Connect Directly
RSS
E-Mail
50%
50%

Keep Everything Forever, Part II - Indexing

In our last entry we reintroduced the idea of a keep everything forever storage retention strategy. We also touched on some of the basic capabilities like cost effective storage options and data movement options that can make a forever retention strategy realistic. In this entry we will look at what is one of the most important requirements the ability to find what you have in the archive.

In our last entry we reintroduced the idea of a keep everything forever storage retention strategy. We also touched on some of the basic capabilities like cost effective storage options and data movement options that can make a forever retention strategy realistic. In this entry we will look at what is one of the most important requirements the ability to find what you have in the archive.The fact that you have a keep it all retention strategy is going to be of little value to you if you can't find a discrete piece of information when you need it. Typically you are keeping all this data in case at some point down the road you need to produce it. Most often this will be in response to some sort of legal action or needing to prove adherence to a regulation. While you don't need rapid restore speed in these cases you do need to be able to deliver it in a timely manner. You can longer throw people at the problem and manually dig through information. In some cases you have to have a system in place that can not only find what you do have but also prove that you don't have something.

This comes down to implementing a solution that can index all the information that you have on storage and give you the ability to search on key words or phrases. I believe this index has to be storage vendor agnostic and potentially even device type agnostic. For example the ability that some backup applications have to build index information on the data that passes through it is good but the only thing being indexed is just that information that passes through the application. What about the data that does not get backed up by that application? Also what if you change your mind and switch applications? Are you really prepared to lock into a particular backup application for decades? And if you were do you think it is realistic to expect to send all your data through that application forever?

Beyond being storage and vendor agnostic the indexing system has to be able to scale to handle the ever growing amount of data that it will be responsible for. Scale here comes in two ways. The first is the ability to scale to meet ingestion rates. In other words how much information can the indexing system process in a given window? The other is how large can the meta-data that the indexing system creates scale to? If you are planning on keeping information forever that meta-data catalog's performance becomes critical.

The final piece also relates to the meta-data that the indexing system creates, how space efficient is the meta-data? You don't want to have to double your capacity requirements to hold all this meta-data, so the indexing system has to be able to capture the information it needs but do so very space efficiently.

Finding information in a keep it forever strategy is important, but probably most important is if you can actually afford to keep it forever. Our final entry in this series will cover trying to determine if a keep it forever strategy is cost effective.

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.

Comment  | 
Print  | 
More Insights
Register for Dark Reading Newsletters
White Papers
Flash Poll
Current Issue
Cartoon
DevOps’ Impact on Application Security
DevOps’ Impact on Application Security
Managing the interdependency between software and infrastructure is a thorny challenge. Often, it’s a “developers are from Mars, systems engineers are from Venus” situation.
Video
Slideshows
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2014-0103
Published: 2014-07-29
WebAccess in Zarafa before 7.1.10 and WebApp before 1.6 stores credentials in cleartext, which allows local Apache users to obtain sensitive information by reading the PHP session files.

CVE-2014-0475
Published: 2014-07-29
Multiple directory traversal vulnerabilities in GNU C Library (aka glibc or libc6) before 2.20 allow context-dependent attackers to bypass ForceCommand restrictions and possibly have other unspecified impact via a .. (dot dot) in a (1) LC_*, (2) LANG, or other locale environment variable.

CVE-2014-0889
Published: 2014-07-29
Multiple cross-site scripting (XSS) vulnerabilities in IBM Atlas Suite (aka Atlas Policy Suite), as used in Atlas eDiscovery Process Management through 6.0.3, Disposal and Governance Management for IT through 6.0.3, and Global Retention Policy and Schedule Management through 6.0.3, allow remote atta...

CVE-2014-2226
Published: 2014-07-29
Ubiquiti UniFi Controller before 3.2.1 logs the administrative password hash in syslog messages, which allows man-in-the-middle attackers to obtains sensitive information via unspecified vectors.

CVE-2014-3020
Published: 2014-07-29
install.sh in the Embedded WebSphere Application Server (eWAS) 7.0 before FP33 in IBM Tivoli Integrated Portal (TIP) 2.1 and 2.2 sets world-writable permissions for the installRoot directory tree, which allows local users to gain privileges via a Trojan horse program.

Best of the Web
Dark Reading Radio