You still have to obtain a new Update 4 license from my. but works exactly the same. This is your traditional Backup and Replication license, licensed per protected socket of hypervisor. In the middle there is some murkiness so let’s take a look at the options. Any new products though will be licensed through a per instance model going forward.
per socket) licensing for Veeam Backup and Replication and the Veeam Availability Suite which includes VBR and VeeamONE is here to stay. For now and for as far as I can get anyone to tell me perpetual (a.k.a. As you keep counting up you can see where this model needed (and still needs) streamlined. Further when you consider that due to Veeam’s Service Provider program you as an end customer have the option of either buying and subscribing directly from a VAR or “renting” those licenses from a server provider. Protecting Office365, AWS instances, and Veeam’s orchestration product are all per consumable unit subscriptions. Now as we look at the present and future Veeam has lots of different products that are subscription based.
As these can be managed and deployed via the Veeam Console this license was required to be installed on your VBR server as well so you now had 2 separate licenses files that were commingled on the server to create the entire solution for protecting VBR and Agent workloads. After that came along Veeam Agents for Windows and Linux and we had the addition subscriptions levels for VAW Server, VAW Workstations, and VAL. In the past if you were using nothing but Veeam Backup and Replication (VBR) you did all your licensing by the socket count of protected hypervisors. It’s worth noting that there is a FAQ on this but the content is varying quite a bit as this gets rolled out.
Now that I’ve got to the bottom of my own licensing issues I’ll post here what I’ve learned to hopefully keep you from experiencing the same headaches. I will be honest and say that the upgrade was not as smooth as I would have hoped.
This rides along with the established perpetual licensing we still have for VBR and Veeam Availability Suite. my guess is their customers have asked for a way to make that protection and licensing portable.In Veeam’s move they have decided this can be solved by creating per instance licensing, which is similar to how you consume many other cloud based services. As workloads that need to be protected/backed up/made available have moved from being 100% on-premises and inside our vSphere or Hyper-V environments to mixes of on-prem, off-prem, on physical, public cloud, etc. Veeam has recently released the long-awaited Update 4 to their Backup and Replication 9.5 product and with it has come some changes to how they deal with licensing.
0 kommentar(er)
