>501 No index records for host: sundev1. Invalid?
>Trying sundev1.corp.walid.com ...
>200 Dump host set to sundev1.corp.walid.com.
>$CWD '/admin1-home/user/dives' is on a network mounted disk
>so you must 'sethost' to the server
>amrecover> sethost admin1
>501 No index records for host: admin1. Invalid?
>Trying admin1.corp.walid.com ...
>200 Dump host set to admin1.corp.walid.com.
>...
>Do you know why I am gettig indexing errors for both hosts?
In the first case (sundev1) Amanda asked the OS what the host name was
and got back the short name (which I usually try to avoid), but what
you have listed in disklist is the fully qualified name (which is the
recommended setup), so the initial guess didn't match. Then Amanda
expanded the name, tried again and found what it wanted. This is more
or less the expected behavior.
The second case (admin1) would have worked without whining if you had
entered the fully qualified name. Since you didn't, the same sequence
of events took place.
>amrecover> lpwd
>/admin1-home/user/dives
>...
>amrecover> add DB2
>Added /user/dives/DB2
>...
>When amrecover finished running extract - i checked the /user/dives
>directory for the file I was trying to restore and it was not there.
That's because you restored user/dives/DB2 into /admin1-home/user/dives.
In other words, look for /admin1-home/user/dives/user/dives/DB2. Note the
double "level" of "user/dives". If you want to restore this "in place",
your current working directory before starting amrecover will have to
be /admin1-home.
>P.S. - No - I did not tell amanda to back up this area via NFS.
Good! :-)
>Denise E. Ives
John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
