If this is your first visit, be sure to
check out the FAQ by clicking the
link above. You may have to register
before you can post: click the register link above to proceed. To start viewing messages,
select the forum that you want to visit from the selection below.

Did you ever get this resolved? I have the exact same problem, and I'm not sure where else to look!

For my output, SUEZ is the backup server and www is the backup client. I can SSH into SUEZ from www just fine using the same private key, and amdump worked perfectly fine, it's just amrecover that's the problem.

The amandad argument goes in the server authorized_keys, you must prepend the key with something like:
from="amanda_client.your.domain.com",no-port-forwarding,no-X11-forwarding,no-agent-forwarding,command="/absolute/path/to/amandad -auth=ssh amindexd amidxtaped"

The amandad argument goes in the server authorized_keys, you must prepend the key with something like:
from="amanda_client.your.domain.com",no-port-forwarding,no-X11-forwarding,no-agent-forwarding,command="/absolute/path/to/amandad -auth=ssh amindexd amidxtaped"

Wow... that makes a lot of sense, and I can connect just fine now. I am having other issues later on in amrecover, but I'll attempt to resolve them myself. I'm still new to this (it's only my second day using amanda). Thanks martineau!