--On Monday, May 12, 2003 15:55:47 -0700 Gibran Marquez <gmarquez AT indyme DOT 
com> wrote:

As you all know, nobody really cares if you can backup, it's restoring that
really counts!

So prior to having a user's hair on fire screaming they need me to restore a
file, I'm testing my backups and restoring procedures. I'm new to amanda and
have taken it over after a temp installed/configured it, but have been able
to operate amanda and even get new clients up and running.

Problem I'm having is restoring the data.

Amrecover from client where testing files that need to be restored (client
is "filer" and amanda server is "backup"):
-------------
[root@filer luser]# amrecover -s backup
AMRECOVER Version 2.4.3. Contacting server on backup ...
220 backup AMANDA index server (2.4.3) ready.
500 Access not allowed: [access as amanda not allowed from root@filer]
amandahostsauth failed

There's your problem.  Your .amandahosts file on the server doesn't contain
a line allowing connections from that client. On 'backup' add to your
.amandahosts file:

filer   root

You really should be using fully-qualified hostnames (filer.domain.com
instead of just 'filer') for security, but that's not your restore problem.

Frank

-------------

From reading some of the documentation on backupcentral, I changed the index
parameter to yes
 index yes (it used to be commented out)

Any clues as to why this is failing, also "amrecover" seems like it should
work pretty straight forward but any extra gotcha's or additional hints I
may need to know about would be appreciated.

Thanks in advance!!!

-Regards,
Gibran Marquez
*****************************
My text editor can beat up your text editor.

No, _really_.

--
Frank Smith                                             fsmith AT hoovers DOT 
com
Systems Administrator                                  Voice: 512-374-4673
Hoover's Online                                          Fax: 512-374-4501