News

6/17/2010
08:34 AM
George Crump
George Crump
Commentary
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
Comments
Oldest First  |  Newest First  |  Threaded View
More Than Half of Users Reuse Passwords
Curtis Franklin Jr., Senior Editor at Dark Reading,  5/24/2018
Is Threat Intelligence Garbage?
Chris McDaniels, Chief Information Security Officer of Mosaic451,  5/23/2018
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Write a Caption, Win a Starbucks Card! Click Here
Latest Comment: This comment is waiting for review by our moderators.
Current Issue
Flash Poll
[Strategic Security Report] Navigating the Threat Intelligence Maze
[Strategic Security Report] Navigating the Threat Intelligence Maze
Most enterprises are using threat intel services, but many are still figuring out how to use the data they're collecting. In this Dark Reading survey we give you a look at what they're doing today - and where they hope to go.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2018-11505
PUBLISHED: 2018-05-26
The Werewolf Online application 0.8.8 for Android allows attackers to discover the Firebase token by reading logcat output.
CVE-2018-6409
PUBLISHED: 2018-05-26
An issue was discovered in Appnitro MachForm before 4.2.3. The module in charge of serving stored files gets the path from the database. Modifying the name of the file to serve on the corresponding ap_form table leads to a path traversal vulnerability via the download.php q parameter.
CVE-2018-6410
PUBLISHED: 2018-05-26
An issue was discovered in Appnitro MachForm before 4.2.3. There is a download.php SQL injection via the q parameter.
CVE-2018-6411
PUBLISHED: 2018-05-26
An issue was discovered in Appnitro MachForm before 4.2.3. When the form is set to filter a blacklist, it automatically adds dangerous extensions to the filters. If the filter is set to a whitelist, the dangerous extensions can be bypassed through ap_form_elements SQL Injection.
CVE-2018-11500
PUBLISHED: 2018-05-26
An issue was discovered in PublicCMS V4.0.20180210. There is a CSRF vulnerability in "admin/sysUser/save.do?callbackType=closeCurrent&navTabId=sysUser/list" that can add an admin account.