"John R. Jackson" wrote:
>
> >What shows an error occurred? ...
>
> By "error" I meant you didn't see all the entries in amrecover that you
> expected to see. There isn't anything in the sendbackup*debug file to
> indicate what went wrong (or even that anything did go wrong). The more
> useful place to look is the index file (see below).
Thanks for this complete response but you really should have said so in
the first place, esp'ly before firing off a bunch of (testy)
questions. Anyway, the answer to your quandary is that I didn't
install indexing. The INSTALL instructions say "If you are going to use
the indexing capabilities of Amanda, then add these to your inetd.conf
... amandaidx stream .... amidxtape stream ... amidxtaped" (Section
2.1.E.) which indicates its installation and use is optional. Unlike
designers of a certain piece of software, i believe in the the KISS
principle and was trying to get a little backup working before making an
even more complicated mess.
I'm pretty sure i won't be using Amanda now, so yes, i am "just testing"
at this point, but after what is by all appearances a wasted 2 weeks, i
thought it'd be reasonable to pursue finding out why Amanda/tar skipped
6 of 10 items (counting empty directories) in a small, single directory
backup. For what its worth, my suspicion is still that Amanda has a
problem correctly creating and saving the tar --listed-incremental file
in some situations, eg w/.files when indexing is off. I'm not prepared
to postulate an infinite worlds hypothesis and test for all possibilites
(or study source code) though, so i'm hoping someone has a better clue.
george
> >I am not cleaning out everything between tests. I don't know how to do
> >that or what that means.
>
> Since you're having amrecover/index problems, the important thing to
> remove is all the index files related to the test. Run "amgetconf
> <config> indexdir" to see where the top of the index directory is, then
> cd to the host directory within there and then cd to the disk directory
> within that. Remove all the *.gz files. Then when you run another test
> you can be sure amrecover (amindexd) isn't see old data by mistake.
>
> You can zcat the most recent file Amanda creates to see what amrecover
> will have to work with. If you see all the files you expect to, but
> amrecover doesn't show them, then that's one kind of problem (with the
> index file itself or amrecover). If you don't see the files you expect,
> then that's a problem with the backup itself.
>
