{"id":13624,"date":"2024-02-29T10:27:19","date_gmt":"2024-02-29T13:27:19","guid":{"rendered":"https:\/\/made4it.com.br\/vmware-x-proxmox-which-choose\/"},"modified":"2024-03-26T10:18:36","modified_gmt":"2024-03-26T13:18:36","slug":"vmware-x-proxmox-qual-choose","status":"publish","type":"post","link":"https:\/\/made4it.com.br\/en\/vmware-x-proxmox-qual-choose\/","title":{"rendered":"VMware vs. Proxmox &#8211; Which one to choose?"},"content":{"rendered":"\n<h3 class=\"wp-block-heading\">\n          <strong>Introduction <\/strong>\n        <\/h3>\n\n<p>When we talk about servers today, we automatically associate them with virtualization. Gone are the days when we used bare-metal servers to run just one application. With the ease of virtualization and better use of server resources, it has become almost mandatory to use your server with some virtualization software.  <\/p>\n\n<p>Currently, two big names are leading the way when it comes to virtualization: <strong>VMware and Proxmox<\/strong>. Even more so after the news of <strong>VMware<\/strong>&#8216;s sale <strong>to Broadcom<\/strong>, this subject has become even more hotly debated. And the question on most people&#8217;s minds is:<strong> VMware or Proxmox?<\/strong> <strong>Which virtualizer to choose? Which is the &#8220;best&#8221;?  <\/strong><\/p>\n\n<p>Throughout this post, we&#8217;ll make some comparisons between the two virtualizers so that you can decide which one best suits your needs and, of course, get to know the main features of each one!  <\/p>\n\n<h3 class=\"wp-block-heading\">\n          <strong>Overview of services  <\/strong>\n        <\/h3>\n\n<p><strong>Proxmox <\/strong>is an open-source virtualizer updated and maintained by <strong>Proxmox<\/strong>. It is based on Debian and uses KVM\/QEMU as a virtualizer and LXC for containers. It <strong>stands out because it&#8217;s free<\/strong> and has a wide range of features, so the limit to how much you can grow and evolve is directly linked to your knowledge of the tool. <strong>Proxmox <\/strong>also stands out when it comes to compatibility with older hardware, as it is directly linked to the Linux kernel being used.  <\/p>\n\n<p><strong>VMware <\/strong>is a proprietary code virtualizer and has recently been updated and maintained by <strong>Broadcom<\/strong>. Currently, it is no longer <strong>free<\/strong>, but only requires a license to use it. It uses proprietary server virtualization technologies as a virtualizer, and its high performance and stability are undeniable. It stands out for its simple interface and features that add a lot to large scenarios. The compatibility part of <strong>VMware <\/strong>depends on the version it is in, and the newer the version, the less compatibility with hardware considered to be old.  <\/p>\n\n<h3 class=\"wp-block-heading\"><strong>Ease of use<\/strong> <\/h3>\n\n<p><strong>Proxmox<\/strong>, at first glance, may seem confusing and difficult, especially since some configurations require integration with the <strong>CLI.<\/strong> However, once you get used to its interface and the functions you need, <strong>everything becomes easier<\/strong>. It also has excellent documentation that covers all the available functions. It also has paid support, which users can choose whether or not to purchase, and has a good active community.  <\/p>\n\n<p><strong>VMware <\/strong>has a user-friendly and more objective interface. With just a few clicks, you can get a VM up and running. On the other hand, if you want access to other features, you will need to purchase a new license and\/or configure other software (e.g. VEEAM, vCenter). It has excellent documentation and several KBs (knowledge base) explaining various problems that can occur.  <\/p>\n\n<h3 class=\"wp-block-heading\"><strong>Performance<\/strong> <\/h3>\n\n<p>Both services perform well. <strong>VMware <\/strong>stands out for running its OS in RAM memory, thus allowing you to better navigate its interface. Other than that, both are very close in terms of performance in mixed scenarios, using Linux and Windows VMs and different types of storage.  <\/p>\n\n<h3 class=\"wp-block-heading\"><strong>Scalability<\/strong> <\/h3>\n\n<p>Both virtualizers allow you to increase the resources (CPU\/MEM\/DISK) of your VMs without any problems, and if necessary, even increase internal resources such as adding more space to some of your VMs&#8217; datastores or disks.  <\/p>\n\n<p>Now, if you acquire another server and want to increase your server infrastructure, <strong>Proxmox handles the addition of a new server to your system better<\/strong>. While <strong>in VMware this server would be isolated and a new service (vCenter) would have to be configured<\/strong> to unite the servers under its management, in <strong>Proxmox <\/strong>all you have <strong>to<\/strong> do is create a Cluster and register the new server in the cluster (literally just these two configurations).  <\/p>\n\n<h3 class=\"wp-block-heading\"><strong>Features and functionality<\/strong> <\/h3>\n\n<p>Both services have similar features and functionalities. In the case of <strong>VMware<\/strong>, access to them will depend on the license you have, while in <strong>Proxmox <\/strong>it will depend on whether or not the version you are on has support for it.  <\/p>\n\n<p>Examples of some of the features they have in both:  <\/p>\n\n<div class=\"wp-block-group\"><div class=\"wp-block-group__inner-container is-layout-constrained wp-block-group-is-layout-constrained\">\n<ul class=\"wp-block-list\">\n<li>Cluster&nbsp;\n<ul class=\"wp-block-list\">\n<li>Accessible via vCenter in the VMware scenario.  <\/li>\n\n\n\n<li>Accessible from any Proxmox node, no additional software required.  <\/li>\n<\/ul>\n<\/li>\n\n\n\n<li>H.A.  <\/li>\n\n\n\n<li>Storage&nbsp;\n<ul class=\"wp-block-list\">\n<li>Proxmox: LVM, LVM-thin, iSCSI\/kernel, iSCSI\/libiscsi, Ceph\/RBD, ZFS over iSCSI, ZFS (local), directory, NFS, CIFS, GlusterFS, Proxmox Backup Server  <\/li>\n<\/ul>\n<\/li>\n\n\n\n<li>Hyper-Converged Infrastructure (HCI)  <\/li>\n\n\n\n<li>Backup\/Restore&nbsp;\n<ul class=\"wp-block-list\">\n<li>Proxmox: native (Proxmox Backup Server \/ PBS)  <\/li>\n\n\n\n<li>VMware: Need a license or third-party software (VEEAM or others)  <\/li>\n<\/ul>\n<\/li>\n\n\n\n<li>Live Restore  <\/li>\n\n\n\n<li>Migration  <\/li>\n\n\n\n<li>Live Migration  <\/li>\n\n\n\n<li>Storage Live Migration  <\/li>\n\n\n\n<li>SnapShot  <\/li>\n\n\n\n<li>Replication  <\/li>\n\n\n\n<li>Template and Clone  <\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\"><strong>Costs<\/strong> <\/h3>\n\n\n\n<p>We did a simulation for a server with 1 CPU (Socket) and these were the costs  <\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>VMware Cloud Foundation: US$1400  <\/li>\n\n\n\n<li>VMware vSphere Foundation: US$540  <\/li>\n<\/ul>\n\n\n\n<p>For Proxmox you don&#8217;t need a license to use it, only direct support from the manufacturer <strong>if you want to<\/strong>.<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Proxmox VE Basic Subscription 1 CPU\/year (Optional): \u20ac 340.00 per year (R$ 1800)  <\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\"><strong>Case studies and practical examples<\/strong> <\/h3>\n\n\n\n<p>Let&#8217;s assume a few scenarios and understand where it is interesting to implement VMware or Proxmox.  <\/p>\n\n\n\n<p>PS: I&#8217;m going to draw attention to the <strong>on-premises <\/strong> scenarios of <strong>Internet providers! <\/strong> <\/p>\n\n\n\n<p><strong>Scenario 1:<\/strong> <\/p>\n\n\n\n<p>I have a used server from before 2015 and would like to add it to production to virtualize 5 non-critical VMs.  <\/p>\n\n\n\n<p><strong>VMware scenario:<\/strong> <\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Purchase license  <\/li>\n\n\n\n<li>Talvez n\u00e3o conseguir executar a vers\u00e3o mais recente por conta de incompatibilidade de hardware!&nbsp;\n<ul class=\"wp-block-list\">\n<li>CPU not supported  <\/li>\n\n\n\n<li>Network card not supported  <\/li>\n<\/ul>\n<\/li>\n\n\n\n<li>Configuring VMs  <\/li>\n\n\n\n<li>Configure a backup scenario using one more VM with the VEEAM Backup software (Free Version Supports Backup\/Replication of 10 VMs)  <\/li>\n\n\n\n<li>Configure a Zabbix Agent on the Backup VM to monitor the Backup.  <\/li>\n\n\n\n<li>Monitoring via API (Integration by Zabbix)  <\/li>\n<\/ul>\n\n\n\n<p><strong>Proxmox scenario:<\/strong> <\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Install Proxmox  <\/li>\n\n\n\n<li>Configuring VMs  <\/li>\n\n\n\n<li>Configure the tool&#8217;s native backup  <\/li>\n\n\n\n<li>Monitoring via API (Integration by Zabbix)  <\/li>\n<\/ul>\n\n\n\n<p>In other words, in both scenarios you will be able to implement your scenario. Of course, in the case of <strong>VMware<\/strong>, in addition to the price of the license, you have to pay <strong>attention to the model of your server and especially its year<\/strong>.  <strong>Very old servers are not supported by the latest versions of VMware<\/strong>, and you will have to make more investments to support the backup scenario if you have more than 10 VMs in your scenario.  <\/p>\n\n\n\n<p><strong>Upgrade Scenario 1:<\/strong> <\/p>\n\n\n\n<p>I saw that the virtualization worked very well, and now I want to add more VMs, but now there will be critical VMs, and to run these VMs I upgraded and bought a new server.  <\/p>\n\n\n\n<p><strong>VMware scenario:<\/strong> <\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Purchase license for new server  <\/li>\n\n\n\n<li>Configuring VMs  <\/li>\n\n\n\n<li>Add VMs to backup policies (if more than 10 VMs, I need to buy a VEEAM license)  <\/li>\n\n\n\n<li>If I want to move to a cluster scenario to improve my management, I need to purchase the license for the vCenter software  <\/li>\n\n\n\n<li>Setting up a new VM for vCenter  <\/li>\n\n\n\n<li>Cadastrar os servidores no vCenter&nbsp;\n<ul class=\"wp-block-list\">\n<li>PS: If vCenter stops, I don&#8217;t have access to my cluster, but I still have access to my servers.<\/li>\n<\/ul>\n<\/li>\n<\/ul>\n\n\n\n<p><strong>Proxmox scenario:<\/strong> <\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Install <strong>Proxmox <\/strong>on the new server  <\/li>\n\n\n\n<li>Configuring VMs  <\/li>\n\n\n\n<li>Add VMs to the backup policy  <\/li>\n\n\n\n<li>You can set up a <strong>Proxmox Backup Server<\/strong> and share it between servers.  <\/li>\n\n\n\n<li>If you want, you can create a <strong>Cluster <\/strong>and add both servers.  <\/li>\n\n\n\n<li>With the cluster configured, you can migrate VMs from one side to the other.  <\/li>\n\n\n\n<li>As you have two servers in a cluster, you could think about setting up <strong>High Availability (H.A) <\/strong>.  <\/li>\n\n\n\n<li>As we have two servers in a cluster, you can configure replication if you are using storage with a ZFS file system.  <\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\"><strong>Conclusion<\/strong> <\/h3>\n\n\n\n<p>Anyway, we&#8217;ve seen that <strong>Proxmox and VMware<\/strong> are very similar and can deliver the same result, as long as you meet a few requirements!  <\/p>\n\n\n\n<p><strong>It all depends on the size of your infrastructure and its criticality.<\/strong>  The first thing we have to take into account is the investment I&#8217;m going to make in licenses. If I choose to use <strong>VMware<\/strong>, what if that investment couldn&#8217;t be more useful in some other area (for example, upgrading some part of my internal server)?  <\/p>\n\n\n\n<p>My recommendation is this: if your infrastructure is 100%, with new servers that don&#8217;t need to be upgraded, and you can afford the licenses, go with <strong>VMware<\/strong>, because it will give you the best in the virtualization world.  <\/p>\n\n\n\n<p>However, if you have a small\/medium-sized infrastructure, <strong>Proxmox <\/strong>will serve you VERY well, as we already have access to all its features from the moment we install it. Unlike <strong>VMware<\/strong>, which requires us to invest in licenses, we can take that investment and improve our infrastructure, whether we&#8217;re buying new disks, memory or even a new server.  <\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Finalization<\/h3>\n\n\n\n<p>In the comparison between <strong>VMware and Proxmox<\/strong>, the right choice depends on the size and needs of your infrastructure. If your structure is robust and you can afford to invest in licenses, <strong>VMware <\/strong>offers the best in virtualization. For small\/medium businesses, <strong>Proxmox <\/strong>stands out, delivering all the functionality right from installation. <strong>Whichever path you choose, Made4it is ready to support you in implementing or migrating from VMware or Proxmox. <\/strong>Count on us to optimize your virtualization and boost your infrastructure.<\/p>\n\n\n\n<div class=\"wp-block-buttons is-layout-flex wp-block-buttons-is-layout-flex\">\n<div class=\"wp-block-button\"><a class=\"wp-block-button__link has-vivid-cyan-blue-background-color has-background wp-element-button\" href=\"https:\/\/made4it.com.br\/en\/\" target=\"_blank\" rel=\"noreferrer noopener\">Find out more about our services<\/a><\/div>\n\n\n\n<div class=\"wp-block-button\"><a class=\"wp-block-button__link has-luminous-vivid-orange-background-color has-background wp-element-button\" href=\"https:\/\/made4it.com.br\/en\/consulting-in-proxmox\/\" target=\"_blank\" rel=\"noreferrer noopener\">Proxmox Consulting<\/a><\/div>\n<\/div>\n<\/div><\/div>\n","protected":false},"excerpt":{"rendered":"<p>Introduction When we talk about servers today, we automatically associate them with virtualization. Gone are the days when we used bare-metal servers to run just one application. With the ease of virtualization and better use of server resources, it has become almost mandatory to use your server with some virtualization software. Currently, two big names [&hellip;]<\/p>\n","protected":false},"author":13,"featured_media":13613,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"postBodyCss":"","postBodyMargin":[],"postBodyPadding":[],"postBodyBackground":{"backgroundType":"classic","gradient":""},"footnotes":""},"categories":[1,786,799,798],"tags":[788,800,787],"class_list":["post-13624","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-nao-categorizado","category-proxmox-en","category-virtualization","category-vmware-en","tag-proxmox-en","tag-virtualization","tag-vmware-en"],"aioseo_notices":[],"_links":{"self":[{"href":"https:\/\/made4it.com.br\/en\/wp-json\/wp\/v2\/posts\/13624","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/made4it.com.br\/en\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/made4it.com.br\/en\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/made4it.com.br\/en\/wp-json\/wp\/v2\/users\/13"}],"replies":[{"embeddable":true,"href":"https:\/\/made4it.com.br\/en\/wp-json\/wp\/v2\/comments?post=13624"}],"version-history":[{"count":7,"href":"https:\/\/made4it.com.br\/en\/wp-json\/wp\/v2\/posts\/13624\/revisions"}],"predecessor-version":[{"id":13933,"href":"https:\/\/made4it.com.br\/en\/wp-json\/wp\/v2\/posts\/13624\/revisions\/13933"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/made4it.com.br\/en\/wp-json\/wp\/v2\/media\/13613"}],"wp:attachment":[{"href":"https:\/\/made4it.com.br\/en\/wp-json\/wp\/v2\/media?parent=13624"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/made4it.com.br\/en\/wp-json\/wp\/v2\/categories?post=13624"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/made4it.com.br\/en\/wp-json\/wp\/v2\/tags?post=13624"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}