Thanks for the direction. The sendsize.debug shows it starting at

=========================================================================
sendsize: debug 1 pid 25350 ruid 1026 euid 1026 start time Tue Feb 18
23:11:08 2
003
/usr/local/libexec/sendsize: version 2.4.2p1
calculating for amname '/directory', dirname '/directory'
sendsize: getting size via gnutar for /directory level 0
sendsize: missing exclude list file "/usr/local/lib/amanda/exclude.gtar"
discard
ed
sendsize: running "/usr/local/libexec/runtar --create --directory
/cmroot/base/r
cs --listed-incremental
/usr/local/var/amanda/gnutar-lists/pitbullcm-lab.tcs-sec
.com_cmroot_base_rcs_0.new --sparse --one-file-system --ignore-failed-read -
-tot
als --file /dev/null "
sendsize: spawning "/usr/local/libexec/runtar" in pipeline
sendsize: argument list: "/usr/local/bin/tar" "--create" "--directory"
"/directory" "--listed-incremental"
"/usr/local/var/amanda/gnutar-lists/hostname-l
ab.domainname_directory_0.new" "--sparse" "--one-file-system" "--ignore-f
ailed-read" "--totals" "--file" "/dev/null" "."
Total bytes written: 19815997440 (18GB, 2.0MB/s)
.....
sendsize: pid 25350 finish time Wed Feb 19 01:49:25 2003
==========================================================

So that took about 2 hours 40 minutes.  Would that require the etimeout to
be upped to ~9000?

Currently the etimeout and the dtimeout are at the defaults, 300 and 1800.

You mentioned I should look into a newer tar version.  Currently I have
1.13.19.  I have not found
a Solaris source for 1.13.25 as of yet.  Maybe that would speed things up.
The directory
does have about 6000+ files in it.

Thanks for the feedback,
Shawn


-----Original Message-----
From: owner-amanda-users AT amanda DOT org
[mailto:owner-amanda-users AT amanda DOT org]On Behalf Of Dietmar Goldbeck
Sent: Wednesday, February 19, 2003 3:43 AM
To: Shawn Sanders
Cc: amanda-users AT amanda DOT org
Subject: Re: NAK: amandad busy


On Tue, Feb 18, 2003 at 04:24:24PM -0500, Shawn Sanders wrote:
> I am adding a new system to our amanda backup system.  The system has a
> LARGE filesystem so I have
> to use tar to divide it up some.  amcheck runs fine, but when amdump runs
I
> get the following error
> in the email report : Request to hostname timed out
>
> The problematic client (Intel Solaris 8) gets this in the amandad.debug
>
> Amanda 2.4 NAK HANDLE 000-D0A00708 SEQ 1045598401
> ERROR amandad busy
>
> The server is running Redhat 7.2.
>
> The two directories I am backing up are 17/18GB.  The tar seems to be
taking
> several hours
> to complete.  Do I need to adjust a wait state or perhaps I am missing
> something else.
>

Please check the sendsize debug files and find out how long estimates
are taking. If you are using an older version of GNUtar, estimates are
extremely slow. I recommend upgrading to 1.13.25

I would increase etimeout and dtimeout. From man amanda

      etimeout int
              Default: 300 seconds.  Amount of time per disk on a
              given client that the planner step of amdump will wait
              to get the dump size estimates.  For instance, with the
              default of 300 seconds and four disks on client A,
              planner will wait up to 20 minutes for that machine.  A
              negative value will be interpreted as a total
              amount of time, instead of a per-disk value.

       dtimeout int
              Default: 1800 seconds.  Amount of idle time per disk on
              a given client that a dumper running from within
              amdump will wait before it fails with a data timeout error.


   Ciao
     Dietmar

--
 Alles Gute / best wishes
     Dietmar Goldbeck         E-Mail: dietmar.goldbeck AT schotterweg DOT de
Reporter (to Mahatma Gandhi): Mr Gandhi, what do you think of Western
Civilization?  Gandhi: I think it would be a good idea.