VBR – Proxy linux server UUID

When a Linux VM is added to Veeam console as a Proxy Server,  you can fall out in the error shown in picture 1

Picture 1

The reason for this behavior is that the default VM config does not allow another software to see the UUID of the VM.

What is UUID?

It’s the unique identifier used to uniquely identify partitions in Linux operating systems.

Why is it important to use it?

A backup where the proxy is a Linux VM only works with virtual appliance transport mode. It uses the VMware hot add capability.

Easier: when a job starts, the proxy Linux mounts the disks of the VM that have to be processed and then send a copy of data to the Veeam Repository.

If the backup server knows which are the proxy disks it can process the others easily and without errors.

The result is that it’s mandatory to set it up correctly as shown in the user guide and in Veeam forum

Note 1: the Linux command to show UUID is blkid

To address the issue just switch off the VM and, from vCENTER Console, follow the procedure showed in the next 4 pictures highlighted in yellow.

Picture 2

Picture 3

Picture 4

Picture 5

That’s all folks

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.

Why? 

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 centos Ubuntu server (ufw)

To check the status just type: sudo ufw status

If it is disabled, change his status with: sudo ufw status enable

For Opening the right ports the commands are:

sudo ufw allow 22/tcp

sudo ufw allow 2500:3300/tcp

as shown from Veeam user guide:

Check your job with the following command

sudo lsof -i:22

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:

Centos-Firewall

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

NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
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:

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

Create the mount point on your server with the command mkdir /mountpoint/xfs-01

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

UUID=UUID  /mnt/xfs-01   xfs defaults 0 1

to get UUID the command is: blkid /dev/sdbc1

Reboot the server and everything should work.

See you soon with second phase.