>How can I tell whether anything good is happening with my amanda
>backup? ...
The usual way is to look at the E-mail report you get after every run.
You are getting those, right? If not, you'd better take a look at
"mailto" in amanda.conf.
Take a look at amanda.conf for the "logdir" variable. In that directory
should be a bunch of files named log.YYYYMMDD.N. You can regenerate a
report like this:
amreport <CONFIG> -l <LOGDIR>/log.YYYYMMDD.N
>Which to me indicates that I successfully made a backup on Aug. 17, Dec. =
>21 and 26. ...
That only says Amanda rewrote the tape label on those days. It does
not mean anything useful happened.
>I attached amdump and the log file, if they help.
And they show all sorts of problems (which would also be in the E-mail):
error result for host isgadmin disk /dev/hda2: isgadmin: [access as amanda not
allowed from [EMAIL PROTECTED]]
error result for host isgadmin disk /dev/hda1: isgadmin: [access as amanda not
allowed from [EMAIL PROTECTED]]
See the FAQ at www.amanda.org for information on this error.
planner: FAILED mailinglists /dev/hda1 0 [missing result for /dev/hda1 in
mailinglists response]
planner: FAILED virtual /dev/hda1 0 [missing result for /dev/hda1 in virtual
response]
planner: FAILED centernet /dev/sda1 0 [missing result for /dev/sda1 in centernet
response]
These say Amanda was not able to get any estimates from these hosts.
Later on:
driver: result time 1743.049 from dumper0: FAILED 01-00004 [access as amanda not
allowed from [EMAIL PROTECTED]] open of /home/amanda/.amandahosts failed
I don't know why this happened, but it's bad.
The first rule with Amanda is always to run "amcheck <CONFIG>". If it's
not happy (which I'm pretty sure it will not be for you), amdump is also
not going to work.
>-Kevin Zembower
John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
