I figured out the problem, after modifying "amadmin disklist" so that
it prints out the spindle number, at least in amanda-24.4p3.
I had lines in disklist which looked something like this:
localhost //bunting/c$ root-sambatar eth0
eth0 was parsed as a spindle number of 0, in addition to being parsed as
an interface value of eth0.
Here's the output from the modified "amadmin normal disklist"
line 56:
host localhost:
interface ETH0
disk //bunting/c$:
program "GNUTAR"
priority 0
dumpcycle 28
maxdumps 4
maxpromoteday 10000
strategy STANDARD
compress SERVER BEST
comprate 0.50 0.50
auth BSD
kencrypt NO
holdingdisk YES
record YES
index YES
skip-incr NO
skip-full NO
spindle 0
It looks like maxdumps is picked up correctly, but the spindle value
of 0 may be preventing multiple dumpers from running. I'll give it
another try soon, and suggest a few patches to the amanda-hackers list.
Kevin Dalley <[EMAIL PROTECTED]> writes:
> "Stefan G. Weichinger" <[EMAIL PROTECTED]> writes:
>
>>
>> Lookup the usage of the parameter maxdumps.
>>
>> man amanda:
>>
>> maxdumps int
>>
>> Default: 1.
>> The maximum number of backups from a single host that Amanda will attempt to run
>> in parallel.
>>
>> Increase this one and tell us the results.
>>
>
>
> That was my starting point. I set maxdumps to 4, but only in the
> dumptypes for amanda. I'm still using the default of 1 for other
> backups.
>
> Should I set maxdumps to 4 globally rather than locally. Here are the
> relevant dumptypes.
>
> define dumptype root-sambatar {
> program "GNUTAR"
> comment "Root partitions dumped with tar"
> options index
> compress server best
> maxdumps 4
> priority low
> }
>
> define dumptype user-sambatar {
> comment "User partitions dumped with samba"
> root-sambatar
> priority medium
> }
>
>
> --
> Kevin Dalley
> [EMAIL PROTECTED]
>
--
Kevin Dalley
[EMAIL PROTECTED]
