Hi Tim,
I did try that previously, but it didn't make any difference.
I have since done the following
1) Deleted all client peer info on the backup server
2) Deleted the certificate on the backup server under NSRLA as it still
contained the name of the server before it was renamed (Server was renamed
about 2 months ago after we moved it off a microsoft cluster to a standalone
server - used mmrecov to do this)
3) Deleted all the shared drives of the physical tape library as all 8 physical
drives were added by our client to every single storage node. There are just
over 30 Storage nodes in the environment which were all trying to access all 8
drives. I assume this would cause NetWorker problems as that is a heck of a lot
of paths to manage ( about 240 to be exact)
4) Upgraded to NetWorker 7.5.3
Since the above steps have been completed the response times of NetWorker has
changed dramatically and neither nsradmin or NMC are timing out any longer.
We still are having an issue accessing "Configuration" -> "Clients" and
"Media" -> "Indexes" in the NMC. The error we receive is: Can't find client
name attribute!
I can still access the client resources via nsradmin and I can view the clients
indexes and save sets via nsrinfo and mminfo with no problems. As any body
encountered this error before?
Freddy
> From: Tim.Cassidy AT kimball DOT com
> To: fenslin AT HOTMAIL DOT COM
> Date: Fri, 30 Jul 2010 09:55:11 -0400
> Subject: RE: [Networker] NMC and nsradmin keep timing out
>
> Not sure on the main issue but on the issue with the long restart you might
> try renaming the /res/jobsdb.
> I do this every time I stop NetWorker along with deleting the /nsr/tmp
> directory. I ran across this issue
> with long start-ups a while back and had a sev 1 case with EMC for a very
> long time. EMC was no help.
> I knew the problem was with the jobsdb so I just re-named it. If you are not
> using it for reporting it should be
> No big deal. This will also help your bootstrap runtimes.
>
> Hope this helps.
>
> -----Original Message-----
> From: EMC NetWorker discussion [mailto:NETWORKER AT LISTSERV.TEMPLE DOT EDU]
> On Behalf Of Freddy Enslin
> Sent: Friday, July 30, 2010 9:41 AM
> To: NETWORKER AT LISTSERV.TEMPLE DOT EDU
> Subject: [Networker] NMC and nsradmin keep timing out
>
> Hi All,
>
>
> I have a client running NetWorker 7.5.2 on Windows server 2008 x64. NMC
> and nsradmin keep timing out
>
> As we have added clients and resources to NetWorker the timeouts are
> getting progressively worse to the point that we cannot add a single
> resource or update a single attribute in a resource without the console
> losing connection to the backup server with the error: Time Out. I tried
> making changes using nsradmin instead but that times out too. The only
> way I can add clients, groups or change attributes is by stopping
> NetWorker Services and using nsradmin -d nsrdb, but this is not going to
> work for the client as they are not that experienced with NetWorker The
> client has a large environment using two EDL 4206 libraries with 280 LTO
> 3 drives configured and and HP ESL with 8 LTO 2 drives all the LTO 2
> drives are configured for Dynamic drive sharing with all the storage
> nodes and DSN's. There are approximately 10 Storage Nodes and
> approximately 21 DSN's mostely Microsoft clusters with multiple virtual
> instances on each cluster. We have configured their storage node
> attributes to curphyhost and their Recover storage Nodes to currechost.
> I mention all this in case it may be causing the problem. There are
> currently just under 500 clients in NetWorker but some are in more than
> one group and 300 of them are VM's backed up via 5 VCB Proxy's. 3/4 of
> the environment consist of MSSQL backups using the NetWorker Module
> (version 5.2.1)
>
> I have restarted the services multiple times and rebooted the server
> multiple times, but this has not helped at all. In fact it is getting
> worse. Now when we try look at clients under configuration the error we
> get is:
>
> Can't find client name attribute!.
>
> I can list the client name attributes in nsradmin though!
>
> Also whenever we restart the nsrd service it takes about 30 mins. to
> start. Please help!
>
>
> Regards,
> Freddy
>
> 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
|
