VMware vSphere vs. Windows Server Failover Clustering

vSphere is well suited for multiple VMWare hosts and can be very useful in larger enterprises where vMotion is used to load balance and failover running virtual machines. In smaller businesses with one or two hosts then the features can be overkill. The addition of virtual TPM support is a very nice addition to provide vm security in a more Microsoft supported methodology.

Incentivized

Windows ServerFailover Clustering works very well for applications that can sustain a short disconnect when failing over. It works, and works well, in providing single-node applications HA, meaning an active/passive setup. It is not a load balancing solution. Use NLB for that. Another area that it works well is when used in combination with Hyper-V. We set our Hyper-V hosts up as clusters, and those clusters also host clusters for SQL Server and other enterprise class applications like BMC's Control-M/Enterprise and Control-M/Server.

Incentivized

• vMotion that provides seamless movement of Virtual Machines between physical hosts and datastores.
• Ease of Manage: vCenter provides very good management experience to the users.
• It provides hassle free upgrade of versions, which requires good planning.
• Easy to manage datastore, networks, CPU and memory resources.
• It also allows to convert the physical machine and bring it to vSphere Environment with minimum effort.

Incentivized

• Live Migration of VMs between hosts. If you have sufficient network bandwidth, it is fast and I never had a failed live migration break the VM or kill it. Worst case is the live migration will fail (not enough RAM for example) but the VM always stayed up.
• Windows Server Failover Clustering enables Scaleout Storage, which is probably the coolest feature Microsoft has to offer at this moment. It gives you Active-Active SMB file shares which can now be used by most Microsoft Services like MS SQL, Hyper-V, etc. and clients if Windows 8+
• Cluster Validation is really complete and easy to understand. The validation gives you comprehensive error messages that help to diagnose and fix rapidly to get your Failover Cluster running in no time.

Incentivized

• Allow enable EVC without requiring host shutdown
• More detail in recent tasks. Instead of just showing a task called "Reconfigure virtual machine" also have a link to more detailed information as to what was reconfigured, changed or removed.
• Allow searching tasks or events

Incentivized

• The setup of the Windows Server Failover Clustering is complex, requiring different networks and multiple network cards.
• Better integration between the Windows Failover clustering and Hyper-V. Unlike VMWare you have to make changes to two places instead of just one panel.
• I wish there was a web portal to manage the cluster. Instead you have to remote desktop into the VIP address and go to the Cluster manager.

Incentivized

We are constantly looking for change that will benefit our company. We are not ones to stick with a product simply because it is what we know, but rather looking for what fits us best. We can't imagine another product on the market today doing a better job of handling our infrastructure than vSphere.

It has proven its value to us both for maintaining SLAs and providing the ability to perform much needed and regular systems maintenance without taking applications offline for more than a few seconds.

Incentivized

It is a highly documented suite. If you are unsure of how to do something, a simple search will yield hundreds of results showing you how to do it. Support is also available if you need to talk to an expert.

Incentivized

Usability of Failover Clustering on Windows Server is generally good. Failover Clustering console is not hard to understand if the complexity of the product is taken into account. Most of the task on the Cluster can be done via PowerShell, so automation is possible and not hard (PowerShell is very intuitive). Configuring storage is the hardest and most confusing task during cluster configuration, so storage configuration should be planned in advance. Cluster Validation Wizard is verbose but most of the errors are easy to understand.

Incentivized

I rarely ever have to contact support and when I do need to resolve an issue, there is always an abundance of kb articles and research information available that can help quickly resolve the issue. Depending on the type of support contract you have, you may get support from some offshore group in another country and this could be a little challenging because of the language barrier.

Incentivized

Online documentation is excellent. Everything I needed to know, I learned from the online documentation. I haven't used phone support as I haven't needed to but would presume it is similar to Microsoft Support for other products that I've used. Phone support from Microsoft is hit and miss. It depends on who you get. That said, my rating is based on the online documentation.

Incentivized

Just make sure that when you implement, that the person implementing truly knows what they are doing and has a plan of action coming in. Since our initial implementation using a consulting service, I have implemented a few vSphere just from what I learned at the initial implementation and use over time, and the person implementing really needs to know what they are doing or you will miss out on features that may help you down the line

vSphere has a lot more feature sets than Hyper-V but at a much higher cost of entry versus MS Hyper-V. I have not been able to play with Hyper-V as much as I would have liked, but the setup and ongoing maintenance seems to be easier in vSphere than with Hyper-V

Incentivized

Both VMware and Microsoft Failover do the job and they both do it extremely well. For many bussiness and environments though, they will have the existing investment in a Microsoft environment and Microsoft infrastructure. The introduction of VMware will or may achieve the end result however it introduces new dimensions like support, licensing, documentation and ensuring the support team are trained.

Incentivized

The contract terms are very clear and can be updated as per the project requirement. Customer support is also included in the contract which help us to troubleshoot critical issues very easily. Training included in contract will really help the client team to empower and hands-on on the latest updates and enhancements

As I said earlier, they're always ready to understand our issues and propose the best and most appropriate solution for issues all the time. The security patches solution is accordingly to the business needs. Another scenario is their Knowledge Base where
they're many articles that help you in order to solve something which
is wrong.

Incentivized

• Having vSphere helped my business quickly recover from a ransomware attack which would have crippled us for weeks if we were not virtualized. I think the ROI on something like that is immeasurable.
• vSphere has allowed my company to purchase bigger server hardware to host 3 or 4 virtual servers, which was at a cost much lower than buying 3 or 4 server hardware boxes, saving us thousands each time we need to upgrade hardware.

Incentivized

• Failover Cluster gives us the power to do updates or hardware upgrade / change without having to create an outage. Which permit us not to work night shifts.
• By creating one cluster with all Hyper-V servers, it enabled us to move VMs via live migration between host to balance RAM usage which was time consuming and took a lot of time over network before.
• It created some problems that caused us to have to investigate quite some time before finding the cause. We encountered dll locking that caused the Failover Cluster to force-restart a host. Logs are really not the strong point of Failover Cluster Manager, and even Microsoft Support wasn't able to help much. We had to find the problem ourself.

Incentivized