个人工具

Quick HOWTO : Ch1 : Network Backups With Rancid/zh

来自Ubuntu中文

落寞三少讨论 | 贡献2008年8月4日 (一) 09:54的版本

跳转至: 导航, 搜索



简介

一个被网络管理忽略的地方是失败的网络备份硬盘的设置,悲哀的是这只是造成灾难性打击的开始。幸运的是Linux/Unix有一个叫Rancid的开源包,它可以自动地、用命令的方法快速完成为大多数驱动器设置备份这项工作。 这个产品可以从 rancid website里下载得到,在Concurrent Versions System (CVS)中还增加旧的自动归档的好外.这个指南将会给您显示如何快速安装和设置它为你的网络备份需要。


安装Rancid

Under Fedora Linux, installation is relatively easy, but there are a large number of simple steps to follow. Let's begin:

在Fedora Linux 安装的Rancid是十分简单的,但接下来有很多简单的步骤,现在我们开始:

1. Rancid uses the expect programming language to operate which you will have to install in advance. Use the rpm command with the -q qualifier to determine whether you have expect installed. In this case, it isn't so the yum command is used to do so.

[[email protected] tmp]# rpm -q expect
package expect is not installed
[[email protected] rancid-2.3.2a2]# yum -y install expect
Repository updates-released already added, not adding again
Repository base already added, not adding again
Setting up Install Process
...
...
...
[[email protected] rancid-2.3.2a2]#

2) Create a Linux group named netadm which will eventually have access to the Rancid directory.

[[email protected] tmp]# groupadd netadm

3) Create a user named rancid that will be used to run the network device backups every night. Here we make rancid a member of the netadm group and make /usr/local/rancid its home directory.

[[email protected] tmp]# useradd -g netadm -c "Networking Backups" -d /usr/local/rancid rancid

4) Create a directory called /usr/local/rancid/tar and use the wget command to get the latest version of the Rancid tar file from its web site.

[[email protected] tmp]# mkdir /usr/local/rancid/tar
[[email protected] tmp]# cd /usr/local/rancid/tar
[[email protected] tar]# wget ftp://ftp.shrubbery.net/pub/rancid/rancid-2.3.2a2.tar.gz
--01:14:26--   ftp://ftp.shrubbery.net/pub/rancid/rancid-2.3.2a2.tar.gz
                     => `rancid-2.3.2a2.tar.gz'
...
...
...
100%[==============================>] 280,435           153.28K/s
 
01:14:58 (152.78 KB/s) - `rancid-2.3.2a2.tar.gz' saved [280,435]
[[email protected] tar

5) Rancid needs to be compiled. Next, you will need to extract the files from the Rancid tar file as a pre-compilation step. In this case the file is named rancid-2.3.2a2.tar.gz so the extraction process will place all the preliminary files in a directory named rancid-2.3.2a2.

[[email protected] tar]# tar -xvzf rancid-2.3.2a2.tar.gz
rancid-2.3.2a2/bin/Makefile.am
rancid-2.3.2a2/bin/Makefile.in
rancid-2.3.2a2/bin/alogin.in
...
...
...
rancid-2.3.2a2/man/lg.conf.5.in
rancid-2.3.2a2/man/rancid.conf.5.in
rancid-2.3.2a2/man/lg_intro.1.in
[[email protected] tar]#

6) Enter the directory.

[[email protected] tar]# cd rancid-2.3.2a2
[[email protected] rancid-2.3.2a2]#

7) In this directory there is a README file with instructions on what to do next. You can view it using the less command to see the various configuration options offered. We will proceed in this example by using a very simple scenario.

[[email protected] rancid-2.3.2a2]# less README

8) Prepare the Rancid package for compiling with the configure command. Here, the --prefix switch is used to set the default directory to match the /usr/local/rancid/ home directory of our rancid user.


[[email protected] rancid-2.3.2a2]# ./configure --prefix=/usr/local/rancid/
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for gawk... gawk
...
...
...
config.status: creating include/config.h
config.status: include/config.h is unchanged
config.status: executing depfiles commands
[[email protected] rancid-2.3.2a2]#

9) Install the package with the make command.

[[email protected] rancid-2.3.2a2]# make install
Making install in .
gmake[1]: Entering directory `/usr/local/rancid/tar/rancid-2.3.2a2'
gmake[2]: Entering directory `/usr/local/rancid/tar/rancid-2.3.2a2'
gmake[2]: Nothing to be done for `install-exec-am'.
test -z "/usr/local/rancid//share/rancid" || mkdir -p -- "/usr/local/rancid//share/rancid"
...
...
...
/usr/bin/install -c 'downreport' '/usr/local/rancid//share/rancid/downreport'
gmake[2]: Leaving directory `/usr/local/rancid/tar/rancid-2.3.2a2/share'
gmake[1]: Leaving directory `/usr/local/rancid/tar/rancid-2.3.2a2/share'
[[email protected] rancid-2.3.2a2]#

10) There is a sample password file named cloginrc.sample. You'll need to copy it to the /usr/local/rancid/ home directory as the hidden file /usr/local/rancid/.cloginrc.

[[email protected] rancid-2.3.2a2]# cp cloginrc.sample /usr/local/rancid/.cloginrc
[[email protected] rancid-2.3.2a2]#

11) Finally you will need to set the .cloginrc file permissions to be readable by the rancid user and the new netadm Linux group. You will also have to change the ownership and permissions of the home directory in a similar fashion.

[[email protected] rancid-2.3.2a2]# chmod 0640 /usr/local/rancid/.cloginrc
[[email protected] rancid-2.3.2a2]# chown -R rancid:netadm /usr/local/rancid/
[[email protected] rancid-2.3.2a2]# chmod 770 /usr/local/rancid/

Now that the installation is complete, you'll need to do some initial configuration to get Rancid to work. Don't worry, it is fairly straight forward.