As the NW server will start, i do not expect an issue with the media index. Consequently your problem must be due to a defective resource as this is just the other major component of the bootstrap.
So let me recommend that you rerun the test but do not reactivate the resources from the res.R directory. If this works, there is an obvious issue the the resources. Worst case, you must recreate the jukebox but this should not be a big deal.
Like everything in NetWorker, name resolution can cause quite a few problems - including at startup.
We see it fairly regularly when we attempt to start up a foreign nsrdb in our lab, or hear it from customers doing DR tests.
If the server can't resolve the client names in your nsrdb (and it will attempt to do for all at startup), then it can hold up startup a very long time. If you want to determine if this is the case, simply shutdown, make a copy of nsrdb, and delete all instances of clients in the DR nsrdb. If you find startup is fairly instant - then it's likely the server attempting to resolve names. This can also be exposed in the daemon.raw by driving nsrd to debug level 1 using dbgcommand.
You can circumvent this issue by creating a dummy hosts file containing all the client names (which would probably take a bit of scripting). There is a hotfix being created for 7.6.5.x at the moment which should prevent the start-time lookups as well, if you wished to try it.
By recovering the bootstrap the media db will be overwritten but you need to 'move' the resources ti the default directory. This is what you should avoid to find out which data is responsible for the problem.
Okay. I see what you are saying. I completed the mmrecov and restarted the server. When I logged back into NMC the library was still working. I renamed the res.r folder and from there on, I stopped being able to open the library from NMC. Also, I ran nsr_render_log on daemon.raw and there’s a lot of errors “nsrexecd GSS Warning session for System/server AUTHORITY has expired and is no longer valid”.
Library configuration is stored in res folder, if you rename folder, than you will lost the configuration of course. If you rename res folder, you have to recreate library again manually either from NMC or cli…
nmc2
268 Posts
0
June 27th, 2013 07:00
There might be some issue with the recovered mm and res. Can you try to restore from some other bootstrap backup and see if this happens again.
Regards,
Prajith
Rathesungoddess
10 Posts
0
June 27th, 2013 11:00
I'm creating a new bootstrap now... I'll test as soon as its finished.
bingo.1
2.4K Posts
0
June 27th, 2013 11:00
As the NW server will start, i do not expect an issue with the media index. Consequently your problem must be due to a defective resource as this is just the other major component of the bootstrap.
So let me recommend that you rerun the test but do not reactivate the resources from the res.R directory. If this works, there is an obvious issue the the resources. Worst case, you must recreate the jukebox but this should not be a big deal.
Rathesungoddess
10 Posts
0
June 27th, 2013 11:00
I'm not sure what you meann about not reactivating the res.r resources... do you mean just not rename the folder?
jkernagh
35 Posts
0
June 27th, 2013 12:00
Like everything in NetWorker, name resolution can cause quite a few problems - including at startup.
We see it fairly regularly when we attempt to start up a foreign nsrdb in our lab, or hear it from customers doing DR tests.
If the server can't resolve the client names in your nsrdb (and it will attempt to do for all at startup), then it can hold up startup a very long time. If you want to determine if this is the case, simply shutdown, make a copy of nsrdb, and delete all instances of clients in the DR nsrdb. If you find startup is fairly instant - then it's likely the server attempting to resolve names. This can also be exposed in the daemon.raw by driving nsrd to debug level 1 using dbgcommand.
You can circumvent this issue by creating a dummy hosts file containing all the client names (which would probably take a bit of scripting). There is a hotfix being created for 7.6.5.x at the moment which should prevent the start-time lookups as well, if you wished to try it.
bingo.1
2.4K Posts
0
June 27th, 2013 14:00
By recovering the bootstrap the media db will be overwritten but you need to 'move' the resources ti the default directory. This is what you should avoid to find out which data is responsible for the problem.
Rathesungoddess
10 Posts
0
June 28th, 2013 15:00
Okay. I see what you are saying. I completed the mmrecov and restarted the server. When I logged back into NMC the library was still working. I renamed the res.r folder and from there on, I stopped being able to open the library from NMC. Also, I ran nsr_render_log on daemon.raw and there’s a lot of errors “nsrexecd GSS Warning session for System/server AUTHORITY has expired and is no longer valid”.
Lucky85
173 Posts
0
June 30th, 2013 23:00
Library configuration is stored in res folder, if you rename folder, than you will lost the configuration of course. If you rename res folder, you have to recreate library again manually either from NMC or cli…
Lukas