Hi,

thanks for all the answers.

To give a more general overview:

We are running a GFS (StorNEXT) as "normal" file system.
One server is working also as TSM client. 8 file systems
are defined, each is able to deliver ~60-100MB/s in avereage.
The file space is ~60TB with 22Million files.

2 dedicated NIC's (intel e1000) are used in a dedicated vlan
and configured using bionding without any further settings.

This link is connected to our TSM Server (AIX 8 core) which is
also connected to this vlan using a dedicated network interface.
In the moment we do not have many traffic on the file system, therefore
I can not measure many things.

What I currently trying after reading all the posts is to
configure the client to use not only one task (and streams), but
to use 2-4 streams. When everything is working corrently, it *might*
split 2 streams on each NIC ....

However tuning this parameter on the client nearly dropped the
backup time by a factor of 2 !

But I need more transfer, to see, if the usage of the Nic's is improved.

Maybe we have to try LANfree backup ...

Bye, Peer

Rick Jones schrieb:
> Linux bonding does offer the prospect of doing round-robin scheduling
> of packets across the links in the bond, but that comes at a price -
> packet reordering. Get "too much" of that and you start to get
> spurrious retransmissions and clamping of the congestion window.
>
> Also, the packet scheduling algorithms in the bonding code are for
> transmit only. A backup server is ostensibly a recv-mostly sort of
> thing. The scheduling of packets for inbound to the backup server
> would be determined by the algorithms in the switch to which it was
> connected.
>
> You might also sniff the wire to see what sort of window sizes are
> being used. Also, check the CPU util of _each_ CPU on the server.
> I'm assuming your filesystem/whatnot can take-in data >> 60 MB/s? Does
> the side sending the data to the server report any TCP
> retransmissions?
>
> rick jones