Hello,
Could this be a Jobs dB issues and addtionally you really need to look at 
networker architecture and look at splitting up to multiple masters or 
increasing storage node capabilities, you might also consider investigating
Group size\scheduling and device avalibility.
Network Latencies, client load and incorporating VTL\Disk based backup.
Upgrading if indicated the networker inviroment and  consider best practices 
for your workload.
Thanks
Fazil Saiyed
 
> Date: Thu, 7 Oct 2010 14:42:29 -0400
> From: stan AT TEMPLE DOT EDU
> Subject: Re: [Networker] Client limit for Networker
> To: NETWORKER AT LISTSERV.TEMPLE DOT EDU
> 
> When did you upgrade to 7.4.2? That version is quite old and I don't believe 
> EMC even supports it now.
> 
> On 10 7, 2010, at 1:32 PM, Suhas M wrote:
> 
> > Hello!
> > 
> > Server has 3 storage nodes and was working fine until it was upgraded
> > to 7.4.2. The same payload worked fine with 7.2.1 previously
> > 
> > Regards,
> > Suhas
> > 
> > On Thu, Oct 7, 2010 at 7:44 PM, STANLEY R. HORWITZ <stan AT temple DOT edu> 
> > wrote:
> >> You are backing up 1800 clients with one server and no storage nodes? 
> >> There are numerous limiting factors, but you need to look at save streams 
> >> rather, not just clients. If you log onto PowerLink, there is a NetWorker 
> >> performance and tuning guide which you can download and read. I encourage 
> >> you to read that document. 1800 clients on one server without any storage 
> >> nodes is ripe for tuning improvement by splitting the clients up into 
> >> multiple storage nodes.
> >> 
> >> 
> >> On 10 7, 2010, at 9:38 AM, Punitsingh Suryawanshi wrote:
> >> 
> >>> 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
> >> 
> >> 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