>... somebody really need there stuff :)
Then first things first. If amrecover is giving you grief, and you
really, really need that file back now, don't use it. Amrecover was
able to tell you the right tape, so mount it by hand and do the amrestore
piped into smbclient (or whatever) by hand.
>Load tape EOS-008 now
>Continue? [Y/n]: y
>Error connecting to tape server: Invalid argument
Since amrecover was able to connect to amindexd without problem, it
should be able to connect to amidxtaped as well.
Start by seeing if /tmp/amanda/amidxtaped*debug is getting updated on the
tape server. If not, start checking the inetd or xinetd configurations
to make sure they are even listening on the amidxtaped port. Another
possibility is that you have TCP wrappers or some other kind of port
restrictions (firewall, NAT, etc) between the amrecover machine and
amidxtaped (but not amindexd) on the tape machine.
>Jens Rohde
John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
