VMware vSphere Review

The DRS feature is helpful to my organization.


What is our primary use case?

My primary use case for this solution is the DRS feature of the solution.

How has it helped my organization?

When checking the utilization reports, the operational reporting and matrixes are a little weak.  In terms of what has been the starting growth or trend analysis is something which, currently they have an add-on which we have not used  because it's an add-on product, which we have not bought. As of now, they have this capability but I've not seen these features to be more integrated on the base product itself rather than having as a special add-on.

What is most valuable?

I really value the DRS feature of the solution. Apart from that, there is a high availability in the feature called VMotion. In addition, the centralized management throughout the V-Center software is useful.

What needs improvement?

When checking the utilization reports, the operational reporting and matrixes are a little weak.  In terms of what has been the starting growth or trend analysis is something which, currently they have an add-on which we have not used  because it's an add-on product, which we have not bought. As of now, they have this capability but I've not seen these features to be more integrated on the base product itself rather than having as a special add-on.

As I mentioned, the necessary improvement would be to add additional features that would integrate reporting and management in terms of automation. Those are the two things I would say it's a lot of, or the third item could be of some service important to integration. Right now everybody is talking about private clubs, but these are the base foundation so, the effect it has had on embedded software attack, running on the hypervisor for self-provisioning, it definitely has an edge.

For how long have I used the solution?

More than five years.

What do I think about the scalability of the solution?

Its highly scalable, we have never had to make radical changes to the design to make it more, or to put in more capacity. So, as we are growing we have been adding the servers into the existing pool without even worrying about a need for redesign. As we grow, we find that our company is more dependent upon this product. 

How is customer service and technical support?

Technical support usually we have online support, where we can log a call if there is any trouble. But so far in the last three years that I have been here, we rarely, or I cannot collect any one instance where we had necessity to log a case with the support team, the forums and the community are, have enough knowledge based articles to make us pass through any technical challenges that we have faced.

Which solutions did we use previously?

We have prior use knowledge of Hyper-V. First, it did not have this automatic scalable capability which are scored to move across from one specific hardware to another without impacting any downtime. And secondly, it did not have a lot of automatic configuration capabilities, based on the utilization of the specific hardware it could re-balance what goes around on top of it. So these two are they key features that I feel were lacking at that point in time and it's hard to use another feature that I feared was lacking. In addition, it relied a lot upon the physical machine.

How was the initial setup?

It was very straightforward setup. 

The way we had done it is it came pre-installed with as part of the hardware stack that we purchased so the new servers that we purchased we bundled that ESXi software on top of it from the hardware vendor itself. So from that perspective, the implementation strategy was to have it as an OEM100 by the hardware vendor itself and then the way we designed it from our side is we designed it into two different data centers. One for production, one for test and development. So just have a logical separation there in terms of the hardware that was used for production and what was used for distribution.

Overall timelines are approximately two to three weeks time-frame. After the hardware was developed, they came in and installed the base software and considered it based on our requirements.

What about the implementation team?

Deployment was done by the hardware vendor itself. The hardware came from HP and there was a HP reseller who shipped us the hardware. The resellers team only came and did all the installation and confirmation after the design was agreed with us.

What's my experience with pricing, setup cost, and licensing?

Pricing is competitive I would say, because usually we buy the software, along with the hardware stock so it's usually a bundle thing that we try to squeeze the hardware windows in to get us proper discounts. So, it is regularly higher than what a Microsoft overall solution turns out to be. But, the capabilities are worth it. The price is justified.

Licensing is pretty standard.

Which other solutions did I evaluate?

In my previous organization, we used Hyper-V for over eight years.

What other advice do I have?

From my side, the advice would be to design it properly the first time. Have proper capacity planned out, and don't just create over-provision in the production environment. Best you can do with provisioning with production, you definitely need to have some capacity sizing done properly. And, that goes in not for just this product but any virtualization product that a company implements. You do not want to overload the hardware. You have to think about the capabilities of the end-user.

Disclosure: I am a real user, and this review is based on my own experience and opinions.
Add a Comment
Guest
Sign Up with Email