>Ok, this is all my faul.
By definition, it's always the user's fault, never Amanda's. :-)
>Here is what amrecover has to say:
>...
The first thing I'd do is "amadmin DailyDump find <client> <disk>".
That will tell you what tapes have what images.
Assuming Amanda tells you good things (if it doesn't we'll have to deal
with that, but let's assume it does), prepare the new disk area (e.g.
mkfs/newfs it, mount it, etc) and cd to it. Then load the full dump
tape you found above and fsf to the image (the find output tells you
the file on the tape).
Now do the restore. Assuming the client isn't the tape server, and that
you're using GNU tar, it would be something like this (on the client,
in the area to be restored):
rsh -n <tape-server> /path/to/amrestore -p </path/to/tape> <client> <disk> \
| gtar xf - .
If there aren't a bajillion files, you might want to add 'v' to the gtar
flags so you can have the nice warm feeling of seeing things actually
get reloaded.
If you have incrementals to do, repeat the above for the last level 1,
then the last level 2 and so on.
Then repeat the whole thing for the next client/disk.
You might look at:
ftp://gandalf.cc.purdue.edu/pub/amanda/amr-all
to get a summary of what tapes are needed, etc. But in your current
environment, I wouldn't necessarily believe it 100% without some
independent confirmation (e.g. "amadmin <config> find ...").
>Stan Brown
John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
