I see no answer on this so here is one
The key point is TCPServeraddress option and the IP routing table on the
node. Based on server address and routing info the IP stack will make the
decision through which interface to send the data. Example
TSM Server
100 Mb - 172.16.1.1
1 Gb - 192.168.1.1
Node
100 Mb - 172.16.1.5
1 Gb - 192.168.1.5
So if you specify TCPServeraddress 172.16.1.1 IP stack will send the data
over 100 Mb interface. You have to use 192.168.1.1.
TCP Clientaddress is just where the server should contact the client in
SCHEDMODe PRompted. To send schedule info over 1 Gb dedicated LAN just to
send the backups over 100 Mb production LAN is of no value.

Zlatko Krastev
IT Consultant






Steve Schaub <Steve.Schaub AT HAWORTH DOT COM>
Sent by: "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
22.08.2002 19:20
Please respond to "ADSM: Dist Stor Manager"


        To:     ADSM-L AT VM.MARIST DOT EDU
        cc:
        Subject:        Win2k client - specifying a specific ethernet adapter


Our environment:
TSM 4.2 on AIX 5.1
1 100mb ethernet to Cisco 6509 connected to our production network
2 gigE to Cisco 6509 on a dedicated backup vlan

We have always backed up our Intel servers over the production network,
using the gig ports for some of our Oracle data on HP-UX.  Now the serv
team is willing to put in a 2nd nic on new Win2k server builds, for TSM
backups.  In the HP-UX environment, we control this using multiple stanzas
in the dsm.sys file, and the dba's specify the one they want in their
scripts.  In the Win2k environment, where we want all TSM backup/restore
going through the 2nd nic, is it just a matter of specifying the
tcpclientaddress=xxx.xx.xx.xx in the dsm.opt, or is there more to it?
Also, is there anything special I need to do so any backups/restores done
through the client web gui use the 2nd nic as well?

Steve Schaub
Systems Engineer
Haworth, Inc
Steve.Schaub AT Haworth DOT com
616-393-1457 Desk
616-836-6962 Cell
Siempre Hay Esperanza