>... I have numerous questions about amanda all leading hopefully
>towards making it work. ...
An enviable goal. :-)
>The short story is that now 'amcheck' runs w/o
>errors but when I issue "amdump daily" it appears as if nothing happens and I
>get the prompt back immediately. ...
Pretty early in the script it changes directory to wherever you have
your amanda.conf (.../daily) and then redirects stdout/stderr to a file
named "amdump". If the script runs more or less to completion, it will
rename all the other amdump.<NN> files up by one number and rename the
latest to amdump.1.
So is there anything interesting in that file?
Or here's another interesting thought. Who owns the "daily" directory?
Can your Amanda user create files in it, i.e. does it have rwx access
either through ownership or group membership? If it doesn't, that would
explain a **lot** of the other things you mentioned.
>At some point noticed that there is an amanda-2.4.2 version and it appeared
>as though it is no longer beta. ...
As of a day or two ago.
>... Amcheck still failed and still showed brought to you by Amanda
>2.4.1p1 - is this a key indicator of my problem? ...
It indicates you're still running 2.4.1p1, not 2.4.2. So there must
still be some remains of your old stuff laying around. If you're using
ksh (or bash, I think), you should be able to do "whence amcheck" to
see where it is coming from in your PATH.
>I fianlly was able to get
>amcheck to pass off my install as good. :)
Does it still say 2.4.1p1? If so, I'd say things are still shaky.
>What follows is what I had to do to get amcheck to run successfully. ...
>I had
>to manually create and assign permissions for numerous files and directories
>including ... /var/amanda/curinfo and /index directories,
I think if your Amanda user had had permission to create new entries in
/var/amanda (same rwx comments as above), these two directories would
have been created for you.
Also, they should be configuration specific, i.e. you probably want the
name "daily" in there someplace.
You also should not have had to create the tapelist file, and again, it
might be because of a permissions problem on the parent "daily" directory.
>... /usr/local/sbin/amgetconf as getconf to make amcheck happy. ...
If you're still hunting for getconf, that's another indication you still
have pieces of 2.4.1p1 laying around. That was changed to amgetconf at
least by 2.4.2.
>And
>you are not allowed to select 'Randy' as the answer to that question. grin.
Ummm, let's not be taking options off the table, please. :-) :-)
>Randy Cordell.
John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
