Table of contents Introduction I. Common procedure to build and install kernel module II. Installing on Mandrake 9.2 with kernel 2.4.22-37mdk III. Installing on Mandrake 10.1 with kernel 2.6.8 IV. Common installation procedure on Debian V. Installing Japanese version of Acronis True Image Server for Linux 9.1. VI. Installing on Fedora Core 3/4/5 VII. Installing on Redhat Advanced Server 4.0 VIII.FAQ: Q: How do I run *.i686 installation file? Q: Is *.i686 installation file compatible with my x86_64 arch? Q: Can I install Acronis True Image Server for Linux/Acronis True Image Enterprise Linux Agent on a ia64 system? Q: The installer complains that it cannot find kernel sources in /lib/modules//build or in /lib/modules//source directories. What should I do? Introduction This HOWTO refers to Acronis True Image Server for Linux and Acronis True Image Enterprise Server Linux Agent. Sometimes the installer can not compile the necessary kernel modules or prepare the required execution environment. Usually it prompts you about such problems and refers to this file. Section I describes the common "how to build and install module" procedure. Most often you should read it if you have a custom kernel or non-standard kernel sources location. Sections II -VII provide necessary information for certain specific distributions. Section VIII covers several most often asked questions. If your question is not answered here, refer to FAQ articles at www.acronis.com . Please note that Redhat 9.0, Fedora Core 1, Fedora Core 2, Redhat Advanced Server 3.0, SuSE 9.0, 9.1, 9.2, 9.3, Slackware 10, ASPLinux 9.2, ASPLinux 10, ASPLinux 11 ASPLinux Server II and Gentoo and some other distributions with stock kernels should not have issues with Acronis products for Linux, so that they are not mentioned in the description below. I. Building and installing kernel module in general case If the installer can not compile the necessary kernel modules, you will have to do it manually. Please install the sources of your running kernel, find appropriate kernel config file and install all packages required for kernel building packages (like gcc, glibc-devel, etc.). You should be prompted about the necessary packages while kernel sources installation. Most often the snapapi kernel module should be built and installed with the "dkms" command. It can be done with the following commands: # dkms build -m -v \ -k --config --arch \ --kernelsourcedir # dkms install -m -v \ -k --config --arch \ --kernelsourcedir must be "snapapi" for 2.4.x kernels or "snapapi26" for 2.6.x kernels. is the version of your running kernel. You can find it using # uname -r command can be detected by # ls /usr/src/snapapi* is your kernel config filename. Usually this file can be found in the /boot directory. can be detected by # rpm -q --queryformat "%{ARCH}\n" kernel for RPM based distributions or by # uname -m for non-RPM based distributions. For details please refer to dkms man page (man dkms). After successful module building and installation you may try to launching trueimage or trueimagecmd (see "man trueimagecmd") utilities or connect to the Linux agent from management console and check the functionality of the software. Respective kernel modules will be loaded automatically. II. Installing on Mandrake 9.2 with kernel 2.4.22-37mdk 1.You should install the kernel sources and prepare kernel to build with the following commands: # make -C /usr/src/linux-2.4.22-37mdk/ mrproper # cp /boot/config-2.4.22-37mdksmp /usr/src/linux-2.4.22-37mdk/.config # make -C /usr/src/linux-2.4.22-37mdk/ oldconfig # make -C /usr/src/linux-2.4.22-37mdk/ dep 2. Then build and install snapapi module with the following commands: # dkms build -m snapapi -v 0.7.12 -k 2.4.22-37mdksmp --arch i686 \ --config /boot/config-2.4.22-37mdksmp --kernelsourcedir \ /usr/src/linux-2.4.22-37mdk/ --no-prepare-kernel # dkms install -m snapapi -v 0.7.12 -k 2.4.22-37mdksmp \ --arch i686 It is supposed that you have kernel 2.4.22-37mdksmp, kernel architecture is i686 and module version is 0.7.12 3. Check if devfs support is active on your system. In case it is not, you should activate devfs support with the following commands: # mkdir /devfs # mount -t devfs devfs /devfs NOTE: you may make devfs support permanent by adding "devfs /devfs devfs defaults 0 0" to your /etc/fstab file. III. Installing on Mandrake 10.1 with kernel 2.6.8 Please install libstdc++5-3.3.4-1mdk.i586.rpm from the first CD by entering: # rpm -ihv libstdc++5-3.3.4-1mdk.i586.rpm IV. Common installation procedure on Debian distributions. 1. First of all you should install rpm support by entering: # apt-get install rpm 2. Then create rpm database by entering: # rpm --initdb 3. Then you should be able to install Acronis True Image Server for Linux 9.1 successfully. If after installation the software complains that it cannot find any hard drives, check if devfs is enabled on your system. In case it is not, you should activate devfs support by issuing the following commands: # mkdir /devfs # mount -t devfs devfs /devfs You can make devfs support permanent by adding "devfs /devfs devfs defaults 0 0" to your /etc/fstab file. NOTE:If you are using Debian 3.0 distribution, it is possible that raw-devices were not created during initial installation/configuring. The following simple script can be used to check and create the devices if needed (root permissions required): #!/bin/bash mkdir -p /dev/raw/ if [ ! -e /dev/rawctl ] ;then mknod /dev/rawctl c 162 0 fi for i in `seq 1 128`; do if [ ! -e /dev/raw/raw${i} ] ;then mknod /dev/raw/raw${i} c 162 ${i} fi done V. Installing Japanese version of Acronis True Image Server for Linux 9.1. If you have a Japanese build of Acronis True Image Server 9.1 for Linux, you should proceed with the following steps to activate Japanese support in X window application (trueimage): 1. Download and install TrueType Japanese fonts rpm ttfonts-ja-1.2-8.noarch.rpm. The file can be downloaded from http://www.rpmfind.net//linux/RPM/redhat/7.3/i386/ttfonts-ja-1.2-8.noarch.html To install the rpm please run: # rpm -Uhv ttfonts-ja-1.2-8.noarch.rpm --nodeps 2. To activate new fonts please add FontPath "/usr/share/fonts/ja/TrueType/" record into Section "Files" of /etc/X11/XF86Config file and restart X server. VI. Installing on Fedora Core 3/4/5/6 If installer complains that libstdc++.so.5 is required for trueimage rpm please install compat-libstdc++.rpm from the Fedora Core CD by typing: # rpm -ihv compat-libstdc++-.rpm And repeat the installation. VII. Installing on Redhat Advanced Server 4.0 If installer complains that libstdc++.so.5 is required for trueimage rpm please install compat-libstdc++-33-3.2.3-47.3.i386.rpm from the second Redhat Advanced Server 4.0 CD by: # rpm -ihv compat-libstdc++-33-3.2.3-47.3.i386.rpm VIII. FAQ: Q: How do I run *.i686 installation file? A: This is a standard binary file. In order to start the installation, do: # chmod +x .i686 # ./.i686 where .i686 is the name of your installation file. Q: Is *.i686 installation file compatible with my x86_64 arch? A: Yes. In order to install Acronis True Image software on x86_64 Linux distribution follow the standard installation procedure. Q: Can I install Acronis True Image Server for Linux/Acronis True Image Enterprise Linux Agent on ia64 system? A: No, this architecture is not supported by the current versions of Acronis True Image Server for Linux 9.1 and by Acronis True Image Enterprise Linux Agent. Q: The installer complains that it cannot find kernel sources in /lib/modules//build or in /lib/modules//source directories. What should I do? A: This usually means that you do not have the sources of your running kernel installed. We suggest you to check the documentation for your Linux distribution to find the correct sources. Note: kernel sources should 100% correspond to your running kernel! Some examples are below: If you have Fedora Core Linux distribution: You may install the sources using rpm manager or using yum. Find your kernel version by entering: # uname -r Let us suppose it is 2.6.12-1.1372_FC3 And your kernel architecture by entering: # uname -m Suppose it is i686 So you should install the packages called kernel-devel-2.6.12-1.1372_FC3.i686.rpm You may find it on your Fedora Core installation CD or download from Fedora ftp server. In order to use yum to install the kernel sources, consult with the appropriate documentation. If you have RHEL4/CentOS 4.x Linux: Find your kernel version by entering: # uname -r FSuppose it is 2.6.9-34.ELsmp Detect your kernel package architecture: # uname -m Suppose it is i686. So you should install the kernel-smp-devel-2.6.9-34.EL.i686.rpm package. You should be able to find it on your Linux distribution CD. Note: on RHEL3/CentOS the name of the kernel source package should be kernel-source-, where is the name of your running kernel. If you are using SUSE Linux distribution: Find your kernel version: # uname -r Suppose it is 2.6.5-7.244 Detect your kernel package architecture: # uname -m Suppose it is i686 Note, most of all SUSE packages have i586 architecture, so you should install the package kernel-source-2.6.5-7.244.i586.rpm. You can find it on your Linux distribution CD or download from SUSE Linux ftp server. If you are using Debian distribution. The easiest way is to install the sources is to use apt-get utility. Find your kernel version: # uname -r Suppose it is 2.6.18-3-686 So, to install the sources of your kernel you should use the command below: # apt-get install linux-source-2.6.18-3-686 Note: "apt-get install linux-source" will download the sources of the most recent kernel. Use it only if you are completely sure that you are using the most recent kernel. Note: If you are using Debian Sarge, the command should be similar to: # apt-get install kernel-source- where is the name of your kernel image. Q: I cannot connect to Acronis True Image Enterprise Linux Agent installed on 64 bit Debian (or Debian-based) system. What should I do? A: At the moment Debian x86_64 does not support running 32-bit applications to its full extent. Acronis True Image Enterprise Linux Agent is a 32-bit application and it tries to authenticate against 64-bit PAM module by default. To solve this issue, you should install a minimal set of 32-bit libraries: # apt-get install ia32-libs Download i386 package libpam-modules and the packages it depends on: libselinux1 libsepol1 from packages.debian.org For example, packages for Debian Etch can be downloaded from: http://packages.debian.org/stable/libs/libpam-modules http://packages.debian.org/stable/libs/libselinux1 http://packages.debian.org/stable/libs/libsepol1 Extract the downloaded packages. For example: # dpkg --extract libpam-modules_0.79-4_i386.deb # dpkg --extract libselinux1_1.32-3_i386.deb # dpkg --extract libsepol1_1.14-2_i386.deb Put the extracted shared libraries to /lib32/ # mkdir /lib32/security # cp /lib/security/* /lib32/security/ # cp /lib/libselinux.so.1 /lib32/ # cp /lib/libsepol.so.1 /lib32/ Add the path to the extracted libraries to /etc/pam.d/acronisagent ----------- #%PAM-1.0 auth required /lib32/security/pam_unix.so account required /lib32/security/pam_unix.so ----------- Restart Acronis True Image Enterprise Linux Agent : # /etc/init.d/acronis_trueimage_agent restart