An IT manager and a CIO reveal how they selected a vendor to help them deal with the exploding amounts of data on their systems.
"What we determined was that, if we signed CommVault, not only were we going to be able to solve our core problem, which was backup and recovery, but we could put in a system that allowed us to archive, as well as to utilize their eDiscovery component."
Kelley recalls that AMP was "in a huge growth mode, especially since we were building a number of power plants, and so we knew that the data would be growing by leaps and bounds. We anticipated that archiving was going to be an increasing problem for us down the road."
For Kelley, the vendor selection process involved creating a list of and prioritizing AMP's needs and then scoring each vendor on its ability to meet those needs, including:
- Does the software provide an easy, integrated solution, such as "a single pane of glass”? All of Kelley's systems—whether they be Windows, Linux, Oracle and so on —need to be backed up on one system.
- Is the product the vendor's core business? All of its R&D money needs to be spent improving and supporting that product.
- Is the product hardware agnostic? Kelley wanted to purchase software, not hardware, and the software needed to run and function similarly on any type of server.
- Is the product easy to administer? "It took about 24 hours each week to deal with the original 22 processes," says Kelley. "Today we spend about four hours a week. That's a $60,000 per year savings right there. And we no longer need an outside consultant to refresh our QA, dev, and test environments each Monday; it's now automated. That's another $60,000 a year savings."
But, says Kelley, the priority wasn't to save money; it was to make sure AMP has a very secure, robust product that, in the event the company's data needed to be recovered, it was recoverable.
The system proved itself almost immediately.
"Within the first two weeks of having CommVault go live, one of our core critical applications went down," Kelley recalls. "And we were able to recover the system in four hours, losing only five minutes of transactions. If we had had those original 22 systems in place, I estimate recovery would have taken us days. We would have not only lost transactions, but we wouldn't have been able to process new transactions during that period. I'd say that day, the product paid for itself."
About the Author
Paul Hyman is a freelance technology writer and editor. He was an editor-in-chief at CMP Publications (now United Business Media) and currently reports for such publications as Communications of the ACM, IHS’ Electronics360, and CRM Magazine. See an archive of some of his stories.