Hypervisor + VM licensing model vs Stand Alone VM licenses

Hypervisor + VM licensing model vs Stand Alone VM licenses

Stand Alone VM License
  • Used to license any VM on any Hypervisor platform (KVM, Xenserver, Xen, VMWare or any cloud Platform (Amazon, Google Cloud, Rackspace, etc)
  • Only VMs with root OS install is supported (ie Virtuozzo or OpenVZ containers cannot be backed up using this license and require the node root administrator to install on the node and backup all containers)
  • only limitation is a max size of 32GB RAM for the VM being backed up. VM's larger then 32GB require either the hypervisor + vm licensing model OR can be licensed as a physical server
Hypervisor + VM licensing model
  • Used for cloud platforms where each hypervisor is licensed and then any VM on a licensed hypervisor can be backed up at the per VM rate
  • there is no memory limitation on the VM size on a licensed hypervisor.  so, licensing a hypervisor with 128GB RAM and 2* 64GB VMs is licensed as a single hypervisor license + 2 associated VM licenses.  In a similar manner, if you are hosting 120* 1GB VMs on the hypervisor and wanted to back up 30 of those VMs with Bacula4, you would license the hypervisor and then license 30 associated VM licenses
  • If you originally license VMs as stand alone vms or physical servers and later want to switch to hypervisor + vm licenses, simply purchase the number of hypervisor + associated VM licenses you need, then connect your hypervisors or cloud platform under the "hypervisor" tab in your Bacula4 GUI and the licenses will automatically convert from stand alone VM licenses to hypervisor + vm licenses.  You can then downgrade your physical server and/or stand alone VM licenses
  • current support cloud platforms are OnAPP, Xenserver, SolusVM (please note, for SolusVM, the hypervisor + vm licensing model can only be used for XEN and/or KVM hypervisors.  For OpenVZ, you would purchase a physical server licenses for each OpenVZ master node)
    • Related Articles

    • Hypervisor + VM licensing model vs Stand Alone VM licenses

      Stand Alone VM License Used to license any VM on any Hypervisor platform (KVM, Xenserver, Xen, VMWare or any cloud Platform (Amazon, Google Cloud, Rackspace, etc) Only VMs with root OS install is supported (ie Virtuozzo or OpenVZ containers cannot be ...
    • Adding Servers - Licensing Options

      Please see this article for a description of the different license types HERE When adding servers/VMs - here are the options you choose (again, based on the licensing model linked above) 1) add a server - use this option when adding a stand alone ...
    • How Licensing Works

      Bacula4 offers several different types of licenses 1) Physical Server license - A physical server license covers a single server with a single root OS install. No limitations. Because of the nature of how some VPS container technologies work (ie ...
    • How Licensing Works

      Bacula4 offers several different types of licenses 1) Physical Server license - A physical server license covers a single server with a single root OS install. No limitations. Because of the nature of how some VPS container technologies work (ie ...
    • Licensing How To (DCE/Self Hosted)

      With the DCE/Self Hosted edition, licensing is controlled via your accounts.bacula4.com portal 1) log into https://accounts.bacula4.com and manage your DCE/Self Hosted Service 2) upgrade/downgrade at section below, and set license numbers to what you ...