VMware vCenter is an advanced server management software that provides a centralized platform for controlling vSphere environments for visibility across hybrid clouds. VMware vCenter is no longer sold as a standalone product and is now available as a part of VMware Cloud Foundation.
$6,044
per year
Windows Server Failover Clustering
Score 9.2 out of 10
N/A
Windows Server Failover Clustering (WSFC) is a group of independent servers that work together to increase application and service availability.
We fell the Windows Server Failover Clustering was better than the Oracle Real Application Clusters. Although the Oracle Real Application cluster provided an active setup it was more unstable. On more than one occasion a split brain issue had occurred when both nodes thought …
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 …
If you are already on Windows Server and are using a compatible Role and hardware (Ex. Shared Storage), Windows Failover Clustering is free (If you already run Windows Server) and doesn't require much effort to put in place even as an afterthought.
It isn't the best on the …
The VMware vCenter server is very useful in maintaining the CPU/RAM/datastore resources are balanced when there are multiple ESX/ESXi host servers. It is clear what resources are being used, and it is easy to migrate VMs to different ESX/ESXi hosts. Being able to remotely connect to the VM servers in vCenter when you cannot have other remote connections helps in maintenance and troubleshooting.
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.
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.
Currently, the HTML 5-based vSphere Client lets you manage the essential functions of vSphere from any browser, however, it would be nice if they would port all management functions over to the HTML 5-based Client.
Performing updates and upgrades to the infrastructure is a bit challenging for someone that may not be as intimate with vSphere. I think the updates/upgrades should be more integrated into the UI and provide the ability to push to the hosts, etc...
It would also be nice to have a more robust snapshot management tool to prevent snapshot overgrowth. It would be nice to be able to set a lifespan for the snapshot(s)
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.
We are very dependent on this software, it has become a much needed tool to perform the daily tasks that are required to maintain the virtual server environment. VMware has become very pricey over the years, so we are looking for alternatives for cost savings strategy, but nothing has been found to be on par to what we are currently using
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.
I work with vCenter for 10+ years and i love it. I can find my way around and can help building and expanding the platform. It is easy to use and there are a lot good communities for the extra support when needed. Even the Homelab community is of great value.
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.
VMware support has always been fantastic and they have been invaluable in solving tougher issues that have been run into. Most of the time, any oddities encountered are fixed by available updates. This can be deduced by support quickly with logs within vCenter. We have not run into something yet that support was unable to help with. They either have a solution already, or they are able to find one quickly.
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.
Since moving away from the Windows Server hosting the vCenter application and instead using a virtual appliance, it has become much easier to implement and deploy the new versions. We can easily create a snapshot or clone of the vCenter vApp to ensure any problems encountered during the upgrade can be mitigated with a fall back to the old version to prevent unscheduled downtime.
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.
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.
