Re: Configuring Auth SSH for a client behind a firewall

The host name in the Host line must be the exact name amanda use. * Yes, we have the exact name on the Host line. And we are able to SSH from the command line using this name. Is there any special config on the Client side? There is no eveidence on the client side such as an amandad debug file t

Re: How do send dumped DLEs to tape earlier?

On Fri, Dec 10, 2010 at 10:02:40PM +0100, Marc Muehlfeld wrote: > Hi, > > is there a way, I can tell amanda not to collect data and then transfer it > to tape? Currently there is mostly 1 DLE direclty send to tape and then > it's collecting data before the rest is also written: Not certain I unde

Re: Configuring Auth SSH for a client behind a firewall

Debbie O Connell wrote: Hi, We are trying to setup Amanda for 1 client behind a firewall with Auth SSH for the first time. The machines behind the firewall are all NATed. The firewall will not allow us to port redirect port 22. As a result, all the machines behind the firewall have non-standa

Configuring Auth SSH for a client behind a firewall

Hi, We are trying to setup Amanda for 1 client behind a firewall with Auth SSH for the first time. The machines behind the firewall are all NATed. The firewall will not allow us to port redirect port 22. As a result, all the machines behind the firewall have non-standard SSH port numbers. For

Re: having problem with amrecover under 3.2.0

amanda-client.conf is not required. Maybe you added some config in it? Jean-Louis McGraw, Robert P wrote: After a little more searching I found the problem. Even thought the debug files did not say, it seem that I needed an amanda-client.conf file in ~amandabackup/etc/amanda. Once I added the

How do send dumped DLEs to tape earlier?

Hi, is there a way, I can tell amanda not to collect data and then transfer it to tape? Currently there is mostly 1 DLE direclty send to tape and then it's collecting data before the rest is also written: SUMMARY part real estimated size size w

RE: having problem with amrecover under 3.2.0

After a little more searching I found the problem. Even thought the debug files did not say, it seem that I needed an amanda-client.conf file in ~amandabackup/etc/amanda. Once I added the file amrecover started working. This might be a check that needs to be added. Thanks for your help Robert

Re: having problem with amrecover under 3.2.0

amrecover get a timeout, you must check why the server did not respond. Do hertz (128.210.3.201) in the name of the amanda server? What's the inetd config for the amanda service on hertz? What's in the amandad.*.debug file on hertz? Any error in syslog? Jean-Louis McGraw, Robert P wrote: Runnin

having problem with amrecover under 3.2.0

Running amanda 3.2.0 on a Sun Solaris 10 server. ./amrecover archive AMRECOVER Version 3.2.0. Contacting server on hertz ... [request failed: timeout waiting for ACK] 123][r...@hertz]:amanda/client/archive# cat amrecover.20101210142059.debug Fri Dec 10 14:20:59 2010: amrecover: pid 275 ruid 0 e