Dark Reading is part of the Informa Tech Division of Informa PLC

This site is operated by a business or businesses owned by Informa PLC and all copyright resides with them.Informa PLC's registered office is 5 Howick Place, London SW1P 1WG. Registered in England and Wales. Number 8860726.

News

5/19/2008
03:15 PM
George Crump
George Crump
Commentary
50%
50%

Standalone SRM

In a recent briefing with a Storage Resource Management Software manufacturer I heard the quote that I have now heard 1,001 times; "Excel is the No. 1 Storage Resource Management software." People are using Excel to do SRM work more often than specific SRM tools. They are manually inputting storage capacity, storage used, and other storage information into Excel spreadsheets.

In a recent briefing with a Storage Resource Management Software manufacturer I heard the quote that I have now heard 1,001 times; "Excel is the No. 1 Storage Resource Management software." People are using Excel to do SRM work more often than specific SRM tools. They are manually inputting storage capacity, storage used, and other storage information into Excel spreadsheets.The problem is that it is all manual, gets out of date very quickly, and doesn't typically capture all the information you really need to understand your data assets. Despite all this, Microsoft Excel remains the most used tool for SRM... Why?

First of all, it's cheap, at least compared with other SRM tools. Some of these tools cost more than the storage they're managing. That's a problem. I don't care what analyst study you cite, if you're a system or storage administrator hoping to get your boss to sign off on a storage management application that is more than the cost of the physical storage you just bought, that is a very tough sell. While they don't need to be anywhere close to the cost of Excel, SRM tools need to be reasonably priced and probably be less than the cost of the storage they are managing.

The second reason is, ironically, it is independent of storage manufacturers. It is a standalone tool. What has really hurt the SRM market is as each of these utilities began to build a customer base, many of them were acquired by storage hardware manufacturers and then their appeal faded. To be universally accepted, these tools need to be under the leadership of a company that has no allegiance to making their support of one hardware platform better than another. They need to be as free to exploit the full reporting and monitoring potential of the storage platform as possible. Standalone companies such as Tek-Tools and Monosphere are two examples of companies that do this well today.

This causes competition not only between software vendors like Tek-Tools, Monosphere, and others, but it also will cause competition at the hardware level. Hardware suppliers will be forced to not only open their API sets to external software developers, but also to expand the capabilities of their API sets. An Open API set is good; an open API set that actually does something is even better.

Allowing these software vendors to focus on this market allows for better overall mapping of the environment as well. For example, these companies have added support for VMware, which allows you to see how storage is connected to the virtual machine or how many virtual machines are accessing the same LUN or Volume so you can be aware of potential performance traps. This additional mapping isn't limited to VMware. Support for databases, backup applications, and specific OSes is available.

SRM vendors spend a lot of time convincing us that their tools are needed, but really that is a given. That is why you are using Excel to track things right now. Right? The convincing needs to center on the value of not using a manual tool, albeit cheap, like Excel, to using an automated dynamic tool. These tools can make life in the multivendor data center worth living. Even if all your storage does have the same logo, getting an end-to-end view from the application through the virtualization tool to the storage has tremendous value.

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.

 

Recommended Reading:

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
COVID-19: Latest Security News & Commentary
Dark Reading Staff 8/3/2020
Pen Testers Who Got Arrested Doing Their Jobs Tell All
Kelly Jackson Higgins, Executive Editor at Dark Reading,  8/5/2020
Exploiting Google Cloud Platform With Ease
Dark Reading Staff 8/6/2020
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
Special Report: Computing's New Normal, a Dark Reading Perspective
This special report examines how IT security organizations have adapted to the "new normal" of computing and what the long-term effects will be. Read it and get a unique set of perspectives on issues ranging from new threats & vulnerabilities as a result of remote working to how enterprise security strategy will be affected long term.
Flash Poll
The Changing Face of Threat Intelligence
The Changing Face of Threat Intelligence
This special report takes a look at how enterprises are using threat intelligence, as well as emerging best practices for integrating threat intel into security operations and incident response. Download it today!
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2020-16219
PUBLISHED: 2020-08-07
Delta Electronics TPEditor Versions 1.97 and prior. An out-of-bounds read may be exploited by processing specially crafted project files. Successful exploitation of this vulnerability may allow an attacker to read/modify information, execute arbitrary code, and/or crash the application.
CVE-2020-16221
PUBLISHED: 2020-08-07
Delta Electronics TPEditor Versions 1.97 and prior. A stack-based buffer overflow may be exploited by processing a specially crafted project file. Successful exploitation of this vulnerability may allow an attacker to read/modify information, execute arbitrary code, and/or crash the application.
CVE-2020-16223
PUBLISHED: 2020-08-07
Delta Electronics TPEditor Versions 1.97 and prior. A heap-based buffer overflow may be exploited by processing a specially crafted project file. Successful exploitation of this vulnerability may allow an attacker to read/modify information, execute arbitrary code, and/or crash the application.
CVE-2020-16225
PUBLISHED: 2020-08-07
Delta Electronics TPEditor Versions 1.97 and prior. A write-what-where condition may be exploited by processing a specially crafted project file. Successful exploitation of this vulnerability may allow an attacker to read/modify information, execute arbitrary code, and/or crash the application.
CVE-2020-16227
PUBLISHED: 2020-08-07
Delta Electronics TPEditor Versions 1.97 and prior. An improper input validation may be exploited by processing a specially crafted project file not validated when the data is entered by a user. Successful exploitation of this vulnerability may allow an attacker to read/modify information, execute a...