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 Type Managed by BCJ 1+ Backup 1+Backup CC VUL
Server VBR Y Y Y 1
Server Agent N Y Y 1
Workstation Agent N N Y 1/3


Stand Alone 1+ Backup 1+Backup CC VUL
Server Y Y 1
Workstation N Y 1/3



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