Real world, we count on 8M/sec throughput for backups over 100Mb. And yes, if
you set both up, you can get approximately 16M/sec throughput during concurrent
backups.
Couple things to make sure of:
1. client config for master server must contain both FQDN and shortname for
both NICs so it can be used for backup purposes by clients
2. set your storage node (minimum) -OR- your storage node and server network
interface to the new NIC name on the clients you want running over the new NIC
- depends on if you want meta-data all over one pipe or matched to data
path
3. As discussed before, make sure either DNS or all impacted /etc/hosts
contain the new NIC values. Best bet if you have to use hosts files......push
the new hosts file to ALL clients. That way, you can move a client from NIC1
to NIC2 for backups just by modifying their client config (see #2) and w/o
needing to update the local values of the client server.
Hope this helps.
--Ted
NOTE: all the above info is based on my previous experience w/ qfe (4port)
NICs and my current 4x GigE Unix Legato environment. YMMV on a Wintel master,
but the principles are the same.
-----Original Message-----
From: Legato NetWorker discussion [mailto:NETWORKER AT LISTSERV.TEMPLE DOT EDU]
On Behalf Of Skinner,Alan C(Contractor)
Sent: Friday, August 26, 2005 12:34 PM
To: NETWORKER AT LISTSERV.TEMPLE DOT EDU
Subject: Re: [Networker] Second IP on Server
Do the math, 100 megabits/second nic turns out to be 12.5 megabytes/second of
data going to tape. That's purely a max max speed which you never see in the
real world. So I thought if I could double up on nic's I could double up on
data to tape.
Alan Skinner
Network Administrator
Research, Analysis & Maintenance, Inc.
609-562-6039
<alan.skinner AT dix.army DOT mil>
-----Original Message-----
From: lemons_terry AT emc DOT com [mailto:lemons_terry AT emc DOT com]
Sent: Friday, August 26, 2005 1:18 PM
To: NETWORKER AT LISTSERV.TEMPLE DOT EDU; Skinner,Alan C(Contractor)
Subject: RE: [Networker] Second IP on Server
Before doing this, you should make sure that your single Ethernet adapter is,
indeed, the bottleneck. For instance, if your backup and/or storage node
server CPU is running 90-100% busy (perhaps handling the IP traffic containing
your backup data coming in from clients via the LAN), or if your backup client
is busy, slow, or has many small files, then adding a second Ethernet adapter
won't help.
Where is your bottleneck now? That will help us advise you.
If you're not sure, check out the NetWorker Performance Tuning book, available
(as are all NetWorker manuals) on the Legato web site.
Hope this helps.
tl
Terry Lemons
CLARiiON Appliance Engineering
CLARiiON Application Solutions Integration
EMC²
where information lives
4400 Computer Drive, MS D239
Westboro MA 01580
Phone: 508 898 7312
Email: Lemons_Terry AT emc DOT com
-----Original Message-----
From: Legato NetWorker discussion [mailto:NETWORKER AT LISTSERV.TEMPLE DOT EDU]
On Behalf Of Alan Skinner
Sent: Friday, August 26, 2005 12:42 PM
To: NETWORKER AT LISTSERV.TEMPLE DOT EDU
Subject: [Networker] Second IP on Server
I am on a 100mb network. Trying to make my back ups faster. My hp server
has a single network interface card with two ports. I have a library with 2
sdlt 320's rated at 16MB per second per driver. I am averaging 6 or 7 MB
per second per drive. What I thought I could do is assign a second ip to
the other nic. Then go around and change half my host files so that half
my servers would backup on the other ip, basically increase my input to the
backup server. I did the experiment but networker is giving me a connection
refused. The client recognises the fully qualified domain name and the
second ip. I am a windows environment. Is there any configuration on the
networker server that needs to done.
To sign off this list, send email to listserv AT listserv.temple DOT edu and
type "signoff networker" in the body of the email. Please write to
networker-request AT listserv.temple DOT edu if you have any problems wit this
list. You can access the archives at
http://listserv.temple.edu/archives/networker.html or via RSS at
http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER
To sign off this list, send email to listserv AT listserv.temple DOT edu and
type "signoff networker" in the body of the email. Please write to
networker-request AT listserv.temple DOT edu if you have any problems wit this
list. You can access the archives at
http://listserv.temple.edu/archives/networker.html or via RSS at
http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER
To sign off this list, send email to listserv AT listserv.temple DOT edu and
type "signoff networker" in the
body of the email. Please write to networker-request AT listserv.temple DOT edu
if you have any problems
wit this list. You can access the archives at
http://listserv.temple.edu/archives/networker.html or
via RSS at http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER
|
