Table of Contents
To understand this section, basic knowledge of Linux or UNIX systems is required.
If you received a pre-installed machine. You just need to connect it to your network. You must then reset the network parameters. We use as default parameters: IP=192.168.0.99, network=192.168.0.0, server name=lrs. Log in as "root" user with the password "linbox".
The main settings to adapt the system to your network and the configuration files are shown below. For more information, the system manpages can be displayed with the man command: man [configuration_file]. For example: man interfaces to get all the details about this file. The lbs.conf file has no man page.
When you change the network settings, you must use the /etc/init.d/networking restart so that the settings are applied.
/etc/lbs.conf contains information about
the LRS configuration and user licenses (the key is ignored if you
installed the 'LRS libre').
# LRS configuration file
# Comments (begin with #)
iface=eth0 # Interface listening to the clients requests
hwmac=00:06:29:0D:22:66 # MAC address of the network adapter
license=100 # Number of license (i.e. of clients)
key=EB92235ABD4C45C5 # License Key (depend of hwmac and license)
autoselect=no # automatic update of the file header.lst
# if base/local images are created
skelsync =no # automatic update of the template
# if base/local images are created
# password
adminpass=linbox
# paths
basedir = /tftpboot/revoboot # Base system directory
addscript = /tftpboot/revoboot/bin/create_config
[dhcp]
nostaticip=1 # use dynamic dhcp addresses allocation
The configuration file to use is
/etc/network/interfaces. Here is an example with
comments :
# loopback interface (do not change it)
auto lo
iface lo inet loopback
# first network interface
auto eth0 # "auto" means that the interface should
# be brought up automatically on system boot
iface eth0 inet static # eth0 interface definition
address 192.168.0.2 # address IP
netmask 255.255.255.0 # netmask
network 192.168.0.0 # network address
broadcast 192.168.0.255 # broadcast address
gateway 192.168.0.1 # default gateway
up route add -net 224.0.0.0 netmask 240.0.0.0 dev eth0 # for multicast packetsChange this settings according to your needs.
If you want to use the DHCP server included in the LRS, you should use the Webmin configuration module. If you have an external DHCP server, please refer to the section 'Using an existing DHCP server'.
In the Webmin DHCP server module, check that the subnet settings match those of your network card. Also check that the 'Boot filename' option, is set to '/tftpboot/revoboot/bin/revoboot.pxe'. Do not forget to add a dynamic address pool in 'Address Pools for Subnet'.
Resolver settings are done in /etc/resolv.conf. Here is an example :
search localdomain # default domain search nameserver 192.168.0.1 # DNS server ip address
By default, no resolv.conf file is installed on the server. To backup clients, LRS uses the NFS filesystem. A client send to the server a mount request for the storage area. For more security, the NFS server do an inverse DNS request with the client IP address. So the resolver uses resolv.conf to know how to proceed this inverse resolution. If the inverse resolution returns nothing for the client IP address, the mount of the storage area will fail. So it is easier and safer to not use a DNS service on the LRS server, else it involves declaring all the client IP addresses into the DNS.
The host name is stored in /etc/hostname. By default, the host name is lrs.
lrs
The host name is specified in /etc/hosts too.
127.0.0.1 localhost # do not change this line
192.168.0.2 lrs.localdomain lrs # to set according to your IP,
# your hostname and domain name
Many other parameters, may be modified through webmin and its numerous modules. A few examples are :
NFS exported directories configuration (instead of manually modifying /etc/exports),
Samba configuration,
Visualization/modification of server hard disk partitions,
To have the LRS seen by Windows clients from another name, you should add the following lines in the '[global]' section to /etc/samba.smb.conf:
workgroup = YOURDOMAIN netbios aliases = NEWNAME
Some modules need to be able to resolve WINS names to work properly. If clients and servers are on the same subnet, no additional setup should be needed. If not, you should configure the LRS to use a WINS server, by adding the following lines to the '[global]' section:
wins server = wins.server.ip.address
If you have more than one WINS server for different networks, please use the following syntax:
wins server = srv1:wins.server.ip.address srv2:other.wins.ip.address
The server setup is made through an auto-installable CD-Rom.
Insert the CD-Rom in the server and restart the server. Verify the order of boot devices in the BIOS configuration. The boot order should allow to boot from the CD-Rom before booting from the hard disk.
The boot program from the CD-Rom will create the partition on the hard disk and will set up a full Linux distribution (based on a Debian Sarge 3.1), and a pre-configured LRS software.
After the boot on the CD-Rom, you just need to hit twice the "y" key to confirm that you wish to set up the system on the hard disk. Beware, all data on the hard disk will be erased!
Once the restoration is complete (about 10 minutes), the system will be similar to a pre-installed one, as described above.
The standard installation will create 3 partitions :
a main partition of 1.4 GB mounted as root (/) with the filesystem is ext3,
a 256 MB swap partition,
a partition of 6.6 GB mounted as /tftpboot with the filesystem reiserfs. This partition contains all LRS components and the backup area. This partition is managed by LVM (Logical Volume Manager), so that the storage area can be spread easily across other hard disk partitions. (for more information on the LVM, please read the 'Suse LVM White Paper', http://www.suse.com/us/whitepapers/lvm/index.html).
![[Tip]](/ucome.rvt/any/en/Produits/LRS/details/doc/img/tip.png) | |
To make the data partition, /tftpboot, use all available hard disk space, you first have to run '/root/resize', which will create an additional partition, and will dynamically extend /tftpboot. |
You will also encounter problems Webmin's SSL certificate. To update the certificate, run '/root/webmincert', and answer the questions but take care to give the official LRS host name (or its IP address) on your network, when you're asked for 'Common Name (eg, YOUR name)'.
For the other parameters, please refer to Section 2.1.1, “Pre-installed Server” above.
The LRS is built over some basic packages which can be installed manually on every Linux system. The procedure described here is based on a LRS installation on a RedHat ES 4 system, but can be done on other platforms, with the help of specificities of each distribution.
To manually deploy a LRS, you have to:
Organize the available disk space,
Install the missing packages on the target server (xprobe2, backuppc, etc…),
Set up the required services (apache, mysql, dhcp, nfs, etc ...),
Install and setup the LRS service,
Install and setup the LRS administration interface.
The reference platform is a Redhat ES 4 with the following settings:
English language,
US keyboard,
Automatic partitioning, with a / sized to 5 GB, the remainder being free for later use,
Standard Grub install,
Network: setup upon the network environment,
No firewall,
SeLinux disabled,
No additional language,
Timezone setup upon the environment,
root password: « linbox »,
Custom settings: no service, no graphical environment, final size: 762 MB.
The LRS will work even if all of the above elements are not set up, with the help of some tuning.
The LRS primarily stores its data in 3 places:
inventory and lsc data: in a MySQL database,
system module: in /tftpboot/revoboot,
files module: in backuppc's data storage directory.
It is strongly advised to group these three data pools together on a single dedicated partition. In this documentation we will consider that it will be /tftpboot, with:
/tftpboot/revoboot for the system module,
/tftpboot/mysql for MySQL,
/tftpboot/backuppc for the files backup module.
With regard to the choice of the partition format, it is highly recommended to avoid the ext2/ext3 format: the files module is very greedy for inodes, which implies a very low block size. In this documentation we will choose the ReiserFS format.
![[Note]](/ucome.rvt/any/en/Produits/LRS/details/doc/img/note.png) | |
Under RH ES 4, ext2/3 is the only available format. |
Here is an example of manual creation of the /tftpboot partition, LVM volume, ReiserFS format:
keep in mind the free PE number available on the LVM volume (using « vgdisplay »: Free PE),
create a new logical volume using this number of PE:
lvcreate VolGroup00 --name tftpboot --extents <nombre de PE>
create a Reiserfs partition type in /dev/VolGroup00/tftpboot:
mkfs.reiserfs /dev/VolGroup00/tftpboot
make the /tftpboot mountpoint:
mkdir /tftpboot
declare the partition in /etc/fstab:
/dev/VolGroup00/tftpboot /tftpboot auto defaults 0 0
mount the partition:
mount /tftpboot
If it is not possible to create a dedicated partition to LRS data, it is still possible to use an existing partition using a simple symbolic link. For example to store the LRS data in the /data:
mkdir -p /data/linbox/lrs ln -s /data/linbox/lrs/tftpboot /tftpboot
The following packages are required to transform a standard server into a LRS server:
The official distribution repositories,
Contributors repositories (if needed, see below),
The Linbox repository.
The following software has to be installed:
Webmin,
DHCP server ( ISC, >=3.0 recommended),
TFTP server,
NFS server,
MySQL, PHP,
Samba,
Apache,
mkisofs, cdrecord, dvdrecord : to burn CDs and DVDs.
Depending on the mileage of the distribution, the following packages have to be installed (your mileage may vary):
| Service/Distribution | Redhat ES 4 (RPM) | Mandriva 4 (RPM) | Debian 3.x (DEB) | Mandrake 10.x (RPM) |
|---|---|---|---|---|
| NFS | nfs-utils & nfs-utils-client | nfs-utils & nfs-utils-client | nfs-kernel-server & nfs-common | nfs-utils & nfs-utils-client |
| DHCP | dhcp | dhcp-server & dhcp-common | dhcp3-common & dhcp3-server | dhcp-server & dhcp-common |
| MySQL | mysql-server | mysql-5.0.24 | mysql-server | mysql |
| PHP | php, php-mysql, php-gd2 | php4-cgi, php4-xml, php4-mysql, php4-gd2 | php4-cgi, php4-xml, php4-mysql, php4-gd2 | php-cgi |
| Samba | samba | samba-client | samba | samba-client |
| PERL modules | N/D | perl-DB_File, perl-Archive-Zip, perl-Compress-Zlib, perl-Digest-MD5, perl-Authen-PAM, perl-Convert-BER, perl-Mon, perl-Net-SSLeay | libdb-file-lock-perl, libarchive-zip-perl, libcompress-zlib-perl, libdigest-md5-perl, libauthen-pam-perl, libconvert-ber-perl, libmon-perl, libnet-ssleay-perl | perl-DB_File, perl-Archive-Zip, perl-Compress-Zlib, perl-Digest-MD5 |
| TFTP (server) | atftpd & tftp | atftpd & tftp | atftpd & tftp | atftpd & tftp |
| Apache | httpd | apache-mpm-prefork, apache-mod_php4 | ||
| webmin (version >= 1.07) | N/D | N/D | webmin | webmin (version >= 1.07) |
| mkisofs & cdrecord | mkisofs & cdrecord | mkisofs & cdrecord | mkisofs & cdrecord | mkisofs & cdrecord |
| xprobe2 | N/D | xprobe | xprobe | xprobe |
| Distro system | Distro system | Distro system | Distro system |
![[Warning]](/ucome.rvt/any/en/Produits/LRS/details/doc/img/warning.png) | |
These packages must be installed now, before even going further in the documentation. |
| |
Do not forget to setup the DHCP, MySQL, HTTPD and NFS services to have them started at boot using system-config-service, or drakconf. |
| |
If a service is unavailable on your distribution, it may be available on a third-party repository, such as RPM Forge (http://rpmforge.net) or Dag (http://dag.wieers.com) for all RPM-based distributions, and backports.org or apt-get.org for DEB-based distributions. |
To obtain the files below, you must:
either go to Linbox's « pro » FTP (ftp.linbox.com) to get them, using your customer access code,
or go to Linbox's « GPL » FTP (ftp.linbox.org)
You must get the following files:
| File name | File path |
|---|---|
| atftpd.static | /pub/lrs/base/atftpd/atftpd.static |
| backuppc.init | /pub/lrs/backuppc/rpm/backuppc.init |
| backuppc-0.9.0.wbm | /pub/lrs/webmin/backuppc-0.9.0.wbm |
| backuppc-2.0.2-2.noarch.rpm | /pub/lrs/backuppc/rpm/backuppc-2.0.2-2.noarch.rpm |
| base_20061030.tgz | /pub/lrs/base/base_20061030.tgz |
| cgi.tgz | /pub/lrs/base/www/cgi.tgz |
| dhcpd.conf.clean | /pub/lrs/base/conf/dhcpd.conf.clean |
| init.d | /pub/lrs/base/conf/init.d |
| lbs.conf | /pub/lrs/base/conf/lbs.conf |
| lbs-2.6.7.wbm | /pub/lrs/webmin/lbs-2.6.7.wbm |
| lbs-cd-1.7.1.wbm | /pub/lrs/webmin/lbs-cd-1.7.1.wbm |
| lbs_common-1.4.12.wbm | /pub/lrs/webmin/lbs_common-1.4.12.wbm |
| lbs-vnc-0.9.4.wbm | /pub/lrs/webmin/lbs-vnc-0.9.4.wbm |
| lrs-inventory-2.1.2.wbm | /pub/lrs/webmin/lrs-inventory-2.1.2.wbm |
| lrs-theme-3.1.wbm | /pub/lrs/webmin/lrs-theme-3.1.wbm |
| lsc-1.0.2.wbm | /pub/lrs/webmin/lsc-1.0.2.wbm |
| nfs-exports | /pub/lrs/base/conf/nfs-exports |
| smb.conf | /pub/lrs/base/conf/smb.conf |
| webmin-lsc | /pub/lrs/base/conf/webmin-lsc |
| www.tgz | /pub/lrs/base/www/www.tgz |
| xinetd.atftpd | /pub/lrs/base/conf/xinetd.atftpd |
| |
The version numbers given here are those which were available when this document was written, and given as an indication only. |
| |
Do not install them now, they will be deployed below. |
For all distributions build over Debian, you will have to obtain the following files:
either by going to Linbox's « pro » FTP (ftp.linbox.com) to get them, using your customer access code,
or by going to Linbox's « GPL » FTP (ftp.linbox.org)
| File name | File path |
|---|---|
| cgi.tgz | /pub/lrs/base/www/cgi.tgz |
| dhcpd.conf.clean | /pub/lrs/base/conf/dhcpd.conf.clean |
| nfs-exports | /pub/lrs/base/conf/nfs-exports |
| smb.conf | /pub/lrs/base/conf/smb.conf |
| www.tgz | /pub/lrs/base/www/www.tgz |
| |
The version numbers given here are those which were available when this document was written, and given as an indication only. |
You must also add the following lines to /etc/apt/sources.list:
deb ftp://lrs:<mod de passe>@ftp.linbox.com/pub/lrs/base/deb/ woody/ deb http://www.linbox.com/pub/lrs/backuppc/deb/ woody/ deb ftp://ftp.debian.org/debian sarge main contrib non-free
And put the following « pinnings » on your system (/etc/apt/preferences):
Package: * Pin: origin www.linbox.com Pin-Priority: 1001 Package: * Pin: origin ftp.linbox.com Pin-Priority: 1001
Packages have to be installed in the specified order. The configuration files are given for example only. Please, back-up your configuration files before any modification.
First copy the given DHCP conf file:
[root@lrs LRS]# cp -a dhcpd.conf.clean /etc/dhcpd.conf
Then restart DHCP:
[root@lrs LRS]# service dhcpd start Staring dhcpd : [ OK ]
| |
Under Debian: [root@lrs LRS]# cp -a dhcpd.conf.clean /etc/dhcp3/dhcpd.conf [root@lrs LRS]# invoke-rc.d dhcp3-server start Starting DHCP server: dhcpd3 |
Add the required NFS exports in /etc/exports:
[root@lrs LRS]# cp -a nfs-exports /etc/exports
| |
The NFS service seems to be in « sync » mode by default under RH ES 4, which considerably degrades the performances. In this case please add the « async » option for the LRS required NFS exports. |
| |
When using a partially setup DNS (for example no reverse given), it is strongly advised to start the NFS service without resolv.conf file. On MDV or RH, this behavior can be emulated using the following patch on the NFS daemon start script: --- /etc/init.d/nfs.dist 2006-07-08 12:17:11.000000000 +0200
+++ /etc/init.d/nfs 2006-11-23 22:24:52.000000000 +0100
@@ -71,6 +71,7 @@
fi
# Start daemons.
# Start daemons.
+ mv -f /etc/resolv.conf /etc/resolv.conf.tmp 2>/dev/null
[ -x /usr/sbin/rpc.svcgssd ] && /sbin/service rpcsvcgssd start
action $"Starting NFS services: " /usr/sbin/exportfs -r
@@ -114,6 +115,7 @@
# Let rpc.idmapd know that rpc.mountd just started
[ -x /usr/sbin/rpc.idmapd ] && /sbin/service rpcidmapd condstart
+ mv -f /etc/resolv.conf.tmp /etc/resolv.conf 2>/dev/null
;;
stop) |
Then, refresh the NFS exports list:
[root@lrs LRS]# exportfs -ra
With Debian-based distributions:
apt-get install lbs
For others distributions, you must:
unpack base_20061030.tgz in /tftpboot:
[root@lrs LRS]# cd /tftpboot; tar zxf /root/LRS/base_20061030.tgz; chown -R root.root /tftpboot
You will then obtain the following structure:
/tftpboot/revoboot |--bin : binaries |--cfg : directory containing the default configuration |--etc : config files | |--ether : etherboot config files (MAC/IP matching) | |--pci.ids : pci ID / cards matching |--images : will contain one directory per client, using the MAC address |--imgbase : will contain the shared images | |--Local-Disk : shared image used to boot on a local drive | | |--conf.txt : menu conf file and associated menu action | |-- ... : others directories also containing shared images |--imgskel : skel directory containing the default configuration |--iso : ISO images directory |--log : logs directorycopy the default license file to /etc/lbs.conf:
[root@lrs LRS]# cp -a lbs.conf /etc/
install the wrapper:
[root@lrs LRS]# cp init.d /etc/init.d/lbs [root@lrs LRS]# chmod +x /etc/init.d/lbs [root@lrs LRS]# ln -s ../init.d/lbs /etc/rc6.d/K01lbs [root@lrs LRS]# ln -s ../init.d/lbs /etc/rc3.d/S99lbs
| |
If Webmin is not installed into /usr/share/webmim, you must create the following symlink: root@lrs LRS]# ln -s /usr/libexec/webmin /usr/share/webmin |
Some of the LRS modules are written in PHP and thus require another symlink:
[root@lrs LRS]# mkdir -p /var/lib/lrs
[root@lrs LRS]# ln -sf /usr/bin/php /var/lib/lrs/php
| |
Under Mandriva CS4 and Debian: [root@lrs LRS]# ln -sf /usr/bin/php4-cgi /var/lib/lrs/php |
As the LRS uses PHP/CGI under Webmin, some tuning must be done (usually in /etc/php.ini, but your mileage may vary):
cgi.redirect_status_env = "MINISERV_CONFIG"; cgi.fix_pathinfo=1 log_errors = Off
Some Samba shares are defined on the server to help the user using the LRS:
[root@lrs LRS]# cp -a smb.conf /etc/samba/smb.conf
[root@lrs LRS]# service smb restart
| |
Under Debian: [root@lrs LRS]# invoke-rc.d samba restart |
For Debian-based distributions, just install the Woody (3.0) version of BackupPC:
apt-get install backuppc=2.0.2-7
then alter the $Conf{BackupPCUserVerify} directive in /etc/backuppc/config.pl:
$Conf{BackupPCUserVerify} = 0;and then restart BackupPC.
For others distributions, installing BackupPC is a little bit tricky, as some tuning has to be done:
RPM installation:
[root@lrs LRS]# rpm -i --nodeps --force backuppc-2.0.2-2.noarch.rpm
Then copy the start script:
[root@lrs LRS]# cp backuppc.init /etc/init.d/backuppc [root@lrs LRS]# chmod +x /etc/init.d/backuppc [root@lrs LRS]# ln -s ../init.d/backuppc /etc/rc3.d/S99backuppc
Then apply this patch (--- => deletions, +++ => inserts) to the start script:
--- /etc/init.d/backuppc.init 2003-06-18 00:00:00.000000000 +0200 +++ /etc/init.d/backuppc 2005-09-22 18:34:21.000000000 +0200 @@ -33,7 +33,7 @@ # __INSTALLDIR__/bin/BackupPC -d # echo -n "Starting BackupPC: " - daemon --user __BACKUPPCUSER__ __INSTALLDIR__/bin/BackupPC -d + daemon --user backuppc /usr/bin/env LC_ALL=en /usr/share/backuppc/bin/BackupPC -d RETVAL=$? echo [ $RETVAL -eq 0 ] && touch /var/lock/subsys/backuppc || \ @@ -43,7 +43,7 @@ stop() { echo -n "Shutting down BackupPC: " - killproc __INSTALLDIR__/bin/BackupPC + killproc /usr/share/backuppc/bin/BackupPC RETVAL=$? [ $RETVAL -eq 0 ] && rm -f /var/lock/subsys/backupcpc echo "" @@ -57,14 +57,14 @@ reload() { echo -n "Reloading config.pl file: " - killproc __INSTALLDIR__/bin/BackupPC -HUP + killproc /usr/share/backuppc/bin/BackupPC -HUP RETVAL=$? echo return $RETVAL } rhstatus() { - status __INSTALLDIR__/bin/BackupPC + status /usr/share/backuppc/bin/BackupPC } case "$1" inThen modify the BackupPCUserVerify directive in /etc/backuppc/config.pl:
$Conf{BackupPCUserVerify} = 0;and restart BackupPC:
[root@lrs LRS]# service backuppc restart Shutting down BackupPC: [ OK ] Starting BackupPC: [ OK ]
For Debian-based distributions:
apt-get install lrs-all
For others, use the Webmin interface (https://lrs:10000), go to "webmin", "webmin configuration", "webmin modules", and install all .wbm files previously downloaded, starting with lbs_common.
Using the Webmin interface (https://lrs:10000), click on "webmin", "webmin configuration", "webmin themes", then select the "LRS" theme.
If you did not install the lrs-inventory module using apt-get (or dpkg), you have to fill-in the database using the provided SQL scripts:
[root@lrs LRS]# cd /usr/share/webmin/lrs-inventory/sql [root@lrs sql]# ./create-db.sh ERROR 1049 (42000): Unknown database 'inventory' Create the database Upgrading to v2 Upgrading to v3 Upgrading to v4 Upgrading to v5 Done
[root@lrs LRS]# cd /usr/share/webmin/lsc/sql ERROR 1049 (42000): Unknown database 'lsc' Create the database Upgrading to v2 Upgrading to v3 Doner
If you want to modify the LRS database credentials, please modify '/usr/share/webmin/lrs-inventory/classes/DataSources.xml' for the inventory, and '/usr/share/webmin/lsc/include/config.inc.php' for the LSC.
Start by installing the Linbox CGI and static pages:
mv /var/www/html /var/www/html.dist mkdir /var/www/html cd /var/www/html tar zxf /root/LRS/www.tgz chown apache: . -R cd /var/www/cgi-bin/ tar zxf /root/LRS/cgi.tgz
Apache is configured using a dedicated VHost (which could be written to /etc/httpd/conf.d/99_lrs.conf for example), containing:
<VirtualHost *:80>
ServerName lrs
DocumentRoot /var/www/html/linbox
DirectoryIndex index.html index.shtml index.html.var
<Directory /var/www/html/linbox>
Options +Includes +Indexes +FollowSymLinks +MultiViews
AllowOverride AuthConfig Options Limit
Order allow,deny
allow from all
</Directory>
ScriptAlias /cgi-bin/ "/var/www/cgi-bin/"
<Directory "/var/www/cgi-bin">
AllowOverride None
Options None
Order allow,deny
Allow from all
</Directory>
ErrorLog /var/log/httpd/error_lrs_st-ouen.log
# Possible values include: debug, info, notice, warn, error, crit,
# alert, emerg.
LogLevel warn
CustomLog /var/log/httpd/access_lrs_st-ouen.log combined
ServerSignature On
<Directory /usr/share/webmin/lrs-inventory/agent/>
Allow from all
</Directory>
Alias /lbs-transfert /usr/share/webmin/lrs-inventory/agent/
Alias /lbs-transfer /usr/share/webmin/lrs-inventory/agent/
Alias /lrs-transfert /usr/share/webmin/lrs-inventory/agent/
Alias /lrs-transfer /usr/share/webmin/lrs-inventory/agent/
Alias /ocsinventory /usr/share/webmin/lrs-inventory/agent/transfertNG.php
</VirtualHost>The configuration will be updated after having restarted the Apache service:
[root@lrs LRS]# service httpd reload Reloading httpd : [ OK ]
| |
If SeLinux is activated on the server (not advisable), it must be disabled for the HTTPd service (using system-config-securitylevel). |
The LRS uses the TFTP multicast (atftpd) protocol to save / deploy images. Its installation is quite simple. Please remove any other tftpd service prior to its installation.
[root@lrs LRS]# cp -a atftpd.static /usr/local/sbin [root@lrs LRS]# chmod +x /usr/local/sbin/atftpd.static [root@lrs LRS]# cp -a xinetd.atftpd /etc/xinetd.d/atftpd [root@lrs LRS]# service xinetd reload Reloading configuration : [ OK ]
| |
Under Debian, please install the « atftpd » package. |
The first thing to do is to generate the SSH key, and to copy it to the right directory:
[root@lrs LRS]# ssh-keygen -t dsa Generating public/private dsa key pair. Enter file in which to save the key (/root/.ssh/id_dsa): Enter passphrase (empty for no passphrase): Enter same passphrase again: Your identification has been saved in /root/.ssh/id_dsa. Your public key has been saved in /root/.ssh/id_dsa.pub. The key fingerprint is: 88:26:06:3d:31:2a:6b:d9:1b:ad:c1:df:df:84:d0:31 root@localhost.localdomain [root@lrs LRS]# cp -a /root/.ssh/id_dsa.pub /tftpboot/revoboot/images/data
Additionally, for non-debian based distributions, the following steps are required:
Add the cron file:
[root@lrs LRS]# cp -a webmin-lsc /etc/cron.d/webmin-lsc
Change some permissions:
[root@lrs LRS]# chmod +x /usr/share/webmin/lsc/scheduler-daemon.php
Add some example scripts to the LSC files repository, using the following commands:
mkdir -p /tftpboot/revoboot/lsc/linbox/ cp -ar /usr/share/webmin/lsc/scripts/* /tftpboot/revoboot/lsc/linbox/
Finally, for the remote hard-drive exploration function to be available, you will need the 'lufs-utils' package (containing /usr/bin/auto.sshfs), and the lufs kernel module. The 'autofs' must also be fully operational and configured with the following line in its master config file /etc/auto.master:
/var/autofs/ssh /usr/bin/auto.sshfs --timeout=60
If your platform do not allow the remote hard-drive exploration function (f.e. if there is no lufs kernel module), you can disable it in the LSC module configuration page.
If you don't use a free version of the LRS, you will need to obtain a license, bound to the network interface MAC address on which the LRS daemon is listing.
Under GNU/Linux, you can obtain the MAC address by using the following command:
[root@lrs LRS]# ifconfig
eth0 Link encap:Ethernet HWaddr 00:10:DC:B0:25:5F
inet addr:192.168.0.9 Bcast:192.168.0.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:139644 errors:0 dropped:0 overruns:0 frame:0
TX packets:5321 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:24865816 (23.7 MiB) TX bytes:6324079 (6.0 MiB)
Interrupt:11 Base address:0xc000 Memory:d5100000-d5100038The eth0 interface MAC address is printed next to ''HWaddr'' (here: 00:10:DC:B0:25:5F).
Send this information to <lrs@linbox.com>. You will
then receive instructions to install the LRS license using the Web
interface.
Connect to the LRS Web interface (https://<LRS-IP-address>:10000/lbs_common), click on « check that your licenses are correct », enter the license key and restart the LRS service:
[root@lrs LRS]# service lbs start Starting Linbox Rescue Server: OK (daemon) (traffic shaping)
| |
This is a Redhat / Mandriva specific bug: restart does not work; on Debian this problem does not exist. |
Also in https://<LRS-IP-address>:10000/config.cgi?lbs , in « <ip-du-LRS> », fill-in the « XPM file » field with /tftpboot/revoboot/lib/linbox2.xpm .
If you already have a DHCP server on your network, then you should disable the LRS DHCP server, and configure your server to enable network booting of your clients. Successfully tested DHCP servers include: ISC DHCP 2.x and 3.x, Microsoft DHCP, Lucent QIP 5.x and 6.x, Check Point MetaIP 5. To disable the LRS DHCP server, use the Webmin 'System / Bootup and shutdown' module, click on 'dhcp3-server' and desactivate the 'Start at boot time' option.
You only have to add a few DHCP options in the client's address pools, with your usual DHCP server configuration interface. The options are:
'filename' set to "/tftpboot/revoboot/bin/revoboot.pxe" . It sets the network boot program file to load. This option is also usually available under the name 'Option DHCP 67, BootFile Name'.
'next-server' set to the LRS IP address. It is usually available under the name 'Option DHCP 66, Boot Server Host Name'.
# change 192.168.0.2 by the server IP next-server 192.168.0.2; filename "/tftpboot/revoboot/bin/revoboot.pxe";
Some DHCP servers (MetaIP 4.x), are unable to boot PXE clients. In that case, a possible workaround is to use on the same network LRS' DHCP and your DHCP server at the same time. In order to achieve this, on the LRS, you need to use the 'PXE only replies' DHCP configuration file (/etc/dhcp3/dhcp.conf.pxeonly), and on your server, to add the 'DHCP 177' option set to the following string: "the.lbs.ip.address:/tftpboot/revoboot".
LRS images can be written to a NAS. For this, you will have to:
Mount the NAS share using NFS on /tftpboot on the server, after having copied the contents of this directory to the NAS.
On the DHCP server, add the DHCP 177 option and set it to the string "the.nas.ip.address:/tftpboot/revoboot".
Windows based NAS cannot work with the LRS because sub-directories cannot be mounted over NFS.
There are two possibilities: the client is PXE compliant or it is not.
PXE is an open industry standard developed by software and hardware vendors. PXE works with a network interface card (NIC) in the PC, and makes the NIC a boot device. The PXE vision is to "Make the network interface a standard, industry-accepted PC boot device." This means adding the NIC to the traditional list of standard boot devices, such as floppy drives, hard disks, and CD-ROMs, that load the operating system or set up programs on the PC. It allows a PC to "network boot".
A list of PXE compatible cards and BIOSes is available in Appendix III.
Many network cards are supported by Etherboot. The full list of LRS supported network cards via Etherboot is found at: ftp://ftp.linbox.com/pub/lrs/pxe/etherboot-pxe/NIC . Linbox has a boot floppy or CD-ROM allowing you to use the LRS with these cards.
If you have a PXE adapter, the installation process is listed below.
At boot, the client performs a DHCP request. The screen display appears as:
Intel UNDI, PXE-xxx (xxxx) Copyright xxxx DHCP MAC ADDR : xx-xx-xx-xx-xx-xx DHCP.../
If the server answers to the request, a menu should be displayed and you're ready to use the LRS to back up the client hard disk.
If you do not see these DHCP requests, your PC may not be configured to boot on the network. Enabling this feature depends on your NIC's type:
Integrated NIC (on Motherboard): Just configure the BIOS boot order to : LAN,(FLOPPY),CDROM,HD-0...
EtherExpressPro100 family: Configure by pressing "Ctrl-S" at boot-time. Choose PXE and boot from LAN before Local boot.
3C905C family: Press "Ctrl-Alt-B" at boot-time. Choose PXE.
RTL8139+PXE ROM: press "Shift-F10" at boot-time. Choose PXE and Network before int18h.
Note: You may have to modify some of the BIOS parameters, especially those of "network boot" in the boot order (enable boot from LAN) and probably disable the "Virus checking" of some BIOS (because the PXE ROM code & LBL might be considered as viruses by the BIOS).
Etherboot ( http://www.etherboot.org ) is an open source software package for creating ROM images to allow network booting.
To create the boot disk you need to download an etherboot-pci.* file from ftp://ftp.linbox.com/pub/lrs/pxe/etherboot-pxe/ which contains all the drivers for PCI NICs. Zdsk and .dsk files are floppy disk images, and .iso or .liso files are ready-to-burn ISO images. If you have an ISA NIC or that the 'all-in-one' driver image does not work, you can try single NIC boot disks found in 'dsk', 'iso' and 'liso' directories. The 'NIC' file can help you to find the right driver for your card with its PCI ids. You can also find more information on supported hardware at http://www.etherboot.org/db/.
To put a .zdsk disk image on a floppy, under Windows, use rawrite or rawritewin (http://www.fdos.org/ripcord/rawrite/rawwritewin-0.6.zip).
With Linux, use dd: dd if=bootdisk.dsk of=/dev/fd0
Then, boot with this floppy. The LRS menu should be displayed on the client screen.
If the network boot does not succeed, you can also try our old etherboot based bootdisk (not PXE): ftp://ftp.linbox.com/pub/lrs/pxe/etherboot-non-pxe-old/. If it still fails, please email Linbox and give us your network card model, so that we can tell you as soon as possible if your network card could be supported in the future.