Networker

Re: [Networker] Client limit for Networker

2010-10-07 15:06:48
Subject: Re: [Networker] Client limit for Networker
From: Punitsingh Suryawanshi <punit.suryawanshi AT GMAIL DOT COM>
To: NETWORKER AT LISTSERV.TEMPLE DOT EDU
Date: Fri, 8 Oct 2010 00:35:31 +0530
The upgrade was somewhere near March this year (I guess), support is not a
problem, we have extended support contract in place for old versions (EOS &
EOL)

Thanks,
-Punit

On Fri, Oct 8, 2010 at 12:12 AM, STANLEY R. HORWITZ <stan AT temple DOT edu> 
wrote:

> 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
>



-- 
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