|
Initial disk of amrecover set up incorrectly
2002-12-20 04:34:55
amrecover will in my setup make a completely wrong guess about what disk
to consider at startup in most cases. The example output included below
should illustrate the problem; /usr/freeware/apache is not on the /u
filesystem, and it has a separate disklist entry. Any ideas what is going
on?
praha 17# cd /usr/freeware/apache
praha 18# amrecover ks
AMRECOVER Version 2.4.2p2. Contacting server on amanda-server ...
220 praha AMANDA index server (2.4.2p2) ready.
200 Access OK
Setting restore date to today (2002-12-20)
200 Working date set to 2002-12-20.
200 Config set to ks.
501 No index records for host: praha. Invalid?
Trying praha.kscanners.no ...
501 No index records for host: praha.kscanners.no. Invalid?
Trying praha.advim.no ...
501 No index records for host: praha.advim.no. Invalid?
Trying praha ...
501 No index records for host: praha. Invalid?
Trying www ...
501 No index records for host: www. Invalid?
Trying ftp ...
501 No index records for host: ftp. Invalid?
Trying mx ...
501 No index records for host: mx. Invalid?
Trying fileserv ...
200 Dump host set to fileserv.
$CWD '/usr/freeware/apache' is on disk '/u' mounted at '/u'.
200 Disk set to /u.
Invalid directory - /usr/freeware/apache
amrecover>
--
Toralf Lund <toralf AT procaptura DOT com>
|
| <Prev in Thread] |
Current Thread |
[Next in Thread> |
- Initial disk of amrecover set up incorrectly,
Toralf Lund <=
|
|
|
