Greetings friends, Veeam has launched a few weeks ago the new Veeam Agent for Linux 2.0, which includes among many new features the possibility of performing a Backup to Cloud Connect, which was the missing piece of equipment to offer full service to Cloud environments where we have Linux, such as AWS, Azure, Digitalocean, etc…
New features of Veeam Agent for Linux 2.0 and comparison between versions
Veeam Agent for Linux 2.0 brings several new features, one of them is discussed here, but it has others that I show you in this comparison table, if you want to know the entire comparison, visit the official PDF:
How to install Veeam Agent for Linux 2.0, step by step
Already I told you how to download the Veeam Agent for Linux package quickly using my GitHub project. This project continues to support the new version of Veeam Agent for Linux 2.0.
Installing Veeam Agent for Linux
Once downloaded the package, we will be able to execute the following command that will install VAL and the dependencies that it requires, I leave you the steps for all the Operating Systems, we will have to be in the path where we have downloaded the file veeam-release-*.
For CentOS / RHEL / Oracle Linux / Fedora
rpm -ivh ./veeam-release* && yum check-update
For openSUSE / SLES
zypper in ./veeam-release* && zypper refresh
For Debian / Ubuntu
dpkg -i ./veeam-release* && apt-get update
To install Veeam Agent for Linux we will finally launch the following command, depending on the Operating System we have:
For CentOS / RHEL / Oracle Linux / Fedora
yum install veeam
For openSUSE / SLES
zypper install veeam
For Debian / Ubuntu
apt-get install veeam
We can see something similar to the next log, in my case is Ubuntu 14.04:
Reading package lists... Done Building dependency tree Reading state information... Done The following packages were automatically installed and are no longer required: linux-headers-3.16.0-71 linux-headers-3.16.0-71-generic linux-headers-3.16.0-76 linux-headers-3.16.0-76-generic linux-image-3.16.0-71-generic linux-image-3.16.0-76-generic linux-image-extra-3.16.0-71-generic linux-image-extra-3.16.0-76-generic Use 'apt-get autoremove' to remove them. The following extra packages will be installed: binutils cpp cpp-4.8 dkms fakeroot gcc gcc-4.8 libasan0 libatomic1 libc-dev-bin libc6-dev libcloog-isl4 libfakeroot libgcc-4.8-dev libgomp1 libisl10 libitm1 libmpc3 libmpfr4 libquadmath0 libtsan0 linux-libc-dev make manpages-dev veeamsnap Suggested packages: binutils-doc cpp-doc gcc-4.8-locales dpkg-dev debhelper gcc-multilib autoconf automake1.9 libtool flex bison gdb gcc-doc gcc-4.8-multilib gcc-4.8-doc libgcc1-dbg libgomp1-dbg libitm1-dbg libatomic1-dbg libasan0-dbg libtsan0-dbg libquadmath0-dbg glibc-doc make-doc The following NEW packages will be installed: binutils cpp cpp-4.8 dkms fakeroot gcc gcc-4.8 libasan0 libatomic1 libc-dev-bin libc6-dev libcloog-isl4 libfakeroot libgcc-4.8-dev libgomp1 libisl10 libitm1 libmpc3 libmpfr4 libquadmath0 libtsan0 linux-libc-dev make manpages-dev veeam veeamsnap 0 upgraded, 26 newly installed, 0 to remove and 0 not upgraded. Need to get 49.7 MB of archives. After this operation, 123 MB of additional disk space will be used.
He will ask us if we want to continue or not, we will type Y to continue:
Do you want to continue? [Y/n]
The installation process will then begin:
Get:1 http://repository.veeam.com/backup/linux/agent/dpkg/debian/public/ stable/veeam veeamsnap all 184.108.40.2060 [87.0 kB] Get:2 http://us.archive.ubuntu.com/ubuntu/ trusty-updates/main libasan0 amd64 4.8.4-2ubuntu1~14.04.3 [63.1 kB] Get:3 http://repository.veeam.com/backup/linux/agent/dpkg/debian/public/ stable/veeam veeam amd64 220.127.116.110 [30.2 MB] Get:4 http://us.archive.ubuntu.com/ubuntu/ trusty-updates/main libatomic1 amd64 4.8.4-2ubuntu1~14.04.3 [8,636 B] ... Setting up dkms (18.104.22.168-1.1ubuntu5.14.04.9) ... Setting up veeamsnap (22.214.171.1240) ... Loading new veeamsnap-126.96.36.1990 DKMS files... First Installation: checking all kernels... Building only for 3.16.0-77-generic Building initial module for 3.16.0-77-generic Done. veeamsnap: Running module version sanity check. - Original module - No original module exists within this kernel - Installation - Installing to /lib/modules/3.16.0-77-generic/updates/dkms/ depmod...... DKMS: install completed. Setting up veeam (188.8.131.520) ... Adding system startup for /etc/init.d/veeamservice ... /etc/rc0.d/K20veeamservice -> ../init.d/veeamservice /etc/rc1.d/K20veeamservice -> ../init.d/veeamservice /etc/rc6.d/K20veeamservice -> ../init.d/veeamservice /etc/rc2.d/S20veeamservice -> ../init.d/veeamservice /etc/rc3.d/S20veeamservice -> ../init.d/veeamservice /etc/rc4.d/S20veeamservice -> ../init.d/veeamservice /etc/rc5.d/S20veeamservice -> ../init.d/veeamservice Setting up libfakeroot:amd64 (1.20-3ubuntu2) ... Setting up fakeroot (1.20-3ubuntu2) ... update-alternatives: using /usr/bin/fakeroot-sysv to provide /usr/bin/fakeroot (fakeroot) in auto mode Setting up libc-dev-bin (2.19-0ubuntu6.13) ... Setting up linux-libc-dev:amd64 (3.13.0-137.186) ... Setting up libc6-dev:amd64 (2.19-0ubuntu6.13) ... Setting up manpages-dev (3.54-1ubuntu1) ... Processing triggers for libc-bin (2.19-0ubuntu6.13) ...
We can now run a sudo veeam and see the Veeam Agent for Linux Console
How to configure our first backup job to Veeam Cloud Connect
It is worth mentioning that the first thing we have to take into account is that the Provider with Veeam Cloud Connect needs to be in the latest Release Veeam Backup & Replication v9.5 U3, video steps and images to update.
If the provider already fulfills the requirements, when making the sudo veeam, this message will appear where we ask if we want to install a license, in our case if we want to use the new functionality to Veeam Cloud Connect, we need a license of Veeam Agent Workstation or Server, en Free is not available this feature.
In my case I have selected my license already located on the server in the /home/oper/license.lic path.
We already see that the license has been installed correctly, I get a message in red indicating the validity of the license:
Perfect! We have everything ready, let’s create the job, press the C key to create the first job:
We will select a name for the job, in this case BackupJob-CC, for example:
We will select that we want to copy the whole machine:
We will be able to see the backup target options, and since I have a Workstation or Server license, I can select Veeam Cloud Connect:
We will now select the FQDN of the Veeam Cloud Connect provider, and the port through which it operates:
We will accept the SSL Certificate warning message to continue:
We will now introduce the tenant user that the provider has provided us with:
We will now see the resource, or resources that our Veeam Cloud Connect provider has given us, select the one we want and enter the number of restore points we want:
NEW! It is time to select these three options, two of them new, the first one is encryption of our backup at source, so the Backup file is protected, the second option is to index the files and then they can be recovered more easily:
I have marked that I want to protect my backup and the password I want:
We will now select the task schedule and scheduling:
And if everything is correct, we can already say that you start the work now, or wait for the programming and click Finish:
The backup job process will begin:
And after the time the server needs to copy itself to the Veeam CC, we can see the result of the task:
That’s all friends, simple, isn’t it?
I have already mentioned that if the Provider does not have the latest version of Veeam Backup & Replication v. 95 U3, it is likely that when you try to configure an Agent for Linux 2.0 to a Veeam CC you will receive this message:
Con que el proveedor actualice a la última versión será suficiente.
As always, here are some links that you will find useful:
- GA build: 184.108.40.2060 (December 19, 2017)
- Full list of new and improved features > What’s New in 2.0
- System Requirements, Known Issues, How to Install and Upgrade > Release Notes
- All the needed official guides, in all possible formats > Veeam Help Center
Another Blog posts worth to read:
[…] por Jorge de la CruzEscrito en 2 January, 20184 January, 2018 Read it in English […]