Our primary use case for VxRail right is deploying management systems. We are trying to consolidate some infrastructure.
VxRail has improved out organization because we are trying to be a little more proactive and elastic. We are trying to change our conventional approach to development. So this kind of solution is very suitable for data and that approach.
It could be very interesting to integrate VxRail with vSAN Ready Nodes, which we also use. Both solutions were built by Dell. vSAN Ready Nodes is another family of products, but with the same building blocks as VxRail, I think. VxRail easier to manage and deploy, but it is a little more expensive, and vSAN Ready Nodes would work better for some of our clients' use cases.
It would be good to have both of these solutions on the same dashboard. We don't want to have two management domain. It would be great for us to have these two Dell solutions integrated.
Dell could do more to help customers understand the real value proposition of this solution, especially related to deployment and scaling. A lot can be done with this solution. For example, it can be used for coverage bonds for virtual machines or as a solution for disaster recovery. This is important for customers with critical infrastructures.
In-person training and online training tools could be great, as well. Including training in the bundle with the equipment would be beneficial for us.
We have been using VxRail for two years.
Ecuador is a small market, so we do not have much access to local tech support. There are a lot of local commercial channels and partners, but not so much technical support. I think we only have two or three channels.
Before switching to VxRail, we had a very common solution that utilized Blade servers. We switched because we wanted something more elastic and scalable.
Deployment was not initially straightforward for us. We had an incompatibility issue that was very difficult for Dell Professional Service to solve. We had people from different countries trying to solve it. We were deploying the regional product but something with the version was inconsistent. It was a special case, but was very difficult to identify and to solve. It took us about two days.
Once we solved that issue, deployment was very easy. It took maybe an hour and was really easy.
The impression we got from the technical papers was that it would be very easy and quick to deploy this solution, but it was not. However, after we dealt with those issues, the solution was very solid, very easy. It wasn't easy to configure, but right now it's very stable. We are happy with that.