On Wednesday 18 September 2002 06:33, Neil wrote:
>Is someone out there kind enough to share a good howto on
> installing amanda? I am planning to reinstall my non-working
> f****** amanda. I have tried the INSTALL file that comes with it.
> I also have posted earlier about the issue I was encountering but
> never had any replies to that POST.
>
>Thanks.
I've been keeping up with the 2.4.3 branch, which means I rebuild it
everytime Jean-Louis makes another snapshot available.
I do the builds in /home/amanda/amanda-version-number by unpacking
tha tar.gz's there as root, then do a "chown -R amanda:disk *" to
set the owner:group of the unpacked files. Then I call up whatever
file manager you use and copy the gh.cf file from the previous
version's top level directory to the new versions top level
directory. This is the file that contains all the options one
needs to configure amanda, and it looks like this:
--------------------------------
#!/bin/sh
# since I'm always forgetting to su amanda...
if [ `whoami` != 'amanda' ]; then
echo
echo "!!!!!!!!!!!! Warning !!!!!!!!!!!!"
echo "Amanda needs to be configured and built by the user amanda,"
echo "but must be installed by user root."
echo
exit 1
fi
make clean
rm -f config.status config.cache
./configure --with-user=amanda \
--with-group=disk \
--with-owner=amanda \
--with-tape-device=/dev/nst0 \
--with-changer-device=/dev/sg1 \
--with-gnu-ld --prefix=/usr/local \
--with-debugging=/tmp/amanda-dbg/ \
--with-tape-server=192.168.1.3 \
--with-amandahosts \
--with-configdir=/usr/local/etc/amanda
--------------------------------------
Customize to suit of course, particularly the with-tape-server=
line, and whatever devices will be used to access the tape drive
and robot on your system.
Then with the prelims out of the way, cd to the new versions tree,
do an "su amanda" (you do have a user amanda don't you? And amanda
is a member of group disk? Ok, just checking:)
and do
#>./gh.cf
which is the name of the above file.
when the configure is done;
#>make
get back to root
#>exit
and
#>make install
All done, all the execution perms are set correctly and amanda is
ready to use.
If you don't already have the working configuration setup, then you
will have to use (as amanda, not root!) the amcheck utility to help
you pinpoint the missing files and to actually get it ready for
use, the syntax being "amcheck /config/" where /config/ is the name
of the subdir in (from above, /usr/local/etc/amanda/config) where
all of amandas controlling file, and her record keeping, will live.
If running a later RH system, RH is now using xinetd instead of
inetd, and you will need this file, named amanda, to be placed in
your /etc/xinetd.d directory.
------------------------------------------
# default = off
#
# description: Part of the Amanda server package
# This is the list of daemons & such it needs
service amanda
{
disable = no
socket_type = dgram
protocol = udp
wait = yes
user = amanda
group = disk
groups = yes
server = /usr/local/libexec/amandad
}
service amandaidx
{
disable = no
socket_type = stream
protocol = tcp
wait = no
user = amanda
group = disk
groups = yes
server = /usr/local/libexec/amindexd
}
service amidxtape
{
disable = no
socket_type = stream
protocol = tcp
wait = no
user = amanda
group = disk
groups = yes
server = /usr/local/libexec/amidxtaped
}
---------------------------------------
The rest is the a-------s & elbows grunt work of getting all the
needed files touched, directories made according to the output of
amcheck. Note that WARNING's aren't fatal as they will be created
by amdump, but I prefer to do all that ahead of time just to
prevent last minute gotcha's.
Once amcheck is happy with everything but the tape name it finds,
then you start to apply labels to your rotating tape stock, for my
system I use 20 tapes so the /config/amanda.conf file has
dumpcycle 1 week
tapecycle 20
runtapes 1
runspercycle 1
Ones tapecycle should be at least 2x dumpcycle tapes.
This setup has no provision for long term storage since this is a
home machine setup of 2 machines, with rsync making a mirror of one
machine on the others bigger drive. If I make a mistake and need
to restore, I'll know I need to restore well before the tapecycle
is done and the restore I need has been overwritten, so its
adequate for me. If you want long term storage, then most setup
another /config/ directory and set that one up to always do fulls
(runtapes may have to be expanded in that case) at say weekly
intervals.
3 things to keep in mind. 1) amanda cannot do a filesystem entry in
the disklist that exceeds a singe tapes capacity. And 2) amanda
doesn't ever append to a tape. Also 3) amanda likes to do her own
scheduleing so that about the same amount of tape is used each
night. Let her do it, its much simpler for you that way as she
will figure out how to put a 46 gig drive on a 4gig tape all by
herself. You may need to 'stage' the disklist entry activations as
you get started however to prevent greater than one tapes data on
the first couple of runs.
The first means you may have to use tar rather than dump, and one
can get into religious wars over that, and break your disklist
entries up into manageable sized subdirs of big partitions, like
/usr, which is 36 gigs here but my tapes are only 4 giggers.
And last, useing the drives hardware compression is generally
considered bad because the true capacity of the drive is then
hidden from amanda, who counts bytes *after* any software
compression has been applied and therefore needs an accurate
picture of what the tape can actually hold. Software compression
is generally much more efficient that hardware in terms of space
used on the tape, I have some partitions in my disklist that
regularly occupy less then 15% of the space on the tape that they
use on the hard drive. So turn it off, and do this before any
tapes have been labeled because you can't easily turn it off after
since its recorded on the tape as being compressed.
--
Cheers, Gene
AMD K6-III@500mhz 320M
Athlon1600XP@1400mhz 512M
99.15% setiathome rank, not too shabby for a WV hillbilly
|
