|
Re: Estimate timeouts after upgrade and easy way to test just one backup target
2006-04-19 11:59:19
|
Subject: |
Re: Estimate timeouts after upgrade and easy way to test just one backup target |
|
From: |
"Ram \"TK\" Krishnamurthy" <tk AT zmanda DOT com> |
|
To: |
Fran Fabrizio <fran AT cis.uab DOT edu> |
|
Date: |
Wed, 19 Apr 2006 08:59:44 -0700 |
Fran Fabrizio wrote:
I recently upgraded the server side to 2.4.5 and a subset of my hosts
are consistently timing out on estimates each night, even after doubling
the time limit for estimates. The affected clients are running
2.4.4p2. Is there a known issue here? Some clients also running
2.4.4p2 are working, so I am not sure that is the problem.
amcheck reports no errors on any of the hosts.
I would like to debug this by not having to wait for the nightly backup
to fail but by just testing one backup target, tweaking, and testing
again. I could define another config altogether, but then I have to
load tapes for it, etc... is there an easy way to just force a run, but
of only one target, without adversely affecting things when I go back to
the full run?
Why not try a config backing up to disk and see if there are any changes
in behavior?
Further, any other speculation about why estimate timeouts would start
happening in a subset of clients but not other clients in a config where
the only change is a server upgrade from 2.4.4 to 2.4.5 which
corresponded with a move from redhat 9 to fedora core 5 for the server?
Thoughts about the best way to debug?
Any commonality from a network perspective among those clients that
timeout - like they are behind a firewall or a particular class of
subnets and the likes?
Thanks
tk
Thanks,
Fran
--
Ram "TK" Krishnamurthy
Amanda Wiki: http://wiki.zmanda.com
Amanda Forums:http://forums.zmanda.com
|
|
|
