I use a multi-NIC master AND multi-NIC storage nodes. The top 3 things I can
think of to assist in performance.
1. Add all master and storage node DNS values to all master and storage node
/etc/hosts files.
2. Setup and use "nscd" (Name Server Caching Daemon) on all master/storage
nodes to decrease DNS hits
3. On every client, set the "Server Network Interface" for Master/MetaData
connections. Also on every client, set the "Storage Nodes" field by removing
'nsrserverhost' and putting in StorageNode identifier.
NOTE: All my servers have an Enterprise (routed) network connection
and a Backup (flat, non-routed) network connection(s). The Enterprise is used
to telnet/GUI use/general interactions. The Backup network is used for
MetaData and backup data transfers.
Example:
Master has 3 NICs
Master-A == Enterprise connection
Master-B == Backup Specific
Master-C == Backup Specific
Storage Node One (SN1) has 2 NICs
SN1-N == Enterprise connection
SN1-M == Backup Specific
Storage Node Two (SN2) has 4 NICs
SN2-W == Enterprise connection
SN2-X == Backup Specific
SN2-Y == Backup Specific
SN2-Z == Backup Specific
All 3 servers would contain an /etc/hosts file that contains (at minimum):
x.x.x.x Master-A loghost
x.x.x.y Master-B
x.x.x.z Master-C
y.y.y.y SN1-N
y.y.y.z SN1-M
z.z.z.w SN2-W
z.z.z.x SN2-X
z.z.z.y SN2-Y
z.z.z.z SN2-Z
And when setting up client ABC to backup to SN2 -
In the ABC client config you would enter 'Master-B' as the "Server
Network Interface" and you can enter all 3 SN2 values in the "Storage Nodes".
Storage Nodes:
SN2-X
SN2-Y
SN2-Z
- Or you could only add one and manually "balance" the load, like we
have done.
- Or you can put "nsrserverhost" as the LAST entry, backup to master if
the Storage Node ever goes down.
And if setting up client DEF to backup to SN1 -
Server Network Interface = Master-C
Storage Nodes = SN1-M
Probably much more rambling than I meant it to be. Hope this helps in some way.
--Ted
-----Original Message-----
From: Legato NetWorker discussion
[mailto:NETWORKER AT LISTMAIL.TEMPLE DOT EDU]On Behalf Of Howard Martin
Sent: Friday, January 07, 2005 11:23 AM
To: NETWORKER AT LISTMAIL.TEMPLE DOT EDU
Subject: Re: [Networker] Multiple NIC configuration
Tarik,
I believe that the "server network interface" only controls the Meta data
and that the back up data is controlled by "storage nodes".
With the NMO module (networker 6.1.3/4) the changes in scripts and util
files did not work - this was with a backup server that had 2 NIC's with
no route between them (not allowed to do routing on the servers).
On Fri, 7 Jan 2005 17:28:29 +0100, Tarik El Mansouri <etarik AT YAHOO DOT COM>
wrote:
>Hello,
>Two points:
>1. 6 gigabit ethernet cards on a V880 server
> contactyour Sun Account Manager for support of 6 GBE NICs on a V880.
> There are retrictions on number of HBAs supported per server type.
> Don't know it by heart... but there are some limitations.
>
>
>2. Use nsrserverhost as storage node,
> - Add all the server hostnames as aliases of the backup servers.
> - Redirect your LAN based baced up data for file system backups
using "server network interface" parameter.
> - Additionnally, for modules based backups such as NMO, NMSAP, ...,
update you RMAN script or you're SAP utl file to change the server name.
>
>Regards,
>Tarik EL MANSOURI
>
>Howard Martin <howard.martin AT EDS DOT COM> wrote:
>This should work if the "storage nodes" field is set to the same value - I
>believe that if left as nsrserverhost then the actual backed up data will
>go through the "primary" backup server NIC. We had a problem with the
>networker oracle module that we couldn't get to talk to the secondary
>interface but would send the backup data via the storage node field entry.
>There should be no problems with 2 routers choosing the right path IF you
>are using tapelib1=x.x.200.x and tapelib4=x.x.200.x where all the x's are
>not the same.
>
>On Fri, 7 Jan 2005 09:00:41 -0500, Joel Fisher wrote:
>
>>Hey Guys,
>>
>>
>>
>>I'm getting ready to upgrade my server and along with this upgrade I had
>>planned on implementing sun trunking and just having one big(4Gb) pipe
>>on the same IP that I use now. Well, after having a long discussion
>>with the networking guys here, because our core links are only 1Gb I
>>would be better of having the separate NICs on separate switches and
>>separate subnets.
>>
>>
>>
>>Our data center is setup like below.
>>
>>
>>
>>2 Cisco 6509 connected to 2 Cisco routers(not sure what model) via 1Gb
>>pipes.
>>
>>Our servers mostly use 3 subnets x.x.158.x, x.x.200.x and x.x.201.x.
>>
>>So in a perfect world I would get the best network performance if I had
>>6 NICs 1 on each subnet on each switch. That would keep the amount of
>>traffic that has to cross the shared 1Gb pipe way down.
>>
>>I have a V880 8x1.2Mhz 16GB Memory, so I have the physical ability to do
>>this.
>>
>>
>>
>>My question is: Is networker able to take advantage of a configuration
>>like this? I would set it up like below.
>>
>>
>>
>>In switch1: tapelib=x.x.158.x(main server NIC),
>>tapelib1=x.x.200.x,tapelib2=x.x.201.x
>>
>>In switch2: tapelib3=x.x.158.x, tapelib4=x.x.200.x,tapelib5=x.x.201.x
>>
>>
>>
>>On a client plugged into switch1 on the 200 vlan I would put "tapelib1"
>>in the "Server network interface" field.
>>
>>On a client plugged into switch2 on the 200 vlan I would put "tapelib4"
>>in the "Server network interface" field.
>>
>>
>>
>>>From what I've found in the archive, at least the initial connect will
>>also use the 158 NIC in switch1(no problem). My concern is that it'll
>>try to use both of the 200 NICs instead of the one I designate. Does
>>anyone have a similar setup that is functioning correctly? This would
>>complicate my backup configuration a bit, but I think the potential
>>performance gains are quite high.
>>
>>
>>
>>Thanks,
>>
>>
>>
>>Joel Fisher
>>
>>
>>
>>
>>--
>>Note: To sign off this list, send a "signoff networker" command via email
>>to listserv AT listmail.temple DOT edu or visit the list's Web site at
>>http://listmail.temple.edu/archives/networker.html where you can
>>also view and post messages to the list. Questions regarding this list
>>should be sent to stan AT temple DOT edu
>>=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=
>
>--
>Note: To sign off this list, send a "signoff networker" command via email
>to listserv AT listmail.temple DOT edu or visit the list's Web site at
>http://listmail.temple.edu/archives/networker.html where you can
>also view and post messages to the list. Questions regarding this list
>should be sent to stan AT temple DOT edu
>=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=
>
>
>---------------------------------
> Découvrez le nouveau Yahoo! Mail : 250 Mo d'espace de stockage pour vos
mails !
>Créez votre Yahoo! Mail
>
>--
>Note: To sign off this list, send a "signoff networker" command via email
>to listserv AT listmail.temple DOT edu or visit the list's Web site at
>http://listmail.temple.edu/archives/networker.html where you can
>also view and post messages to the list. Questions regarding this list
>should be sent to stan AT temple DOT edu
>=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=
--
Note: To sign off this list, send a "signoff networker" command via email
to listserv AT listmail.temple DOT edu or visit the list's Web site at
http://listmail.temple.edu/archives/networker.html where you can
also view and post messages to the list. Questions regarding this list
should be sent to stan AT temple DOT edu
=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=
--
Note: To sign off this list, send a "signoff networker" command via email
to listserv AT listmail.temple DOT edu or visit the list's Web site at
http://listmail.temple.edu/archives/networker.html where you can
also view and post messages to the list. Questions regarding this list
should be sent to stan AT temple DOT edu
=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=
|
