Veeam Backup & Replication – Agent Licensing

Today I’m covering how to enable VBR to use VUL licensing to backup Physical Machines (they could be server or workstation both)

If you need more details to understand better the implementation scenarios please refer to the three articles I already wrote

Veeam Agent  Part 1     Veeam Agent Part 2     Veeam Agent Part 3

As many of you already know it is possible to work with the free Veeam Agent version and a paid VBR version.

The only thing that this architecture allows is using the VBR repositories as a global backup container.

What customers forget is that you can’t have a mixed infrastructure composed of free and paid agents.

Let’s see an example:

An end-user with already 10 VBR sockets license has a new project to protect 30 workstations and he wants to use Veeam agent Free.

The end-user just has to install and set up on every single workstation the free agent to write backup data to VBR repository.

From VBR version 9.5.u4, Veeam is gifting 1 VUL license for every socket customer bought (up to 6 sockets). In our example it means the end-user can protect up to 6 Physical Server or 18 Workstation (1 Vul x 3 Workstation) for free or a mixed architecture.

What happens if you enable VBR to assign the gifted license from your VBR server?

First thing how to enable it? The next three pictures explain how to perform it

Picture 1

Picture 2

        Picture 3

From now on VBR will use the agent license up to consuming them.

In our example, the end-user will protect 18 Workstation but the last 12 will be out from the backup procedure.

Which is the solution?

Easy one, just Buying a new license pack.

Why you should have to buy new licenses?

There are at least three good reasons:

a) It is possible to manage your workstation architecture directly from VBR console.
b) There are more restore options.
c) Veeam support.


1) One of the good news about the licensing of VBR v.10 is that from now on the license bought will be added to the gifted one. It means that you buy just a VUL packet (10 Vul) and have a total of 16 licenses.

2) If you have two license files (the first for VBR, the second for Veeam Agent) you have to merge them in just one license file.

The License rule and the procedure are available reading the following links  (rule)                   (procedure)

3) Is there a turn back procedure?

Yes, please refer to the following KB and  contact Veeam’s support.

To Remember:

4) It’s not possible to protect VM with sockets and VUL license. It means that sockets license has the priority to protect VM respect to VUL.

5) Product comparison edition


Today I’m going to cover what’s happening if you set the protection policy up as a workstation.

In this article, I’m covering the Veeam Agent for Linux (VAL) also,  to widen the range of my site and answer to friends asking me to talk about their workstation based on Ubuntu.

After creating the protection group  (please refer to the previous articles), let’s create a new job and set it up as workstation job.

Now add the laptop (ubuntu2 in my case) and follow the wizard pointing as repository the VBR server

After completing the task, check that the configuration has been rightly applied to the laptop and then launch the first backup.

Now it’s time to connect via SSH to the Linux laptop and lunch  the command veeam as root

it shows your backup status

and from here you can lunch the same job another time.

But what happens if you try to add a new backup from this interface? As previously in Windows case, it is not allowed, because it is managed by VBR.

A good step is to check that the license work in workstation mode.

But if you remember well, my first goal was having a backup outside the primary site.

I already wrote in my last article (VEEAM AGENT FOR WINDOWS/LINUX – REMOTE COPYING DATA – 2 ) how to set up a new backup job from VBR console (I’m pretty sure you are now ready to do it without any help).

After applying the configuration let’s start the Backup job

This is what happens, It FAILED !!!

Why ?

The answer is inside the workstation limitation that you can find on the following Veeam web page (Veeam Edition comparison)

where is clearly written that if you use the agent as a workstation, you can perform the second/third etc job just only writing data to Cloud Repository.

Veeam Agent uses case summary:

Backup TypeManaged byBCJ1+ Backup1+Backup CCVUL


Stand Alone1+ Backup1+Backup CCVUL



In this second article, we are going to cover what happens if we set up a VAW backup job working “managed by agent”.

Let’s see the main differences from the wizard (to know all the procedure please refer the official guide or to my previous article)

Before going on, have a look at the manual to understand what happens in this scenario: (click here)

“Veeam Backup & Replication uses the backup policy as a saved template and applies settings from the backup policy to Veeam Agents that run on computers specified in the backup policy”.

In other words,  the policies are pushed to the VAW; So the laptop is able to protect its data even without a VBR start command.

Ok, following the wizard, input a backup name and select the Laptop to protect

After selecting  Target and Repository you can complete the job creation.

Now check if the backup policies are correctly applied and then launch the backup job.


If you now try to create a backup copy job from VBR console, you will find a problem because it is not available.


Because in this scenario the policy commands the backup process. It’s like saying the Agent is the master of the backup.

How to go over? Just easily add a new backup policy !”

To know: if you use a remote desktop and connect to your saved laptop , you can find the Veeam icons. When you click on them you get the classic interface (as standalone installation)

To Remember: from here you can not add a new job. You always have to set it up from VBR console

And the last thing ? What about licensing? It consumes a single VUL


  1. If your connection between VBR and agent is not reliable probably you have to choose”managed by agent” on the backup mode option. If you plan to use a repository managed by VBR, pay attention to the Repositories-VBR connection also.
  2. If you need to have more than a copy, just create a new policy backup. My two cents are:
    a) Use a forever forward incremental chain
    b) The repository should have a block cloning technology as Refs / Xfs
  3. If you plan to use Backup copy job you have to configure managed by backup server option on backup mode
  4. Licensing does not have any impact, it always uses a VUL license

The next and last article will cover the workstation backup approach. See you soon