Question about a possible backup solution

syg00 · 11-21-2017, 12:18 AM

Decided to have a look at veeam. Downloaded the doco (*excellent* user guide), and found a few concerns. Probably of no/minor concern for most Linux users - no btrfs support, and only distro released kernels supported (because of dkms I guess). I am a heavy user of btrfs - ironically for snapshot largely, and this system also runs rawhide kernels.
No matter, I dug up a sacrificial machine and proceded to go get the download. Hmmm, that registration system I mentioned above got in the way.

Quote:

Please register with your corporate email.

Public email usage is allowed, but has certain restrictions: trial downloads and access to support and licensing portal require a business email usage.

I no longer have one, and I have better things to do than fight these things. Time to remove NFS from my backup server (a veeam requirement), and go back to rsync.

PTide · 11-21-2017, 03:49 AM

Quote:

no btrfs support

Yeah, we've had complaints from SLES users about BTRFS support, too. Now we consider to add it in future release. TBH I was reluctant to add it onto the list despite SUSE having it as a default fs for root. Mostly because of concerns in its stabiblity and readyness, I rarely heard about anyone really using BTRFS in production (except for FB maybe).

Quote:

<...>and only distro released kernels supported (because of dkms I guess)

Mostly because it is difficult to ensure proper testing for something that has not been even released. Also we do not support kernels that do not come from distro repository (for instance, we don't support CentOS 7 with kernel 4.*) If some distro officially gets a newer kernel from its repository then we can support it. For example, not so long ago Fedora 26 got 4.13.5-200 which was not compatible with the product. Those who had upgraded were able to get the fix from our support team.

Quote:

Time to remove NFS from my backup server (a veeam requirement)

Actually I can't remember such a requirement, there is only cifs-utils requirement (in case you want to send backups to SMB).

Quote:

I no longer have one<...>

Free version is available without business email. To make things easier you can get the packages directly from the repo.

Thank you

syg00 · 11-21-2017, 10:04 PM

Pulled the F24 rpms from the repo link above. Fails to build on F26.

Code:

DKMS make.log for veeamsnap-1.0.1.364 for kernel 4.13.12-200.fc26.x86_64 (x86_64)
Wed Nov 22 13:53:12 AEST 2017
make: Entering directory '/usr/src/kernels/4.13.12-200.fc26.x86_64'
  AR      /var/lib/dkms/veeamsnap/1.0.1.364/build/built-in.o
  CC [M]  /var/lib/dkms/veeamsnap/1.0.1.364/build/mem_alloc.o
  CC [M]  /var/lib/dkms/veeamsnap/1.0.1.364/build/sparse_array_1lv.o
/var/lib/dkms/veeamsnap/1.0.1.364/build/mem_alloc.c: In function ‘dbg_kmalloc_huge’:
/var/lib/dkms/veeamsnap/1.0.1.364/build/mem_alloc.c:138:55: error: ‘__GFP_REPEAT’ undeclared (first use in this function); did you mean ‘__GFP_RECLAIM’?
   ptr = dbg_kmalloc( max_size, flags | __GFP_NOWARN | __GFP_REPEAT);
                                                       ^~~~~~~~~~~~
                                                       __GFP_RECLAIM
/var/lib/dkms/veeamsnap/1.0.1.364/build/mem_alloc.c:138:55: note: each undeclared identifier is reported only once for each function it appears in
make[1]: *** [scripts/Makefile.build:302: /var/lib/dkms/veeamsnap/1.0.1.364/build/mem_alloc.o] Error 1
make[1]: *** Waiting for unfinished jobs....
make: *** [Makefile:1516: _module_/var/lib/dkms/veeamsnap/1.0.1.364/build] Error 2
make: Leaving directory '/usr/src/kernels/4.13.12-200.fc26.x86_64'

PTide · 11-22-2017, 01:15 AM

Please find the fixed packages here.

Cheers