>What happens if "netusage" isn't defined? ...
There are defaults for all amanda.conf variables. See the amanda(8)
man page. In this particular case, it's 300 KBytes/s.
>Will amanda use all available bandwidth.
Sigh. Time, yet again, to explain how Amanda thinks about bandwidth :-).
The "interface" (netusage) entries you put in amanda.conf should
be thought of as pools of resources, somewhat like the holding disk.
When Amanda is considering whether to start a particular backup, it takes
the estimated size and historical data for how fast it has gone in the
past and generates an estimated bandwidth for this run. Then it checks
the corresponding "interface" pool to see if there is enough left. If so,
the backup is started (assuming all the other tests pass) and the amount
is subtracted from the pool. When it's done, the value is added back.
That's the complete and total extent of the usage of the amanda.conf
interface values. Once Amanda actually starts transferring data, it does
not do any throttling, but shoves data as fast as it can, just like any
other network application (e.g. ftp). It relies on the underlying OS
and hardware to do flow control.
Amanda also pays no attention to which physical interface is used,
regardless of how you name your amanda.conf "interface" section. That is
also left up to the OS and hardware. So it's probably less confusing
to name your sections logically ("back-room-fddi-ring") rather than with
"real" hardware device names ("hme0").
So the answer to your question is that Amanda will use all the bandwidth
it is given once it starts doing a backup, but you have no control over
that value (unless you mess with the OS or hardware).
>Joshua Warchol
John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
