NetBackup Storage Lifecycle Manager keep crashing

[lalajee]

HI,

We have upgraded our master server from v7.7.1 to 8 which was working fine but now after few months NetBackup Storage Lifecycle Manager keep crashing.

We havent made any changes to server which might effect this service to fail.

This service "NetBackup Storage Lifecycle Manager" keep crashing which then stops all of the SLP jobs.

Our Setup.

• Master server: Windows 2008 R2
• Netbackup 8.0

I found this which talks about currpted nblog.conf file (https://vox.veritas.com/t5/NetBackup/NetBackup-Storage-Lifecycle-Manager-does-not-start/td-p/679517)

[Tape_Archived]

Please go through the windows eventvwr and check if you find any relevance or error for the SLP or NetBackup process. Also check the Reports => Problem in java console. 

This is most probably related to OS and NetBackup issue if you have not changed anything in Netbackup

[Marianne]

The issue with nblog.conf was my personal experience:
https://www.veritas.com/connect/forums/slps-stopped-processing

I was trying to check nbstserv log for reasons and found that nothing was logged for a while. Looking at nblog.conf, I saw that there was only a couple of lines. Most content was missing.

Do you have a media server to compare the nblog.conf files?

[Mike_Gavrilov]

I've faced with nblog.conf corruption several time on heavy loaded environment. It was madness! Absolutely irrational and unpredictable behavior. 

[Mike_Gavrilov]

Have you cheked nbstserv log?

[Tousif]

Hello,

SLP crashing, Is there any core dump creating for nbstserv on master server?

Regards

[lalajee]

I have copy the nblog.conf files from media server to master server but still same problem

[Marianne]

@lalajee

There were other suggestions as well...............

Replacing nblog.conf (with NBU down) will only work IF the file was corrupt.

[watsons]

If you have not logged a support call yet.. you should probably do so now.

Whenever you see core file generated in unix env. or APPCRASH event in a Windows env,  that you can tell it's generated by a netbackup command (bp* or nb*), and you can rule out anything like known issues, executable file corruption.  you should contact Netbackup support to have them analyzed. 

Collecting linux core dump files: http://www.veritas.com/docs/000088631

Collecting crash dump in Windows:  http://www.veritas.com/docs/000039951