ViPR [EOL] Reviews

Name: ViPR [EOL]
Brand: Dell Technologies
Rating: 0.0 (3 reviews)

3 reviews
0% willing to recommend

What is ViPR [EOL]?

EMC ViPR is software-defined storage to manage and automate all storage resources for traditional and next-generation cloud storage platforms. EMC ViPR Controller is storage automation software that centralizes and transforms storage into a simple, extensible, and open platform. It abstracts and pools resources to deliver automated, policy-driven storage services on demand through a self-service catalog Ð reducing time, cost, and risk.

Get the ViPR [EOL] Buyer's Guide and find out what your peers are saying about ViPR [EOL], FormationOne Dynamic Storage Platform and more!

Helped 865,295 peers since 2012

Featured ViPR [EOL] reviews

it_user6186

Independent Analyst and Advisory Consultant at Server StorageIO - www.storageio.com

PART I During the recent EMCworld event in Las Vegas among other things, EMC announced ViPR (read announcement here). Note that this ViPR is not the same EMC Viper project from a few years ago that was focused on data footprint reduction (DFR) including dedupe. ViPR has been in the works for a…

Read full review

it_user323706

Storage Administrator at a retailer with 1,001-5,000 employees

Obviously I have had my issues since 1.5. In beta it was a 1.0 release. It’s only since recently they have approved that you can update all the back-end (Red Hat) yourself and then the front-end. I have always done it myself because it cost to have an engineer upgrade it. When I went from 2.5 to 3.5 SP1 was a big increase, our EMC guy helped us schedule a free upgrade. Not only did the they guide us through adding an extra VM to scale, they fixed a few minor issues that had come from previous upgrade I had done. Needless to say, I was very impressed with the differences and help.

Read full review

it_user323625

Systems Architect at a tech services company with 1,001-5,000 employees

After upgrading to SRM 3.6, many of the reports did not have the proper graphing algorithm and were displaying incorrect data. This took approx. 6 weeks to fix. Created an “Alert” and after applying the change SRM stopped working for half a day. Started working again after some scheduled database job ran.

Read full review