>I noticed that my "in paralel " option in amanda.conf was set to 4.
>Maybe that could be the source of my problem (at least it would explain
>a bandwith overload). I'm only wondering if it affects the dump of
>multiple partitions on the same system or if it is only influencing
>dumps on independant systems.
Inparallel controls the number of dumpers that are started, which in
turn controls the number of backups that are started at the same time,
irregardless of what client is involved. By setting it to one you've
essentially dropped Amanda back to single-threaded operation -- it
will start one backup on one client, wait for that to complete, then
start another.
This has no effect on how many backups are started on a given client
(except that by setting it to one you've pretty much put everything in
"one at a time" mode). That's controlled with maxdumps. So changing
inparallel will not have any effect, unless the client that's crashing
is the taper server itself.
Is maxdumps set higher than one for this client (based on the dumptype)?
You can tell with "amadmin <config> disk <client> <disk>". If so,
set it back to one to see if that helps.
John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
