We do a lot of backups daily, and mainly we just keep the operating system images. We do take database and active directory backups as well. We handle all types of backups using this product.
Read reviews of IBM StoredIQ alternatives and competitors
Easy to manage with a simple user interface but needs better local support
Pros and Cons
- "The user interface is very easy to navigate."
- "The local support could be improved."
What is our primary use case?
What is most valuable?
The user interface is very easy to navigate. The interface itself is very simple.
Overall, it is doing the job we need it to do.
It supports whatever line types and support types and systems we have. It supports all types of backup systems quite easily.
The stability has been very good so far. We haven't had any problems with it.
The product is easy to manage.
What needs improvement?
The local support could be improved. Right now, it's something about the solution that is lacking.
They should offer better partners that can help us implement the solution in a better way.
It would be ideal if they offered editing or activating options.
I don't know how good it is with the virtual environment. I have not tried the product with VMware, for example.
For how long have I used the solution?
I've been using the solution for about six years at this point. It's been a while.
What do I think about the stability of the solution?
We've never had any issues with stability. It doesn't crash or freeze. There are no bugs or glitches. It's pretty reliable.
What do I think about the scalability of the solution?
We are still running with a single server, and it's a per server per instance-based license model. If we need to add our first storage-based model or another division, we cannot support both. It's a licensing model issue.
How are customer service and technical support?
The local support is lacking overall. It's something they need to really work on improving.
Which solution did I use previously and why did I switch?
We have worked with Veritas and IBM in the past, however, that was a very long time ago. I wouldn't be able to compare them to this solution as too much time has passed and much has changed. We used those solutions maybe ten or so years ago now.
How was the initial setup?
The initial setup is not easy or difficult. It's moderate, or somewhere in the middle. I wouldn't describe the implementation as complex, however.
The deployment too more than expected, as the vendor involved was having some staffing issues. The engineers were changing and we had some technical requirements which we realized at a later stage.
Maintenance isn't required very often, however, we have to ensure it is up-to-date. We also have to ensure whenever anything changes, we have to properly add them to the Commvault - whether they are new servers or new clients. Whenever we change our backup library or the memory storage, we have to reconfigure things. In that regard, there is occasional maintenance, depending on our background changes.
We only need one person to manage the solution. It doesn't take a lot of staff. Typically, they are an administrator and they handle everything that needs to be done as it's required.
What about the implementation team?
We are integrators and therefore we are able to implement the solution ourselves.
What's my experience with pricing, setup cost, and licensing?
The pricing falls somewhere in the middle of what the market offers. It's not overly expensive. The licensing model is quite good. Everything is included under it.
What other advice do I have?
We are just a customer and an end-user.
We're using the latest version of the solution. We always use the latest version.
I'd recommend the solution.
I'd rate it at a seven out of ten.
Which deployment model are you using for this solution?
Disclosure: I am a real user, and this review is based on my own experience and opinions.