Just a follow up on this issue, which isnt makeing
sense to me at all.
I shut down the amanda client via xinetd, and ran
the backups and the backups worked perfectly. It went over
the client with the report mentioning that the client
was not responsive.
However, I had someone (by accident?) turn off the power
to one of the amanda clients. This caused the backup on the
server to continue to wait for the estimate of the client
for hours (over 10 hours).
I have tried using calcsize, client, and no entry for
the estimate (I dont know what the default is, calcsize (?) ).
No error messages in the logs, just the hanging server waiting
for the estimate of the non responsive client.
I will be trying different options to see what occurs.
Thanks for any input.
On Wed, 30 Mar 2011, Tim Johnson wrote:
Not sure why it is puking on the event of a
non responsive machine (either not on the network or
estimate time out -- which is set for 8000 sec right now)
I will force a machine down and test again.
Thanks in advance.
On Wed, 30 Mar 2011, Jean-Louis Martineau wrote:
Tim Johnson wrote:
Hello all...
This might be a silly quetion, however there
are times that some clients are down. My setup
aborts the backups, and then looses the indexes/log files
of pervious backup history.
So two questions, is there an option somewhere in the config to
tell amanda to overlook any clients that are down but still
continue on with the rest of the clients.
That's what amanda should do, there is no way to do differently.
You should explain why your setup aborts the backup, that's what must be
fixed.
Jean-Louis
