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:
“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
- 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.
- 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
- If you plan to use Backup copy job you have to configure managed by backup server option on backup mode
- 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