Unsolved
48 Posts
0
4470
NetWorker start problem after upgrade from 8.2 to 9.2
Hello folks,
I just updated a NetWorker Server on a Windows 2008 Server from 8.2 to 9.2 which went through without any failure message.
Then I started the NetWorker processes. All processes came up and I could connect with the NMC. But I realized that I could not start any backups. The workflow will start but than hangs forever and does nothing. The daemon.log states a few messages:
14:21:09 2 12 13 3392 7164 0 nsrexecd GSS warning Group membership for "SYSTEM@NT-AUTHORITY“ cannot be verified and will not be included in the user's authentication credential. Remote hosts may not see the user as belonging to any operating system group.
29.05.2018 14:21:42 4 2 15 6924 4176 0 nsrck RPC severe Failed to connect to host ' ': Program not registered
29.05.2018 14:21:44 1 9 0 4600 7368 0 nsrjobd JOBS notice Starting full purge of jobs database
29.05.2018 14:21:44 1 9 0 4600 7368 0 nsrjobd JOBS notice Completed full database purge in 0 min 1 sec. Records purged: 0
29.05.2018 14:25:22 4 2 15 6924 4176 0 nsrck RPC severe Failed to connect to host ' ': Program not registered
29.05.2018 14:25:22 0 0 0 7300 4720 0 nsrd NSR info Index Notice: D:\Program Files\Legato\nsr\index\ contains 1819525 records occupying 265 MB
29.05.2018 14:25:22 0 0 0 7300 4720 0 nsrd NSR info Index Notice: checking index for client ' '
29.05.2018 14:26:22 4 2 15 6924 4176 0 nsrck RPC severe Failed to connect to host ' ': Program not registered
29.05.2018 14:27:23 4 2 15 6924 4176 0 nsrck RPC severe Failed to connect to host ' ': Program not registered
29.05.2018 14:27:23 0 0 0 7300 4720 0 nsrd NSR info Index Notice: D:\Program Files\Legato\nsr\index\ contains 118760 records occupying 18 MB
29.05.2018 14:27:23 0 0 0 7300 4720 0 nsrd NSR info Index Notice: checking index for client ' '
29.05.2018 14:28:28 4 2 15 6924 4176 0 nsrck RPC severe Failed to connect to host ' ': Program not registered
Especially the ones I highlighted got my attention.
The NetWorker Server is now doing the index checks of all my clients but always comes back with "Program not registered".
When I try to start a backup from PowerShell or start a mminfo, I always get "Program nor registered".
I checked the DNS which is alright, I checked the local host-file which is also good.
Has anyone an idea what could bring NetWorker all the way up?
Thanks in advance,
beacon.
bingo.1
2.4K Posts
0
May 30th, 2018 01:00
Which processes are running?
It might be that nsrmmdbd is missing. It might have been started but it might also have died already.
If so, all the ones which are supposed to start later will be missing as well due to these dependencies.
Run
tasklist | findstr nsr
to verify that
I personally would proceed as follows:
- stop all NW daemons
- delete/rename the client related GSS database (..\nsr\res\nsrladb)
- start NW again
Then test the connection with the good old method before you run any backup
nsradmin -p nsrexec -s
I hope that you have not changed the hostname as well. If so, most likely the
- ..\nsr\res\servers file needs to be edited AND
- the NW client daemon needs to be restarted
Then, before running any workflow, I would start a manual backup at the client:
save -s -b l
SurajPujari
155 Posts
0
June 5th, 2018 09:00
I was able to witness this error once when NetWorker services were bounced, Try to run nsradmin -p nsrexecd -C -y "nsr peer information" and let it finish.
Hit a Backup with debug and share results.
jayjay982
48 Posts
0
June 5th, 2018 10:00
Thanks everyone,
I involved EMC tech support and they were not able to resolve the issue.
The problem was that all NetWorker services started, except the nsrsnmd. No way to bring it up.
So I did a disaster recovery on the machine and installed NetWorker v9 on a new system with the same name.
But thanks anyway for the help!