Replicas from Backup

27th July Update:

From now on it’s possible to create a replica Job from a backup copy job set-up as immediate copy mode.

In my last article I talked about how to throttle the network when you need to perform replicas Job (click here for more details).

In this second article, I will show you how to replicate a VM using a Backup as a source.

The main three points are:

  1. Setting up a Backup Job
  2. Setting up a Backup Copy Job
  3. Setting up a Replication Job

Let’s go!

1. It’s quite easy to create a new backup job. If you didnìt read the guide, the next pictures will show the more important points

Picture 1

Picture 2


2. Now it’s time to configure the backup copy Job selecting the just created primary backup as a source.

Picture 4

Picture 5

To simplify reading the article, please pay attention to the name of the second Repository (XFS-Repo-DR)

3. Now it’s time to set up the Replica Job

Picture 6

Picture 7

This is the main point of the article:

Click on “Source” Button (yellow row) and select the Repository XFS-Repository-DR as a source of the Replica, as shown in Picture 8 .

Picture 8

Last steps are:

a) Completing the Replica Wizard creation

b) Running the job

Picture 9

To be sure that everything is working fine you can use any tools that check up the I/O on Repository.

In this article, I choose IOSTAT because it’s light, powerful and easy to use on Linux Repositories

Picture 10 shows the disk status before replica job is launched while Picture 11 shows the disk status when it runs.

Picture 10

Picture 11


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