Hi John!
> >I logged in as root, changed in the directory /usr/local/sbin and type
> >amrecover and become the following error:
> >
> >root@fileserver: /usr/local/sbin > ./amrecover
> >AMRECOVER Version 2.4.2-19991216-beta1. Contacting server on fileserver
...
> >amrecover: Unexpected server end of file
>
> Are the amindexd and amidxtapes services installed in inetd.conf on
> "fileserver"? What's in /tmp/amanda/amindexd*debug on "fileserver"?
In my inetd.conf i have the following entries for amanda:
# amanda backup server with indexing capabilities
#
amandaidx stream tcp nowait amanda /usr/sbin/tcpd
/usr/local/libexec/amindexd amindexd
amidxtape stream tcp nowait amanda /usr/sbin/tcpd
/usr/local/libexec/amidxtaped amidxtaped
amanda dgram udp wait amanda /usr/sbin/tcpd
/usr/local/libexec/amandad amandad
#
Here is the Logfile from amindexd.debug:
amindexd: debug 1 pid 7591 ruid 560 euid 560 start time Mon Nov 13 08:55:29
2000
amindexd: version 2.4.2-19991216-beta1
> You will probably have to provide some other parameters to amrecover, too.
> Like the config name, the tape device name, etc. See the man page.
yes, i called the recover as root (amrecover Daily -d /Dev/nst0 -t
fileserver) from directory /test
> >I want (must) to recover a complete directory, because it�s lost on the
> >Fileserver (and i don�t know why).
>
> If it's critical you get this directory back and don't want to take
> the time to get amrecover working, remember that you don't need it.
> You can use amrestore and pipe the image back to the client where you
> run the appropriate restore command by hand. See docs/RESTORE or the
> "book chapter".
Hmmm....the tape server is a fileserver where my clients are working.
I must recover the directory on the fileserver who is the amanda tape
server.
Bye Juergen
