What is our primary use case?
We use it to work with a record database and with some specific tools for our customer.
What is most valuable?
With SVC it is very easy to manage and to use for migration, meaning that when we want to move or to keep control of the volume or update a server database, it is very easy. That's why we use it.
What needs improvement?
If IBM wants want to put SAN Volume Control ahead of their competitors, like NetApp, they just need to put in the snap volume because now they use what is called a flash copy. This means that you have to take all the volume instead of NetApp which uses their snapshot.
They will have to improve that. Today, it is not so difficult to snap a volume when you have an SSD or NVMe disk, it just takes a few seconds to do it. They should improve the snapshot in the IBM SAN Volume Control.
For how long have I used the solution?
I have been using IBM SAN Volume Control for two years.
What do I think about the stability of the solution?
IBM SAN Volume Control is stable.
What do I think about the scalability of the solution?
IBM SAN Volume Control is scalable.
We have 500 users using it in different positions.
Today, we have three guys to maintain and manage it, but it is not at full design.
How are customer service and support?
We are satisfied with tech support. We have no pending tickets with support or anything like that now. It is really proactive sometimes.
Which solution did I use previously and why did I switch?
We previously worked with NetApp and sometimes with Oracle Exadata. We switched because it was a little bit complex with commercial rules. Every time they changed we decided to go for something where we know the price. We know how much we can spend tomorrow to increase volume and capacity. It is easy for us to go on the market and to see how much we will spend in the future. With some of those solutions it is so difficult to know that. So it was not only because of the technical aspect that we switched.
How was the initial setup?
It was very easy to install and manage.
Installation and starting the migration for each project depends, because during the project you have to do the training. This means that between the end of installation and the training, you sometimes have two months. During those two months, you have a lot of things to do. Sometimes it takes weeks or months.
You have, for example the Windows Servers with Office or something like that. It is a different preparation for DevOps.
What was our ROI?
The return on investment means that you want to speak about CAPEX or OPEX. In our activity, we are more on an OPEX budget. Today, we can rapidly find the amount that we have to engage if we want more capacity or more units. It is very easy. So there is return on investment when you can stay with one person to just calculate and say, "Okay. We know that for this kind of project we have to spend..."
When it is easy, you manage better. You know the budget. I do not have to call everybody in the world to negotiate with integrators or other guys. We don't spend our time discussing about the price.
In the data center, return on investment applies to when your solution is not so high for the crew and all those things are characteristic. It means the number of users in the rack and the coolant to keep the temperature at a very good level. Again, we are seeing that we can do what we want when we want. It's more important.
What's my experience with pricing, setup cost, and licensing?
With IBM, we can separate the license from storage. That means that you are, for example, with an SSD drive, and you buy an SKU. SSD is one SKU. But if you want another path driver with more capacity, your SKU is 1.4 SKU.
You have to compare. With the IBM service you do what you want. Meaning that if you want to make a red six or a red five, you do what you want. You have more tools with the license, you have all the tools to be able to manage your solution. Now, they changed their pricing for redemption tools for compression. They changed it directly in the hardware compression on the drive. This is why I can say that we have all the things to manage and to use the solution with the storage license.
Which other solutions did I evaluate?
We have a lot of cards. For example, we have Exadata. We have cards with HP. We have cards with NetApp and Dell EMC, but we don't have the card with HGS. We have the card for IBM, but they are not our primary partners or supplier. Today, we have the technical experience and that is why we engage with some of them. IBM is for the primary storage but we use Veeam for the backup. We use other things and other software. We have a partnership with Cohesity.
What other advice do I have?
On a scale of one to ten, I would give IBM SAN Volume Control a 10.
Which deployment model are you using for this solution?
On-premises