XFS – Performace

Last article about XFS.

In the previous two paragraphs I explained how to configure and set-up the XFS repository on Veeam Backup & Replication v.10 (VBR)

Today let’s see how perfectly the XFS linked-clone technology helps VBR to transform the backup chain. 

Particularly 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.

To be very short the process is composed of two phases.

Firstly it creates a normal incremental backup data, secondly it creates a full backup file stacking all previous backups (full and incremental).

This process normally needs a lot of work because it is necessary to copy, paste and delete the unnecessary blocks to create the synthetic full.

With XFS integration, we do not move any block because the filesystem will 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:

Full Backup has lasted 7 mins (Picture 1)

Picture 1

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!!!

So Amazing technology  and Veeamzing integration!!!


How to add an XFS Repository to Veeam

This is the second article talking about how to set the Veeam Repository up with XFS

In my last article I wrote about how to create an XFS volume.

Now let’s see how to integrate it!

Numbers of step are quite easy

  1. Add a new Linux Server.
  2. Create Repository  with XFS add on.

The first step seems to be very easy and …  it is … if you have already set up correctly your linux firewall.


Because when you add a new server you can select which ports will be used to communicate from and to Backup Server to the new Repository

Let’s configure the firewall on my centos Linux server (firewallD)

The most important commands are:

  • sudo firewall-cmd –get-active-zones

The output shows you if the firewall is running and where it’s enabled

In the case you need to change the ethernet interface just launch:

  • sudo firewall-cmd –zone=home –change-interface=eth0

Probably the most used command is:

sudo firewall-cmd –zone=public –list-all

where you can see the status of opening ports

What we need now is opening the right ports as shown from Veeam user guide:

Let’s open the ports we need:

sudo firewall-cmd –zone=public –add-port=22/tcp –permanent

sudo firewall-cmd –zone=public –add-port=2500-3300/tcp –permanent 

and check if the output of the command

sudo firewall-cmd –zone=public –list-all 


ports: 2500-3300/tcp 22/tcp

Now it’s time to create the new XFS repository following these easy steps:

  • Adding New Server

Select Linux Server and click on the Advanced button.

Check if the ports we have previous configurated are present.

Now select the server (in my case is cento01),  Browse the XFS folder and then select the XFS option (in Yellow)

Just some more next click and finally you have finally configurated your new XFS repository.

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


The next article will talk about performances so … see you soon

XFS & Veeam Repository

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

As many of you already know, v. 10 of Backup & Replication loves Linux. There are 3 top features that attest 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 recognize 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 rom

Now you have to run fdisk -l  /dev/sdc to understand the 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 create a new disk (this procedure delete any previous file system present) with the command fdisk /dev/sdc.

Just follow the steps below to create the new disk  

    1. n to create a new partition
    2. p to create a primary partition
    3. 1 (default)
    4. First sector (default)
    5. Last sector (default) (if you want to use all the disk capacity)
    6. w write 

Just relaunch the  lsblk command and watch if  sdc1 correctly appears.

lsblk /dev/sdc

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

Two more steps for first phase 

Creating File system XFS with Data-Block Sharing enable (reflink=1) with the following command:

make.xfs -m reflink=1,crc=1 /dev/sdc1  (default block is 4096)

Create the mount point on your server with the command cmkdir /mountpoint/xfs-1

Mount file system addicting the following line in /etc/fstab file

/dev/sdc1 /mountpoint/xfs-1         xfs     defaults        1 2

Reboot the server and everything should work.

See you soon with second phase.