Re: amanda.conf

paolo Cerini wrote:

BUILT_MACH="Linux MILTEST 2.4.20-8 #1 Thu Mar 13 17:54:28 EST 2003 i686 i686 i386 
GNU/Linux"
CC="gcc"
CONFIGURE_COMMAND="'./configure' '--with-user=test' '--with-group=test'

>   '--with-configdir=/usr/local/etc/amanda/Daily'"

Many problems :-)

First you should find a group that has read permission to the
disks.  Usually this is "disk" on Linux.  And it's better to make
a dedicated user for amanda, because in the home directory
of that user you need to create some files (.amandahosts).
If you insist on using user 'test' (for testing phase only),
that's should be fine, but you will have trouble using something
else than gnutar for backups (because dump needs to read the raw
disks, which user test can't -- gnutar works because it uses a
suid-root-wrapper provided by amanda).

You mix up the concept "Config" in amanda with one of its files.
Then the configdir should be a directory that contains all the
configurations.  A configuration in amanda contains several files
(amanda.conf, disklist), and they are grouped in a directory named
like the config and that directory is put into the "configdir".
So if you config is named "Daily, you should compile with
   --with-configdir=/usr/local/etc/amanda
which is the default (with --prefix=/usr/local, also default).

This means that inside that directory you have to create a
directory for each Config that you want.  You could for example
have a configuration "Daily" for running the daily
backups, and you could have a configuration "Archive", that you
run once a month and store the resulting tapes offsite, and you
could have a config "Test" where you do all your testing.
Then you have to create three directories:
        /usr/local/etc/amanda/Daily
        /usr/local/etc/amanda/Archive
        /usr/local/etc/amanda/Test
and each of those directories contains at least two files:
amanda.conf and disklist.

OK, for testing we need only one config. Then we create
a directory /usr/local/etc/amanda/Daily.
The config is named "Daily".  Inside that directory there
should be at least two files: "amanda.conf" (with the
configuration parameters for that config) and "disklist" (with
the list of hosts/disks/types needed to backup).

defs:
DEFAULT_SERVER="MILTEST" DEFAULT_CONFIG="DailySet1"


Amanda also has a notion of "default config" and that seems
to be set to DailySet1.  This means that amanda expects
a directory /usr/local/etc/amanda/DailySet1 and inside
that directory there should be two files "amanda.conf"
and "disklist".

[root@MILTEST amanda-2.4.4]# amdump amanda.conf
amdump: could not find directory /usr/local/etc/amanda/Daily/amanda.conf


You're mixing up the "Config" and one of its files.

You should have said:
        amdump Daily
and then amanda would look for amanda.conf and disklist inside
that directory.  You do not specify the amanda.conf file itself.

DANGER!  Even for testing it is not advised to run the commands as
root!!!  It will work, but now the system will create all its
status files owned by root.  When the time comes that you want to
proceed, and want to run as the amanda user ('test' in your case),
this user will have problems manipulating the status files created
by root!

--
Paul Bijnens, Xplanation                            Tel  +32 16 397.511
Technologielaan 21 bus 2, B-3001 Leuven, BELGIUM    Fax  +32 16 397.512
http://www.xplanation.com/          email:  Paul.Bijnens AT xplanation DOT com
***********************************************************************
* I think I've got the hang of it now:  exit, ^D, ^C, ^\, ^Z, ^Q, F6, *
* quit,  ZZ, :q, :q!,  M-Z, ^X^C,  logoff, logout, close, bye,  /bye, *
* stop, end, F3, ~., ^]c, +++ ATH, disconnect, halt,  abort,  hangup, *
* PF4, F20, ^X^X, :D::D, KJOB, F14-f-e, F8-e,  kill -1 $$,  shutdown, *
* kill -9 1,  Alt-F4,  Ctrl-Alt-Del,  AltGr-NumLock,  Stop-A,  ...    *
* ...  "Are you sure?"  ...   YES   ...   Phew ...   I'm out          *
***********************************************************************