Veeam Backup & Replication – Agent Licensing

Today I’m covering how to enable VBR to use VUL licensing to backup Physical Machines (they could be server or workstation both)

If you need more details to understand better the implementation scenarios please refer to the three articles I already wrote

Veeam Agent  Part 1     Veeam Agent Part 2     Veeam Agent Part 3

As many of you already know it is possible to work with the free Veeam Agent version and a paid VBR version.

The only thing that this architecture allows is using the VBR repositories as a global backup container.

What customers forget is that you can’t have a mixed infrastructure composed of free and paid agents.

Let’s see an example:

An end-user with already 10 VBR sockets license has a new project to protect 30 workstations and he wants to use Veeam agent Free.

The end-user just has to install and set up on every single workstation the free agent to write backup data to VBR repository.

From VBR version 9.5.u4, Veeam is gifting 1 VUL license for every socket customer bought (up to 6 sockets). In our example it means the end-user can protect up to 6 Physical Server or 18 Workstation (1 Vul x 3 Workstation) for free or a mixed architecture.

What happens if you enable VBR to assign the gifted license from your VBR server?

First thing how to enable it? The next three pictures explain how to perform it

Picture 1

Picture 2

        Picture 3

From now on VBR will use the agent license up to consuming them.

In our example, the end-user will protect 18 Workstation but the last 12 will be out from the backup procedure.

Which is the solution?

Easy one, just Buying a new license pack.

Why you should have to buy new licenses?

There are at least three good reasons:

a) It is possible to manage your workstation architecture directly from VBR console.
b) There are more restore options.
c) Veeam support.

Gems:

1) One of the good news about the licensing of VBR v.10 is that from now on the license bought will be added to the gifted one. It means that you buy just a VUL packet (10 Vul) and have a total of 16 licenses.

2) If you have two license files (the first for VBR, the second for Veeam Agent) you have to merge them in just one license file.

The License rule and the procedure are available reading the following links https://www.veeam.com/kb3085  (rule)                         https://www.veeam.com/kb3116    (procedure)

3) Is there a turn back procedure?

Yes, please refer to the following KB https://www.veeam.com/kb2235 and  contact Veeam’s support.

To Remember:

4) It’s not possible to protect VM with sockets and VUL license. It means that sockets license has the priority to protect VM respect to VUL.

https://www.veeam.com/it/availability-suite-faq.html

5) Product comparison edition

https://www.veeam.com/it/products-edition-comparison.html

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

shows

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:

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:

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.