Everything You Wanted to Know About the Differences between VMware and Hyper-V – Part 2

Everything You Wanted to Know About the Differences between VMware and Hyper-V – Part 2

In the first part of this blog series, we started looking at those subtle differences between the two products that can make all the difference. Like most, not dissimilar products, it’s really horses for course. So, with that imagery in mind, let’s take a look at that most crucial of deciding factors, pricing, and see which one is really the safest bet.

Show Me the Money

When you start with the special edition and you have some experience with Windows Servers and your infrastructure is probably based on Windows, then it can be advantageous to use your existing knowledge base. In addition to this,  it will also be cheaper for you, there is no denying that. The difference is even more noticeable when you use Microsoft technologies because imagine you would use Windows Server on top of VMware software, then you would have to buy a VMware license as well as Microsoft licenses, and that results in very expensive “entertainment”. But if you use Linux, then you can see quite similar pricing between VMware and Hyper V. Yet, if your company focuses on Microsoft technologies, it makes extra sense to add just Hyper-V on top of your Windows Server, and then you’re good to go.

I Wanna Grow with the Flow

In terms of scalability, they are both very similar and there are no real limits on how many CPUs you can have and how many terabytes of RAM you can add. Their limit is so high nowadays, that they are not relevant anymore for most people. And with each new version, the limits rise and become so high that those differences are negligible and you can have thousands of virtual machines in one cluster.

But It Wasn’t Always That Way?

In the past, VMware was really good compared to Hyper-V. An example being, when you wanted to make a snapshot, which is a normal operation, and do so without any warning, you couldn’t delete the snapshot while the virtual machine was running. In some cases, when you created a snapshot, you then had to shut down the virtual machine for eight hours or so. Nowadays, this is no longer the case, but due to historical and current preferences, VMware still enjoys a market share of over 50%.

And also previously, when you wanted to start with virtualization, you had to typically buy the physical storage, and the storage array was typically the most expensive part and also the least reliable. Nowadays, what’s really good is you can use hyper-converged infrastructure, which is a fancy name for getting rid of your storage. What this means is that you again put some discs in your server and you create your cluster from your server and your data is actually replicated in real time to another server, so even if your server breaks down, you still have a backup of your data. So this technology allows you to get rid of your expensive storage array, plus it is faster. And both Microsoft and VMware have this hyper-converged infrastructure technology.

Just Want to Hear the Facts

So, after looking at all of these pros and cons, it could be said that there is little to distinguish between the two. But, considering the fact that not only the market favors VMware and also, that only VMcom combined with VMware gives you that level of multi-tenancy and true-granular level storage and backup, in my opinion, VMware is a natural choice. To see for yourself all the benefits VMcom brings to your virtual machine environment, why not take our solution for a free spin? As you will discover, the advantages really speak for themselves!


TRY NOW

1 thought on “Everything You Wanted to Know About the Differences between VMware and Hyper-V – Part 2”

Leave a Comment