We have one that uses three (3).
Two fast ethernet & one GB.
You have to remember that your standard TCP/IP routing is what determines
how these boxes talk !
Client traffic will go in which ever interface you point to and will return
out to the client based on standard routing in the system (but will go back
to the ip in the received packets).
Back when we built our environments "SAN" wasn't really around so we built a
sudo-SAN. Works great !
Our busiest S70 TSM server (just 2 processors & 1 GB memory) seems to max
out at about 60-ish GB/hr of inbound compressed client data (actually kind
of hard to find enough clients to push more than that ;-) but I need to
check recent #'s )
(so during DB backups, that is about 240 GB/hr of client file spaces
being backed up)
Is this good or bad ? ? ?
It is just what we see and it serves our needs !
Dwight
-----Original Message-----
From: Wouter V [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, November 20, 2001 6:49 AM
To: [EMAIL PROTECTED]
Subject: One server, two ip-addresses
Hello,
Does anybody know if a single TSM server can listen on different ip-adresses
(on different nic's) ? Or do you need to run multiple instances on one
machine ?
TSM Server Config example :
Listening for backup data on NIC1 : 192.168.10.10:1500
and on NIC2 : 10.10.10.10:1500
+ other nic for normal lan traffic
Just wondering if adding extra LAN cards in every client to increase the
total bandwith, is a
cheap alternative for SAN environments.
For example : client config with 3 NIC's :
NIC1 : regular client traffic
NIC2 : for online database backup (scheduler
1) (backup lan 1)
NIC3 : for backup of regular file (scheduler
2) (backup lan 2)
2 x 100 Mbit bandwith to backup
Any remarks about this ? I agree, it isn't a good alternative, but I was
just wondering if this is possible ?
Thanks !
Wouter Verschaeve
