个人工具

“Quick HOWTO : Ch1 : Network Backups With Rancid/zh”的版本间的差异

来自Ubuntu中文

跳转至: 导航, 搜索
安装 Rancid
第35行: 第35行:
 
   
 
   
  
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.
+
4) 创建一个名为 /usr/local/rancid/tar 的目录并用wget命令从网站获得最新版本的Rancid压缩包
 
+
 
  [[email protected] tmp]# mkdir /usr/local/rancid/tar
 
  [[email protected] tmp]# mkdir /usr/local/rancid/tar
 
  [[email protected] tmp]# cd /usr/local/rancid/tar
 
  [[email protected] tmp]# cd /usr/local/rancid/tar

2010年11月1日 (一) 00:36的版本



简介

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


安装 Rancid

在 Fedora Linux 安装 Rancid 十分简单,但接下来还有一些简单的步骤,现在我们开始: 1. 要想使用 Rancid,你必须先安装编程语言。用 RPM 命令 -Q 查看你是否决定安装,在这里,是不可以用 yum 命令安装的。

[[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)为将访问 Rancid 目录增加一个名为 netadm 的 linux 组名 。

[[email protected] tmp]# groupadd netadm

3)为了每晚能运行这个网络备份设备,我们在 netadm 工作组里新建一个名为 rancid 的用户,和新建一个目录/usr/local/rancid 。

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

4) 创建一个名为 /usr/local/rancid/tar 的目录并用wget命令从网站获得最新版本的Rancid压缩包

[[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.