>Dumper continues to run on the server (it is in the "top" list) but is
>in idle mode and has "netio" in the WAIT field. I'm not sure what this
>means, is it problem from my client who stops sending messages?
You'd have to ask someone familiar with your OS what "netio" means.
Do you have multiple dumper processes? There should be as many as
you have inparallel set to in amanda.conf. When driver does not have
anything for them to do, they could easily be sitting there with a status
like this.
One way to check is to look at the amdump log file. You will see
FILE-DUMP or PORT-DUMP commands from driver to one of the dumpers, and
the specific dumper will be listed (e.g. "dumper3"). Earlier in the file
it tells you which dumper matches which PID. From that information you
should be able to tell what the dumper is supposed to be doing.
If it's supposed to be doing a dump, I'd then look at the holding disk
and see if the image is growing. I'd also look on the client and see
if amandad/sendbackup and GNU tar (or dump) is running and use tools
like lsof there to see if they are making any progress.
>Plus, there are two "taper" processes that are in idle too.
That's normal. One is waiting on driver to give it something to do.
The other is waiting on the first taper to coordinate writing to tape.
You can tell if taper is busy or idle much the same as you can tell about
a dumper. Look for FILE-WRITE or PORT-WRITE commands and the matching
DONE indications. You can also look at the last "stat" message which
lists whether taper is active or not.
>I think this may be related to my tape drive who seems to have some
>trouble....
I know I'm going to regret asking this :-), but what kind of trouble?
>It is a STD-7000 from sony and I've used the tapetype from the entry in
>faq-o-matic.
The tapetype is only used to help Amanda compute what will fit. It has
no effect on the actual use of the drive.
John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
