VMware vSphere Reviews

Our primary use case is to implement a high availability server environment.

It helps to automate the data replication and DR.

The feature that I have found most valuable is the auto recovery during failure.

The scalability of the solution should be improved.

The scalability needs improvement.

We are virtualizing our x86 server infrastructure with VMware vSphere. It consolidates our environment dramatically. Our virtualization ratio is over 92%.

Using vSphere we have virtualized over one thousand servers and this gave us management, cost and datacenter space advantages.

vSphere offers the High Availability feature which serves automatic recovery of failed host's virtual machines on another host or hosts in the cluster. Also, DRS makes the cluster balanced.

Although vSphere is a nearly perfect product, it does need a little improvement. Datacenter and Cluster structure should be mixed so that the management of clusters would be easier.

• Cloud computing service (IaaS)
• Private/hybrid cloud
• Virtualization infrastructure
• Virtualization desktop infrastructure.

• High availability causes downtime service because it is needed to reboot VMs.
• Fault tolerance is limited by the four vCPUs.
• The service provider is not easy to integrate via API like OpenStack.

• vCloud Director, because we may use it as the dashboard for providing cloud services.
• vCenter 
• vSphere, because it helps us in the management of thousands of VMs in the coverage UI.

The SDK/API to help SPs (service providers) provide the pay-as-you-go business model in cloud service.

Standard commercial environment.

A gold standard of server virtualization.

• vMotion
• NSX
• Dynamic deployment of new servers is critical.

Improvements to the vCenter server appliance are still needed, especially the HTML5.

My primary use case for the product is testing Home Lab. I was involved in the early vSphere 6.7 beta. I wanted to see what the new features were, how it worked. I'm using it currently in my Home Lab for testing lots of the different products as a vSphere-base for vSAN, NSX, running the latest vCenter, etc.

Some of the critical workloads that I'm running in my vSphere environment are Exchange, SQL, various different application servers, and those have to be up and available at all times, and vSphere does that for us. It gives us High Availability, failover, vMotion capability for load balancing. It works great.

Since migrating over to vSphere, we're seeing a significant performance boost due to the fact that we've migrated over to an all-flash vSAN array. Previously we were running external storage SAN over fiber channel. We saw a significant increase, I would say at least a 50 percent increase, in our speeds due to our vSAN running on all-flash. It's been a huge improvement.

The way that vSphere increases our availability in our organization is that it allows us to run our critical business workloads, keep them highly-available, run them at speed, and easily scale when we need to.

The most valuable features for me are a very easily scalable infrastructure. I can have a couple of hosts to do basic workloads. I can have a lot of hosts to do a lot of workloads. vSAN integrates my storage so I don't need an external storage SAN. I love having everything integrated in the same UI. The new HTML5 interface doesn't require any plugins anymore and it's super-fast. Really liking that change.

In terms of the built-in security features that I'm using, currently I am using vSAN Encryption, using an external KMS server, and it works great. It's pretty easy to set up, very easy, especially in the UI, to integrate that and get that set up.

The way that I find vSphere simple and easy to manage is that the interface is all laid out for you. You've got various different views based on what you want to do in the UI. You have your Hosts and Clusters view, if you're doing something where you need to manage at the cluster level. You can manage at the host level in there. If you're doing something very VM-specific or on a vApp level, you can go into the VM and Templates view. It's very easy to scale and use what you need to use.

An improvement could be allowing a "dark mode" for the interface. I think the HTML5 client is a little bit hard to read. It's all white. It's a little bit bright on the eyes. A lot of us IT guys view in the dark.

The stability in our vSphere environment has gone very well. We have never actually had an outage. Due to the HA failover capabilities of the cluster, the High Availability of vSAN, Distributed Resource Scheduler allowing you to basically vMotion VMs and balance your loads across all your clusters, it's been very highly available. We've never had an outage or an issue; never any kind of a data loss incident, even when we were running external storage as well.

Scalability works pretty well. You can start out at a couple of hosts, based on your business needs, your budget. That's probably the base recommendation I would start out at for having some of the DRS and HA failover capabilities. But if your business grows, you can easily add a host and a cluster and expand your capabilities on storage and compute. If you're running vSAN, you can run on the storage side, too.

I have had several instances where I've had to use Global Support Services. They're always great. They are very knowledgeable. If they don't know the answer, they can easily escalate to another engineer and help you out and get the problem solved, usually pretty quickly.

I was not initially involved in the vSphere setup at my current company; that predated my joining the company. But I've brought up the secondary environment and integrated vSAN at that company, and setup was straightforward. It's pretty easy to get everything set up and get things done. I've done that many times in production, and torn down and rebuilt the Home Lab many times. It's pretty straightforward.

We do not currently use VMware Cloud on AWS.

If I had to rate vSphere from one to ten - version 6.7 - I would say right now it's probably about a ten.

We have three different types of environments: internal cloud, managed hosting, and VDA. We use VMware vSphere as the main product to accomplish this.

VMware is now the main backbone in our company.

We are not using VMware cloud on AWS. We are in PoC mode. We may use it in another six months to a year.

vSphere helps our organization. Initially, we don't have an internal Cloud. We have an internal cloud, which is four years old now. We have 8000 to 9000 VMs standing in our internal cloud. We also implemented VDA using a VMware vSphere. So, it has been an absolutely pleasure having vSphere.

We provide a service to our internal customers for our development center. We have internal cloud developers. If they require 1000 VMs or 500 VMs, and in the background, we're using a vSphere VMware product. 

The most valuable feature is performance, especially the 6.7 version. 

We were looking for content library options for templates and were happy that VMware introduced it in 6.7 version. 

I like the speed and the quickness of the boot in the newest version of vSphere.

The mission-critical applications in our company, like SAP, Siebel, and a lot of financially related applications are running. Our developer uses most of animation, etc., and we are using the vSphere for that.

We have seen a performance boost compared to the previous versions, like a 5.1, five years ago. It has gradually increased. Previously, we hadn't migrated any database, like SQL or Oracle, into VMware. However, we are planning to now. We are moving forward because a lot of new features are now available on 6.7. 

We are doing a PoC, which we are happy about now. We may move over the database into our VMware environment.

It is simple to manage. However, some of our operation teams, they are used to the desktop line, but VMware removed it in the previous version. Initially, we had an issue on the flash, but now we are happy. With VMware moving to HTML, it's really fast. We did a bit of version testing, and it's really fast and easy to use now.

I have seen some sessions for version 6.7 covering its improvements, which I was looking for, mainly the content library. Our requirement is to move our templates from one location to another location. Previously, this was not available. We are happy this was introduced. 

Another thing is the flash. However, in 6.7, they completely removed it and they are bringing in the HTML. Let's see, as I haven't tried the 6.7 update yet. I hope it will satisfy everything from our point of view.

The stability is good. We have different clusters based on the load of the application and requirements. We can slice the cluster.  

Since we have an internal cloud, suddenly people may require 1000 or 2000 VMS in something. We have options to analyze and make sure we have enough scalability. 

We have some issues but so far it has been good.

We use tech support, which is okay. We used to have a hard time, but at this time, we are happy.

Previously, for monitoring, we use other products. Slowly, we are moving to vRealize now. It depends on our requirements and budget. 

When 5.5 went to 6, we found it a bit difficult because they changed the model. 

Now, we are okay. We have gotten used to it, because it is a new platform. Initially, it was difficult, but now we are okay.

Five years ago, we planned to move from a physical to virtualization environment. We evaluated a lot of other hypervisors, did some PoCs, etc. We decided on VMware. For the past six to seven years, it's been a big journey. 

I would rate vSphere as a nine out of 10.

I will recommend the solution, but there are some steps to take first. There are some VMware videos to view and some KB articles to read, which are available, regarding compatibility. I would recommend them to go through everything. Go through the KB articles, then I will recommend them to implement that one.

An important criteria for choosing a vendor is evaluating how a company behaves. We will review their past history, the current market, and the value of that product. Then, we will see whether that product can used for our requirement. Based on that, we choose our vendors.

We haven't started using the VM encryption. We are in the very initial stage, doing a PoC for it and also the UEFI Secure Boot. These are options that we are trying. Let's see how they will work, and we're looking forward to their results.

Server virtualization.

Consolidation and normalization.

Distributed vSwitch, and vSphere.

Improvement in price.

We started using this just for virtualization, but now we have gone into creating private cloud features for our customers. 

Gathering all of the hosts together to create one single pool across the enterprise is a terrific feature.

It needs to integrate better between multiple modules. 

I would rate the scalabilty as an eight out of ten. 

The setup was easy. The deployment did not take much time, as long as it was properly planned. The planning must be from an experienced side and user-acceptance front. It should not take more than two months of time. 

We used system integrators. 

The pricing is a bit complex.

VMware alone cannot offer all the features that customers require. There are times when the differential cost of the customer is not feasible. In addition, there are times when the requirements, in terms of API, build up and the connectivity to the outside world is more important. People need to decide on their own whether this is a good solution or if an OpenStack solution is the better choice.