On 11/27/2012 12:52 AM, Jon LaBadie wrote:
On Mon, Nov 26, 2012 at 03:34:23PM -0600, Neil Carter wrote:
Greetings:
Yes, I've looked into this, the network engineer (separate group) is not
interested in bonding, so that won't work. I have to use the four NICs as
independent interfaces.
...
I'm assuming the client is just sending the data to the server hostname via
the hosts file, so I'd like to find more detail on how to use the disklist
interface directive, I think. It appears the amandahosts file has more to
do with authentication than actually working like a hosts file.
Thanks!
Neil
As I've not used the interface directive, take this as
a guesstimate.
In amanda.conf you do a mapping of a name and the actual
device. Plus you can set up some options to the interface,
although only "use" seems available. A possible example:
define eth2 ETH2 {
use 1000000 Kbps
}
Your system may have device files for the interfaces,
mine doesn't. Note the positions of the braces, end
of line and alone a line.
Of course you would need separate definitions for each
of your four interface.
After this you can use the name "ETH2" in the disklist
file. It is the last optional parameter. For example:
ajax.example.com AjaxHome /home comp-user-tar 8 ETH2
You do need a spindle number (my "8") to add the
interface. However, be aware that if two DLE have
the same spindle number they will not be amdump'ed
at the same time.
Decide which clients should use which interface and
modify their DLE accordingly.
Hope this works, let us know.
The interface in amanda only help to manage the bandwidth for each
interface by amanda.
But it is the system that choose which interface to use.
The route must be configured at the network level.
Jean-Louis
