Druva Blog > Customer Stories

egan-case-study-two

Evolving Data Management at Egan Company

This is the second in a 3-part blog series about Egan Company’s journey to 100 percent virtualization and an almost exclusive reliance on cloud-based, as-a-service apps like Druva Phoenix. In the first blog, we asked Jim Nonn, Egan’s CIO, and Andy Blomquist, IT Systems and Support Manager, about how Egan started off on it’s cloud journey. They continue the discussion below. Read part one here.

Q: What have been some of your biggest challenges with data management?

JN: Where do I start? I suppose the biggest issues with any business are cost and complexity. Traditional data storage solutions involve substantial OpEx like servers and RAIDs, and hardware always means software, and that needs to be upgraded and refreshed and kept compatible with other systems. Managing all that means headcount, and that drives CapEx.

AB: Regardless of the cost, data protection is our #1 responsibility. I remember when we used to rotate taking backup tapes home with us at night. That was our daily backup, we collected weeklys in fireproof storage containers and then a service would periodically pickup tapes for offsite storage. That was expensive, and if the catalogs on any of those tapes were damaged or corrupted, the whole thing was a loss.

Q: Where did you go from there?

AB: That was quite a while ago. We tried Commvault and Veeam disk backup systems, they worked, but Commvault was too complex, we always had to get people onsite to do anything out of the ordinary or even just for upgrades. Veeam was an adequate “semi-cloud” solution, although I think in the back of my mind I never felt comfortable having on-premises storage as an intermediary. Neither Commvault nor Veeam had what we were really looking for: scalable, direct-to-cloud data protection, delivered as-a-service, that eliminates on-premises infrastructure.

JN: We’d both go to VMware user group meetings to keep up on things. In particular, we needed a disaster-recovery (DR) solution, and it was obvious to me that a real cloud-native solution, one without on-premises dependencies, was the only way to go. We heard about Druva Phoenix as a backup solution, but it also matched what I believed to be the primary requirements of a DR app.

Q: Moving applications and environments to the cloud can be disruptive and complicated. Did this concern you?

AB: To tell you the truth, that has not been my experience. Maybe it is with some apps, if they’re just adapted to work with the cloud, but a cloud-native app should be easy and painless. Druva certainly is.

Q: So you started a trial?

JN: I always do my research before starting a trial. I don’t want our team using something that really works well and getting to love it and then finding out the numbers don’t add up. Like test-driving a Ferrari when you’ve got a Chevy budget. So with Druva, I made sure we knew exactly what our costs would be beforehand. After that, we tried it, and honestly, I think that if 100 companies did a Druva Phoenix trial, 99 would buy it.

In the upcoming, final blog, Jim and Andy talk about why Druva Phoenix turned out to be a good fit for Egan and why their relationship with Druva is likely to flourish.

Next Steps

Check out this case study and get the full story on how Egan conquered data management and protection challenges.

Watch our on-demand webinar featuring Egan Company and learn how they disaster-proofed its data in the cloud with Druva.

Read the previous blog in this series, Customer Spotlight: Egan Company.


0 Comments

Leave a reply

Your email address will not be published. Required fields are marked *

*