How Licensing Works

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 Virtuozzo and OpenVZ with a single root OS install on the master node), the master node would be licensed and would include all containers on the node

2) Stand Alone VMs license - This license can be used to backup any Virtual Machine on any Hypervisor or Public Cloud Platform.  There is a max ram of 32GB per stand alone VM.  VM's larger then 32GB can be licensed as a physical server. VM customers of public clouds, or Cloud Providers who do not want to license their hypervisors on supported platforms, or who are running hypervisors on non supported platforms, can also license their VMs as stand alone VMs

3) Support Hypervisor + VM license - this model is meant for providers utilizing supported virtualization platforms (ie onapp, xenserver, etc). In this model, providers license each hypervisor within a zone, group or individually - and then license each VM they wish to backup using Bacula4 within that licensed hypervisor zone. There is no memory limitation of each VM within this model. Whether you have single hypervisors with a large number of VMs, or you have a single large VM on a large hypervisor.  In both scenarios, you would license the hypervisor and then select "add a server" wizard, and if the server you are adding is a VM on a licensed hypervisor, it will automatically be licensed under the respective hypervisor + vm model.  This model is ideal for providers with dense hypervisors and many VMs per hypervisor they want to backup - AND - for scenarios where there are hypervisors with a few very large VMs (ie 1-3 VMs per hypervisor being greater then 32GB RAM each)

 

    • Related Articles

    • 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 ...

    • 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 ...

    • 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 ...

    • 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 ...

    • 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 ...