Replicas from Backup

27th July 2020 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 the “Source” Button (yellow row) and select the Repository XFS-Repository-DR as a source of the Replica, as shown in Picture 8.

Picture 8

The last steps are:

  • Completing the Replica Wizard creation
  • 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 the replica job is launched while Picture 11 shows the disk status when it runs.

Picture 10

Picture 11

Take care and see you soon!


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 to the official guide or to my previous article)

Picture 1

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 (Pictures 2 and 3)

Picture 2

Picture 3

After selecting Target and Repository it’s possible to complete the job creation (Pictures 4,5 and 6).

Picture 4

Picture 5

Picture 6

Now check if the backup policies are correctly applied and then launch the backup job (Pictures 7,8,9,10)

Picture 6

Picture 7

Picture 8

Picture 9

Picture 10


If you now try to create a backup copy job from the VBR console, you will find a problem because it is not available if you are going to select Periodic Copy (Immediate copy is available from version 11 of VBR)


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 select Immediate copy or
  • Add a new backup policy !” (Pictures 11 to 14)

Picture 11

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)

Picture 12

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

Picture 13

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

Picture 14


  1. 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.
  2. If you plan to use a Backup copy job you have to configure the Agent as managed by the backup server or on the backup copy job select the immediate copy job.
  3. 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

XFS – Performace

In the previous two articles, I explained how to configure and set up an XFS Repository with Veeam Backup & Replication v.10 (VBR)

In this new article, I’m going to cover why this is a very useful technology and should be adopted as soon as possible.

The main reason is:

“XFS linked-clone technology helps VBR to transform the backup chain” 

Let’s see what happens with Synthetic Full.

What is Synthetic full?

It’s a smart way to help VBR to create a Full Restore point downloading just an incremental backup from production.

The process is composed of two phases.

Firstly it creates a normal incremental backup.

Then it creates a full backup file stacking all previous backups (full and incremental).

This process normally needs a lot of work because VBR commands the repository to copy, paste and delete the data blocks.

The XFS integration, allows the system to do not move any block. In fact, the filesystem is able to re-point his metadata creating a Full Backup in One-Shot.

The result is super fast Full Backup creation.

Let’s see with an example:

A classic Full Backup has lasted 7 mins (Picture 1).

Picture 1

An Incremental Backup has lasted 2 mins and 30 sec (Picture 2).

Picture 2

What about a Synthetic Full

Picture 3 shows that it needs less than 30 seconds (plus the time needs to download the incremental data).

So Amazing technology and Veeamzing integration!!!

Picture 3

That’s all, for now, guys, see you soon and take care.

How to add an XFS Repository to Veeam

This is the second article talking about how to set up a Linux Veeam Repository for using the XFS technology.

In my last article, I wrote about how to create an XFS disk and now we are going to cover how to integrate it.

There are just two steps: 

1. Adding the new Linux Server to the managed VBR server.

2. Creating the Repository Server enabling the XFS add-on.

1. Before working with the VBR console it’s necessary to check the firewall status and more precisely if the ports needed are open to allow the system to work properly.

In this lab the way to set up the firewall is working with ufw command:

sudo ufw status (to check the status) 

If the firewall is disabled, please change its status with the command:

sudo ufw enable  (corrected on 8th May 2021)

Opening the ports with the following command:

sudo ufw allow #port/protocol

In my example I launched the following two commands:

sudo ufw allow 22/tcp

sudo ufw allow 2500:3300/tcp

as shown in the  Veeam user guide (picture 1)

Picture 1

The last command to check the firewall status is on port 22:

sudo lsof -i:22

the output is:

sshd 915 root 3u IPv4 27288 0t0 TCP *:ssh (LISTEN)
sshd 915 root 4u IPv6 27290 0t0 TCP *:ssh (LISTEN)

2. Now we are ready to create the new XFS repository:

  • 1. From VBR console add a new Linux Server (Picture 2)

Picture 2

  • Click on the Advanced button and check the right match between the ports  (Picture 3 and 4)

Picture 3

Picture 4

  • Add a new Repository, by choosing the just added server (in my case his name is cento01).

In the repository option, browse the server folders selecting the XFS one,  selecting the option Use fast Cloning (Picture 5 and 6)

Picture 5

Picture 6

Complete the task with some more clicks.

Note1: If you need more details about how to set up the firewall please have a look at the following site:

Linux Firewall

The next article will talk about performances,  see you soon and take care.

XFS & Veeam Repository

Today I’m going to talk about how to create a new Veeam repository using the XFS file system.

As much as you already know, v. 10 of Backup & Replication loves Linux. There are 3 top features that attest to it and they are:

  • XFS integration
  • Proxy Linux
  • Direct NFS Repository

The first article wants to talk about the XFS Integration and  which steps you should follow to use this smart technology integrated with Veeam Repositories

We will have 3 majors steps:

  1. Adding New Disk and formatting it as XFS
  2. Adding a Backup Repository
  3. Working and testing with XFS integration

So, let’s start with Point 1, remembering how to add a new disk to a Linux Server (we consider you have already added a disk to your physical or virtual Server)

First command is lsblk  that shows which disks have been recognized by the Operating System (in my case the new disk has been seen as sdc)

 sda           8:0    0   16G  0 disk

 ├─sda1        8:1    0  600M  0 part /boot/efi

 ├─sda2        8:2    0    1G  0 part /boot

 └─sda3        8:3    0 14.4G  0 part

   ├─cl-root 253:0    0 12.8G  0 lvm  /

   └─cl-swap 253:1    0  1.6G  0 lvm  [SWAP]

 sdb           8:16   0  200G  0 disk

 └─sdb1        8:17   0  200G  0 part /media/RepoXFS1

 sdc           8:32   0   16G  0 disk

 sr0          11:0    1    7G  0 from

Running the command fdisk -l  /dev/sdc it’s possible to catch the correct size of the disk.

 Disk /dev/sdc: 16 GiB, 17179869184 bytes, 33554432 sectors

 Units: sectors of 1 * 512 = 512 bytes

 Sector size (logical/physical): 512 bytes / 512 bytes

 I/O size (minimum/optimal): 512 bytes / 512 bytes

 fdisk /dev/sdc to create new   partition

Now it’s time to create a new disk (this procedure deletes all previous file systems present) with the command fdisk /dev/sdc.

Just follow the steps below to create the new disk: 

 n (to create a new partition)

 p (to create a primary partition)

 1 (default)

 First sector (default)

 Last sector (default) (if you want to use all the disk capacity)

 w write 

Relaunching the lsblk command it’s possible to see if the sdc1 disk appeared.

lsblk /dev/sdc

 sdc 8:32 0 16G 0 disk
 └─sdc1 8:33 0 16G 0 part /media/RepoXFS2

Three more steps to complete the first phase: 

1. Creating an XFS file system with Data-Block Sharing enables (reflink=1) 

mkfs.xfs -b size=4096 -m reflink=1,crc=1 /dev/sdc1

2. Creating the mount point on your server with the command:

mkdir  /backup/xfs-01

3. Mounting file system addicting the following line in /etc/fstab file

 /dev/sdc1           /backups/xfs-01             xfs          defaults     0   0

If you know the UUID of the disk (blkid /dev/sdbc1) you can also use the following digit instead of the previous one.

 UUID=UUID  /backup/xfs-01   xfs defaults 0 0

Reboot the server and everything should work.

See you soon with the second phase.

See you soon and take care.