We've worked extensively with EMC on this, to the extent of involving
the Architecture Team. They tell us that NetWorker is limited by the
fact that nsrd is single-threaded. They are working on this and the
limit may be removed in a future release, but for now best practice is
to limit the client count in a single data zone to around 1500.
They emphasize that this limit can be exceeded if you have
top-of-the-line hardware and a knowledgeable support staff. But they
really don't like to see more than about 1500 clients on a server.
Conrad Macina
Pfizer, Inc.
-----Original Message-----
From: Albert, Eddie - JACKSONVIL FL
[mailto:eddie.albert AT BANKOFAMERICA DOT COM]
Sent: Thursday, October 07, 2010 6:27 PM
Subject: Re: Client limit for Networker
So many things are factored into what is the true client limit for a
server.
It is not a client count, but more a data capacity number. I used to
have a GREAT backup window calculator, which allowed me to factor how
much data, how much time, NIC cards, fabric, storage speed, etc, etc...
It is like a large puzzle with many edges...
I agree with others have said, I believe the current version of
networker v7.6 sp1 will perform better for you.
When you say your server is well configured and well defined, what does
that mean to you?
OS version & 32bit or 64 bit
HW processors
MEMORY
Motherboard Backplane/Databus speed
Diskspeed
Raid ???
NICs
Describe your network
Do you have a separate data and backup networks?
I have worked for years in organizations where we had 1,500+ clients per
backup server...
What is your parallelism setting at?
Now the more important question.
What is more important getting all 1,800+ clients to fit in backup
window or the speed of your restore?
If you set parallelism up very high, you can backup many more clients up
to saturation limit of your network and drives. But this is at the cost
of your restores...
If you want incredibly fast restore speed, then you set your parallelism
down to single digit and buy many more tape drives.
Ok I am getting down off my technical soap box.
Semper fidelis, /ALE
Eddie Albert ~ Former inmate @ Nimh and Network Ninja white belt only
-----Original Message-----
From: EMC NetWorker discussion [mailto:NETWORKER AT LISTSERV.TEMPLE DOT EDU] On
Behalf Of Punitsingh Suryawanshi
Sent: Thursday, October 07, 2010 9:38 AM
To: NETWORKER AT LISTSERV.TEMPLE DOT EDU
Subject: [Networker] Client limit for Networker
Hello!
I was wondering what is the limit to number of clients that can be
configured and successfully backedup using Networker.
It looks like theoretical limit and practical limit has a gross
difference.
We have a server with roughly 1800 clients and we are very frequently
running into issues like group hung, RPC errors etc.
I am confident that the server is well tuned and configured.
Thanks,
-Punit
--
Regards,
Punitsingh Suryawanshi
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
----------------------------------------------------------------------
This message w/attachments (message) is intended solely for the use of
the intended recipient(s) and may contain information that is
privileged, confidential or proprietary. If you are not an intended
recipient, please notify the sender, and then please delete and destroy
all copies and attachments, and be advised that any review or
dissemination of, or the taking of any action in reliance on, the
information contained in or attached to this message is prohibited.
Unless specifically indicated, this message is not an offer to sell or a
solicitation of any investment products or other financial product or
service, an official confirmation of any transaction, or an official
statement of Sender. Subject to applicable law, Sender may intercept,
monitor, review and retain e-communications (EC) traveling through its
networks/systems and may produce any such EC to regulators, law
enforcement, in litigation and as required by law.
The laws of the country of each sender/recipient may impact the handling
of EC, and EC may be archived, supervised and produced in countries
other than the country in which you are located. This message cannot be
guaranteed to be secure or free of errors or viruses.
References to "Sender" are references to any subsidiary of Bank of
America Corporation. Securities and Insurance Products: * Are Not FDIC
Insured * Are Not Bank Guaranteed * May Lose Value * Are Not a Bank
Deposit * Are Not a Condition to Any Banking Service or Activity * Are
Not Insured by Any Federal Government Agency. Attachments that are part
of this EC may have additional important disclosures and disclaimers,
which you should read. This message is subject to terms available at the
following link:
http://www.bankofamerica.com/emaildisclaimer. By messaging with Sender
you consent to the foregoing.
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
|
