We added a storage node because the bottleneck was the NW server but not
just network-wise. We saw one CPU going to 100% usage even if overall
the CPUs are not busy. Adding a storage node helped with that. Also,
it helped us to segregate some large clients onto drives that are not
multi-threaded quite so much - without creating additional pools.
-T
Teresa Biehler
Information and Technology Services
Rochester Institute of Technology
teresa.biehler AT rit DOT edu
CONFIDENTIALITY NOTE: The information transmitted, including
attachments, is intended only for the person(s) or entity to which it is
addressed and may contain confidential and/or privileged material. Any
review, retransmission, dissemination or other use of, or taking of any
action in reliance upon this information by persons or entities other
than the intended recipient is prohibited. If you received this in
error, please contact the sender and destroy any copies of this
information.
-----Original Message-----
From: EMC NetWorker discussion [mailto:NETWORKER AT LISTSERV.TEMPLE DOT EDU] On
Behalf Of Anacreo
Sent: Thursday, September 03, 2009 7:28 PM
To: NETWORKER AT LISTSERV.TEMPLE DOT EDU
Subject: Re: [Networker] Upgrade Time... (7.4.4 to 7.5.1)
I'm trying to figure out why people have so many storage nodes... 10,
really?
I've got a fairly beefy backup environment, about 36TB on the weekends
and a
lot of boxes 100+. And I'm doing this all on a single Sun T5240...
doesn't
even seem to be cracking a sweat.
Seems to me... any modern machine can handle:
Atleast 6 1GB NIC's if not 2-4 10gb NIC's... so that's 7-40gb/s
inbound...
Atleast 2-4 dual ported 4gb HBA's... So that's 16gb/s outbound...
And a modern 4x4 Intel server or a 100+ coolthread Sun server can
easily
move that much bandwidth...
So why so many boxes?
Are all the storage nodes regional -- if so, I completely understand.
Are all these storage nodes for doing snapshot backups (which I've
learned
to despise and not value at all)?
Is it because you're using a Windows infrastructure?
Or Legacy?
Am I missing a boat somewhere?
Chester, can you explain why you have 10 storage nodes to solve my
curiosity?
Alec
On Thu, Sep 3, 2009 at 2:12 PM, Tim Mooney <Tim.Mooney AT ndsu DOT edu> wrote:
> In regard to: [Networker] Upgrade Time... (7.4.4 to 7.5.1), Chester
> Martin...:
>
> I have two questions:
>>
>> 1) Do the networker server and all the storage nodes need to run
>> the same version? I have over 10 storage nodes and didn't know
whether
>> or not I needed to upgrade all of them at the same time.
>>
>
> Yes.
>
> 2) Is there anything important I'm leaving out?
>>
>
> Most upgrade documents recommend you check client indexes and the
media
> database before doing an upgrade
>
> nsrck -L6
> nsrim -vX
>
> Tim
> --
> Tim Mooney
Tim.Mooney AT ndsu DOT edu
> Enterprise Computing & Infrastructure 701-231-1076
(Voice)
> Room 242-J6, IACC Building 701-231-8541
(Fax)
> North Dakota State University, Fargo, ND 58105-5164
>
>
> 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 with
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 with 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 with 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
|
