I have set up Amanda to backup one of our development servers using GNU tar
and gzip compression. Before running amdump, I cleaned out the curinfo,
index and logs directories, removed the debugging info under /tmp/amanda,
removed the previous dump files on the holding disk and cleaned up the
client-side stuff (amandates and the gnutar-lists directory). Amanda
successfully ran full backups on each filesystem using the default
dumptypes that were defined for comp-root-tar and comp-user-tar (I verified
that indexing is turned on).
When I run amrecover, I am only seeing a partial listing of the files and
directories on one of the filesystem. For the other filesystems, amrecover
is complaining that it cannot find an index. I checked the index directory
and they all exist. I have examined the index files and they look okay.
The files and directories that are missing under amrecover are listed in
the index files. I have examined the dumps themselves and listed the table
of contents. The files and directories that are missing under amrecover
show up in the table of contents. I have ensured that I have the correct
host, disk and date when running amrecover. The debug logs in /tmp/amanda
on the backup server do not show anything interesting, nor do the logs
under the logs directory. I was able to successfully recover a file that
_was_ listed using amrecover.
This same problem happened with the initial backups that I ran last night
on all three of our development servers so I wiped everything clean and
tried again this morning on only one server. I am using Amanda version
2.4.2p2 under Solaris 7. I am running tapeless backups using GNU tar and
gzip.
Any ideas?
Thanks,
Chris O'Regan
