Is storage management already past its prime?

It may sound hasty to dismiss a technology that many companies have yet to deploy or even evaluate, but some of the vibes I am getting lately from vendors suggest that storage management applications may become obsolete before becoming mainstream.

[ MarioApicella's column is now a blog! Get the latest storage news from the Storage Adviser blog. ]

It's hard to give a short answer to the question of what's wrong with storage management, but perhaps the beginning of the end for the technology is the limited scope revealed by its name.

Does it make sense to devolve so much effort to rein in just a single piece of the infrastructure puzzle? Shouldn't storage be orchestrated in harmony with other important -- perhaps even more important -- pillars such as servers, networks, and above all, applications?

To be fair, vendors such as Symantec and HP have not spared efforts to integrate storage management with other disciplines. But quickly finding the source of a problem when it lies within the storage labyrinth remains a difficult-to-nearly-impossible task for many systems administrators.

The fact is, in many organization charts, titles such as "database administrators" belong to a different box than their storage counterparts. That often makes problem resolution an adversarial affair rather than a cooperative effort.

However, conflicts between administrators are more an effect of the divide between storage and other resources than its cause. The main problem is that companies lack tools to provide a comprehensive, storage-resource-inclusive view of their IT services, which complicates overall management, monitoring, and planning.

Companies such as Onaro and Akorri say there's a remedy. Onaro's recently released SANscreen Foundation 3.5 is a suite of applications that promises to fill the gap between storage and other resources in your datacenter.

Visit the Onaro Web site and you'll find an interesting Flash demo of SANscreen. Deployment starts with an automated discovery of the topology of your SAN, similar to the starting point of many SRM applications. Next you add a service model to that static picture, specifying the access, capacity, performance, and recovery characteristics delivered by your SAN.

From there, you begin creating policies to define what the SAN should deliver: Application A should have dual path access to its database, no less than 1GB of free capacity, remote replicas, etc. Once that is done, SANscreen stands on your network like a referee at a tennis match, ready to intercept, record, and call out any policy violation or service level degradation. 

However, SANscreen provides much more than just a list of fouls. In addition to examining a list of violations, you can drill down to specific details, review the policy for correctness, and quickly identify the affected applications and storage components. For example, here's a chart pinpointing unauthorized connections between servers and storage resources.