compared with
Current by Nadja Pollard
on Aug 27, 2014 15:01.

Key
This line was removed.
This word was removed. This word was added.
This line was added.

Changes (21)

View Page History
R1Soft does not provide pre-built modules for the popular kernels anymore, so you will have to compile the module from source. You will have to compile this module against kernel headers or a kernel source tree.
R1Soft does not provide pre-built modules for the popular kernels, so you must compile the module from source. You must compile this module against kernel headers or a kernel source tree.

Server Backup Device Driver is a proprietary, loadable Linux kernel module distributed by R1Soft. It is loadable at run-time without restarting Linux, and you do *not* need to recompile your Linux kernel to use it.
{note}

If the kernel devel is too old and not found, see how to set up access to older {{yum}} packages in [Finding Old kernel-devel Packages For CentOS|kb3:Finding Old kernel-devel Packages For CentOS].

h3. 1. Compiling Server Backup Kernel Module Against Kernel Headers or Kernel Source Tree
h2. 1. Compiling Server Backup kernel module against kernel headers or kernel source tree

We are Server Backup Manager is not always able to compile kernel modules from kernel-devel packages supplied by most major Linux distributions. In some cases, packages are missing header files (broken), or the packages have been are stripped of information that any device driver would need to compile a kernel module. In these cases, we SBM can build using an installed {{kernel-devel}} package on your Linux server, as {{serverbackup-setup}} will obtain obtains the missing information it needs to compile a module from your running kernel.

In order for kernel module compilation to work, you should have Internet connectivity directly from the Linux server you are installing the Backup Manager on, to TCP port HTTPS (443), on the host {{krnlbld.r1soft.com}}.
In order for kernel module compilation, you must have Internet connectivity directly from the Linux server on which you are installing the Backup Manager, to TCP port HTTPS (443), and on the host {{krnlbld.r1soft.com}}.




h3. 2. Installing Kernel Sources
h2. 2. Installing kernel sources

If you are using an unmodified kernel provided by CentOS installer, install the {{kernel-devel}} package:


h3. 3. Verifying that the Source Matches Your Running Kernel
h2. 3. Verifying that the source matches your running kernel

Sometimes, the kernel-devel package is newer than the installed and running kernel. If the kernel-devel is too old and not found, please follow the instructions on how to set up access to older yum packages as documented in [Finding Old kernel-devel Packages For CentOS|kb3:Finding Old kernel-devel Packages For CentOS].

h3. 4. Building Server Backup Kernel Module
h2. 4. Building Server Backup kernel module


h4. Option 1: Building Online
h3. Option 1: Building online

(Direct Internet connection to R1Soft build server).
{code}serverbackup-setup --get-module
{code}
If module has been compiled and installed successfully, you will see an output similar to the following:
If the module is compiled and installed successfully, the system provides output similar to the following:

{code}Saving kernel module to '/lib/modules/r1soft/hcpdriver-cki-2.6.32-279.11.1.el6.x86_64.ko'
!getmodule.png!

h4. Option 2: Building Offline
h3. Option 2: Building offline

(Without direct Internet connection to R1Soft build server).