IBM Cloud for VMware
Solutions is designed to make cloud adoption easier, allowing the user to optimize the
value of existing on-premises infrastructure, while leveraging the
same tools, technologies and skills in the cloud. The solution provides rapid scalability,
deployment in 35+ global data centers and access to disaster
recovery, backup, security and compliance solutions from an array of ecosystem
partners. To address varying workload needs, IBM Cloud…
$0
IBM Cloud Object Storage Cross-Regional Smart Tier 1 GB (hourly)
Windows Server Failover Clustering
Score 10.0 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.
N/A
Pricing
IBM Cloud for VMware Solutions
Windows Server Failover Clustering
Editions & Modules
Add-on
$0
IBM Cloud Object Storage Cross-Regional Smart Tier 1 GB (hourly)
On-demand
$0
0.25 IOPs 1 GB
Reserved (monthly or 730 hours)
$0
0.25 IOPs 1 GB (Per gigabyte of storage (hourly))
Add-on
$0
IBM Cloud Block Storage 1 GB (hourly)
On-demand
$0.01
Per vCPU (hourly)
On-demand
$0.09
Per gigabyte of network and bandwidth egress (monthly)
Reserved (monthly or 730 hours)
$0.09
Per gigabyte of network and bandwidth egress (monthly)
VMware Cloud Foundation for Disaster Recovery environment, when the client needs to deploy a pay-as-you-go service or if they need to migrate SAP workloads, you can use VMware Cloud Foundation for Classic and VPC. We are the unique SAP-Certified VMware cloud service provider.
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.
The presentation is first rate. Our on-prem climate was continually experiencing slack and general languor. With IBM running everything, it's much smoother.
Start another group as little as one ESXi worker or scale a current bunch.
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.
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.
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.
It is easy to use and setting it up is simple. The only con is that the pricing is a little bit high as well as documentation is a little low; so we had to do some personal learning to be able to fully utilize the product, or hop on the phone with someone.
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.
Overall, just a great experience here. No one in my opinion gets a perfect 10/10 rating (no one is ever perfect), so 9/10 is probably as good as it gets! From initial planning to post implementation support, the IBM Cloud and professional services has been there for my group as much as we have needed them. Great job!
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.
IBM professional services helped us plan and implement the project with great success. They guided the project from planning, scoping, pre-implementation, testing, roll-out, then production and post-production support. We were very impressed with their knowledge of VMware and really appreciated their desire to make our project a success. I would highly recommend them!
IBM Cloud for VMware Solutions stacks up against them, we fully agree there are so many features in IBM cloud for VMware Solutions that make it unique and different. The system provides us hypervisor security level and the system even has live backup and storage capacity of data. This system provides us with accuracy that helps us to reduce errors and vulnerability.
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.
It has a positive impact on the cost required to maintain our vSphere environment by allowing us to get rid of our vsphere hardware and not worry about maintenance either.
There have been very few negatives, but one would definitely be the open-ended cost associated with cloud products in general.
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.
