What is our primary use case?
My main use case for Hyper-V is managing a virtualized environment for a large company with more than 300 virtual machines using high availability with a three-node cluster. To perform maintenance, I usually migrate these VMs through live migration to leave one node passive and carry out the necessary maintenance on that host node.
A recent situation where I needed to perform maintenance using Hyper-V involved applying a security patch released by Microsoft without stopping any of the environments. I performed a migration on a three-node cluster, leaving one node passive without any VMs. The other two nodes were able to support all remaining VMs. While that node was passive, I applied the security patch and restarted it. I then performed a reverse migration to bring the VMs back and completed the same process on the other nodes to perform the update.
I usually also use SCCM to do centralized management of these VMs and I make extensive use of checkpoints, which in a VMware environment would be called snapshots. I use this checkpoint practice frequently before doing any kind of maintenance.
What is most valuable?
The best features that Hyper-V offers are its practicality and self-explanatory nature. In terms of configuring virtual switches, it is very good, very functional, and performs well. In terms of checkpoints and instant recovery, it also responds very well. In terms of the possibilities of creating any type of VM with numerous operating systems, it is also quite solid in that respect.
Regarding the checkpoint feature, it contributes to my day-to-day work in that I have needed to restore a virtual machine from a checkpoint countless times. We have a rule and checklist before doing any kind of maintenance or action in the production environment: there must be a checkpoint that is documented as having been taken before that maintenance. Without this evidence, it is forbidden to do any kind of maintenance in the production environment. This requirement exists because we have had needs to perform instant recovery following some updates or releases that did not work out.
Hyper-V has had a positive impact on my organization in terms of organization, visualization, and monitoring. Our observability is able to collect all the data in a highly performant way from all Hyper-V VMs, and we do not have any communication problems in relation to it.
This improved observability has impacted efficiency and decision-making in my consultancy positively. I have noticed time savings and a reduction in incidents. Previously we worked more in a monitoring context, so all actions were reactive. When we started to implement observability, we brought with this concept automations that could perform some preliminary actions even before the problem occurred. This concept of observing to have a proactive rather than reactive response brought us many benefits and provided us with a guarantee of quality and performance of the environments with early action even before some type of problem or impact occurred.
What needs improvement?
Hyper-V could be improved in terms of performance of live migrations. I notice that in VMware, vMotion, which is the same concept as live migration, is faster than in Hyper-V. It is not that it does not work, but in terms of performance, VMware ends up being better for these virtual machine moves.
I do not think there is anything else I would like to add regarding necessary improvements related to the interface, stability, or support. The interface is great and very intuitive. Support is also very quick and functional from Microsoft when a problem occurs. Once the environment is very well configured, there should not be problems in Hyper-V. The main area I would improve is mostly the performance of virtual machine migrations. If this migration performance were improved, I believe Hyper-V would reach a perfect score.
For how long have I used the solution?
I have been using Hyper-V since 2016, which has been six years.
What do I think about the stability of the solution?
Hyper-V is totally stable in my environment. Once very well configured, it is completely stable.
What do I think about the scalability of the solution?
Hyper-V's scalability in my environment is continuous. The environment does not stop growing, and it grows not only in the production context but also in the test, development, and staging context.
How are customer service and support?
The customer support provided by Microsoft for Hyper-V is great. The engagement process works very quickly, reporting is also very fast, and normally in 90 percent of cases, there is always a resolution to our problems.
Which solution did I use previously and why did I switch?
When I arrived at the company, they were using VMware. However, VMware licensing is even more expensive, and they were using a free version that had very few features with practically no snapshot features or migration features, so it was quite chaotic.
What was our ROI?
We have already had a return on investment and payback, mainly in relation to environment performance. After we set up the environments in the Microsoft ecosystem with part of the production environments in Azure and part of the development, test, and staging environments on-premises, all synchronized using Hyper-V to manage these VMs, we had this payback because the environment is now very performant.
What's my experience with pricing, setup cost, and licensing?
My experience with pricing, setup costs, and licensing for Hyper-V is that Microsoft licensing is not cheap. However, it is very worthwhile to have this environment fully licensed once it is very well configured, established, and functional.
Which other solutions did I evaluate?
Before choosing Hyper-V, I did evaluate other options. I know and have worked with VMware for a long time. VMware also delivers everything that Hyper-V delivers. I even think that VMware is more performant in terms of migrations, and its vMotion is much more performant than Hyper-V's live migration. However, VMware licensing is very expensive. In terms of cost-benefit, Hyper-V is worth it for me today.
What other advice do I have?
The advice I would give to others thinking of using Hyper-V is that if they are going to use it in on-premises environments, they should have robust, fully licensed servers and hardware. If they can create a Microsoft ecosystem, that would be the best of all worlds: working in the cloud with Azure, virtualization with Hyper-V, and all Microsoft operating systems and servers. I rate Hyper-V overall as an eight out of ten.
Which deployment model are you using for this solution?
Private Cloud
If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?
Microsoft Azure