VAL on Linux Gentoo

[ndum]

Hi PTide

I have tried to install the Veeam Agent also on a hardened-gentoo.

The following errors are accuring when i compile the modules: (gcc 4.9.3 / 4.9.4, kernel 4.4.2-hardened)

make modules SUBDIRS=drivers/veeamsnap
CC [M] drivers/veeamsnap/mem_alloc.o
cc1: error: incompatible gcc/plugin versions
cc1: error: fail to initialize plugin ./tools/gcc/colorize_plugin.so
cc1: error: incompatible gcc/plugin versions
cc1: error: fail to initialize plugin ./tools/gcc/initify_plugin.so
make[1]: *** [scripts/Makefile.build:259: drivers/veeamsnap/mem_alloc.o] Error 1
make: *** [Makefile:1399: _module_drivers/veeamsnap] Error 2

could you maybe create/publish a new veeam gentoo binary which is also hardened compatible?

Thanks

[PTide]

Hi,

could you maybe create/publish a new veeam gentoo binary which is also hardened compatible?

Due to a large number of existing kernels it is quite problematic to provide a binary for each of them. Moreover, I believe that the problem might not be with the module, but also with the kernel that you use. Kindly contact Gentoo community, let's see what they will say regarding the problem.

I realize this is a unique situation and a little weird but is there a way you can compile and send me a 32bit version of Veeam?

There is no 32-bit version of veeamsnap as well as there is no 64-bit version. Since veeamsnap is distributed as a source code it is bit-agnostic.

Although we have plans to investigate the problem, Gentoo is not officially supported and is not on the top of our priorities list, so it might take some time.

[levente18]

PTide,

I was not asking for a 32 bit version of veemsnap but the actual Veeam software.(there are different from what I understand. At least you have separate folders for them in the RPM). Can you compile a 32 bit version of Veeam?

Thanks

[tsightler]

32-bit version of the VAL userspace code are already available. You can download any version you want from:

http://repository.veeam.com/backup/linux/agent/

The original instructions in this thread suggested using the el7 RPM and extracting the binaries from them so simply download the RPM from the i386 directory instead of the x86_64 directory.

http://repository.veeam.com/backup/linu ... el/7/i386/

However, whether 32-bit Veeam binaries will work with a 64-bit kernel module is not certain, but you are welcome to try it.

[levente18]

Thanks PTide,

I was able to start the 32 bit Veeam and create a job but it fails with the following message:

https://www.dropbox.com/s/730pu7si091r0 ... s.JPG?dl=0

Is this something that can be fixed or do I need to run a pure 64bit system and use the original RPM you suggested?

Thanks,

[PTide]

Please contact our support team directly, send them logs, and post your case ID. Our development team will take a closer look at the setup, however I can't give you any estimates on when the problem will be fixed.

Thank you

[levente18]

Thank you PTide! I really appreciate you guys' efforts. Case #02079476 was created a few minutes ago. Please keep me posted on your findings. I can provide remote access to the system if necessary. Just let me know.

Thanks,

Levi

[jajohnson]

Hello,

I have a client that has a gentoo box and was wondering if this process still applied today or if another method is required? They are currently on version 3.3 so I expect they will need to upgrade gentoo before installing the client.

[PTide]

Hi

We haven't invested too much development and testing resources into making the agent to work with Gentoo since 2017. If you are using kernel 5.8 or later you might want to check this thread.

Thanks!

[jajohnson]

Hi PTide,

Thank you for the additional link. The client I dont believe will bring the kernel up that high given the age of the system. Their end goal is to get rid of the box altogether. If I had them bring the kernel up to 4.4, would the process you had originally posted still work for this? I understand this is a lot of work for a short term system, but the client wanted to get away from the cron jobs and get this system into Veeam.

Thanks,

[PTide]

They need to try to install the product (see this post) and see if that works.
If they encounter any errors they are welcome to seek help on this forum or in other communities, but I cannot guarantee that the issue will be resolved fast (or resolved at all) since Gentoo is not on the list of supported systems.

Thanks!

[jajohnson]

Great, thank you for the direction on this.

[bigun]

So I'm reporting in concerning the current state of compiling veeamsnap in Gentoo.

I've masked every kernel that is newer than 5.8.0, which forced me down to gentoo-sources-5.4.109.

I downloaded veeamsnap-5.0.0.4318-1.noarch.rpm.

I copied the source code to <kernel source>/drivers/veeamsnap, attempted to compile:

Code: Select all

gameserver /usr/src/linux # make modules SUBDIRS=drivers/veeamsnap
  CALL    scripts/checksyscalls.sh
  CALL    scripts/atomic/check-atomics.sh
  DESCEND  objtool
  Building modules, stage 2.
  MODPOST 12 modules

..and no sign of veeamsnap being compiled, when it's over with, no modules named veeamsnap in the modules directory:

Code: Select all

gameserver /usr/src/linux # modprobe veeamsnap
modprobe: FATAL: Module veeamsnap not found in directory /lib/modules/5.4.109-gentoo

This is something I'd like to get working, and I'm using the Community version of Veeam, so no way to open a ticket. As an alternative I can use Ubuntu, but it feels like a downgrade from Gentoo.

[bigun]

I found better instructions:

Grab a copy of the source code via github: https://github.com/veeam/veeamsnap

Create directory and extract zip:

Code: Select all

unzip <archive name>

Enter directory:

Code: Select all

cd ./<archive directory name>/source

Make the module:

Code: Select all

make

Then install the modules:

Code: Select all

make install

Finally load the module:

Code: Select all

modprobe veeamsnap

Confirm module is loaded:

Code: Select all

lsmod | grep veeamsnap

If everything is well, add module to auto load upon boot:

Code: Select all

nano -w /etc/conf.d/modules

Add veeamsnap to modules list:

Code: Select all

modules="veeamsnap"

There's talk here of this version supporting newer kernels. YMMV.

[bigun]

So I've gotten the module loaded, but the actual Veeam Agent seems to be an issue.

I've downloaded the RPM from the site, ran rpmunpack on it. The result is a directory structure that doesn't seem to match any of the instructions I've seen. There's only an etc directory and nothing else.

Code: Select all

gameserver ~/veeam # ls -la ./veeam-release-el8-1.0.8-1.x86_64
total 12
drwxr-xr-x 3 root root 4096 Jun 27 03:21 .
drwxr-xr-x 5 root root 4096 Jun 27 03:25 ..
drwxr-xr-x 4 root root 4096 Jun 27 03:21 etc
gameserver ~/veeam # ls -la ./veeam-release-el7-1.0.8-1.x86_64
total 12
drwxr-xr-x 3 root root 4096 Jun 27 03:25 .
drwxr-xr-x 5 root root 4096 Jun 27 03:25 ..
drwxr-xr-x 4 root root 4096 Jun 27 03:25 etc

[mich]

Code: Select all

make modules SUBDIRS=drivers/veeamsnap
make modules_install SUBDIRS=drivers/veeamsnap

SUBDIRS doesn't work for modern kernels.

kernel 5.15.19-gentoo-x86_64, to build and install veeamsnap:

Code: Select all

cd /usr/src/linux
make M=drivers/veeamsnap
make M=drivers/veeamsnap modules_install

[PTide]

Passed on the news to dev.

Thanks!