>Can't determine disk and mount point from $CWD
Amanda takes your current working directory ($CWD) and tries to figure
out what disk it is related to in disklist on the assumption you started
amrecover from the client and disk you want to do the restore into.
The message says it was not able to do that, which could be caused by
any number of things.
What disklist entry do you think should match your current working
directory?
Do you have index set to "yes" for the dumptype associated with that
disk?
>amrecover> setdisk /dev/hda1
>598 Error: disk not found.
That's the correct syntax, but again, it is not finding the index records
that match "/dev/hda1". Same questions as above: is that a disklist
entry, and do you have indexing turned on?
One way to see what Amanda is working with is to look at your indexdir
entry in amanda.conf. That points to a directory. In there is one
directory per client, and in each client directory is one more directory
for each disk (that has indexing turned on). Finally, in those
directories, are the gzip'd index files themselves.
Note that Amanda is picky about things matching. For instance, if
your disklist entry is "hda1", you cannot enter "/dev/hda1" (or the
mount point). Some of that can be worked around with symlinks, but
amrecover usually gets it right when properly set up.
Another place to look for clues is /tmp/amanda/amindexd*debug on your
server (clark).
John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
