cancel
Showing results for 
Search instead for 
Did you mean: 

bpdbjobs ... no results

jcrawford
Level 3
Partner

Hey guys,

It worked earlier but now since i installed 90 windows updates, bpdbjobs no longer works. Even though in the activity monitor, i see all the jobs, bpdbjobs simply goes to the next line. Same behavior with Summary option... bpdbjobs -summary gives you the header and then goes back to the prompt.

Any suggestions?

1 ACCEPTED SOLUTION

Accepted Solutions

mph999
Level 6
Employee Accredited

I had exactly this issue on my test server - but the OS was Solaris.

No idea what caused it, as being a test server, things get changed - what I can say, is that in my case it was OS related - truss on the process just stopped, no error, nothing, just simply didn;t work.  Logs looked perfect up until the point it just stopped - so absolutely nothing to go on.

Reinstall of NBU didn't fix - which proved it was the OS. 

Reinstall of the OS (when I eventually got round to it) fixed the issue.

Looking in the logs alone I think is not going to be too helpful because you are going to have to identify which patch (or patches) broke this and then lean on MS to assist in doing something about it.  Once the patch is identified then it will be easier to find out why it has broken.  I would strongly suggest you install 'Process Monitor' (from Sys internals) to look at what the process is doing.

Without knowing the patch, it is like saying we know something at the OS level has changed, but we're not going to tell you what, which is the missing piece of the jigsaw - without this piece, it is unreasonable to try and fix it from the Symantec side alone.

Martin

 

 

 

View solution in original post

13 REPLIES 13

Will_Restore
Level 6

try with the  -M <masterserver name>  option

 

jcrawford
Level 3
Partner

I did try that.

bpdbjobs -report -M server -> nothing

bpdbjobs -summary -all_columns -> nothing

its like bpdbjobs is not even seeing the data. I tried bpdbjobs -delete jobid -> that job still exists in the activity monitor without any results in the command prompt.

mph999
Level 6
Employee Accredited

Looks like one of the MS patches broke it - it that change was made directly before it stopped working.

Think your going to have to remove them and then put them back a few at a time to find out which one, then contact Microsoft to start finding out why.

You will probably need to log a call with Symantec as well, but MS should 'lead' the investigation, it is their software that caused the issue, not ours.

Martin

mph999
Level 6
Employee Accredited

Other option is search the Symantec DB see if any of the patches you installed show up as previously known to cause an issue.

M

TomerG
Level 6
Partner Employee Accredited Certified

Have you rebooted? Restarted any NetBackup services?

jcrawford
Level 3
Partner

I have restarted the server a few times and nothing has changed.

Note that i am new to this so any help in how to find the log and where to look for would be very helpful. I rather go the route of troubleshooting instead of removing all the patches (about 100+). (yes, i should not have installed all of them at the same time).

I konw that when i was installing the updates, Security Update for VC++ had issues. Would that cause any problems?

TomerG
Level 6
Partner Employee Accredited Certified

You could enable logging for bpdbjobs (create the directory with this name under the NetBackup\logs directory, or use the mklogdir.bat file there to create all logs, which might be more than you want). You have to restart NBU for this to take effect though and then start running those commands, then look at that log. Note, I wouldn't be able to decipher most of this, maybe someone else on this forum would take a crack at that... I'd log a call in your case with support.

You also haven't mentioned versions of NBU and such. Current version is 7.5.0.4

mph999
Level 6
Employee Accredited

I had exactly this issue on my test server - but the OS was Solaris.

No idea what caused it, as being a test server, things get changed - what I can say, is that in my case it was OS related - truss on the process just stopped, no error, nothing, just simply didn;t work.  Logs looked perfect up until the point it just stopped - so absolutely nothing to go on.

Reinstall of NBU didn't fix - which proved it was the OS. 

Reinstall of the OS (when I eventually got round to it) fixed the issue.

Looking in the logs alone I think is not going to be too helpful because you are going to have to identify which patch (or patches) broke this and then lean on MS to assist in doing something about it.  Once the patch is identified then it will be easier to find out why it has broken.  I would strongly suggest you install 'Process Monitor' (from Sys internals) to look at what the process is doing.

Without knowing the patch, it is like saying we know something at the OS level has changed, but we're not going to tell you what, which is the missing piece of the jigsaw - without this piece, it is unreasonable to try and fix it from the Symantec side alone.

Martin

 

 

 

jcrawford
Level 3
Partner

Thank you all for your feedback. I'll continue to remove the pieces that got installed and once i have the system back up and running (NBU 7.5), i'll post it here just in case.

 

Thank you,

jcrawford
Level 3
Partner

After removing about 10-11 updates, restarting the environment along with removing and re-adding the NIC (Virtual), things are working again. Thanks for all the help.

I'll update once again when i have the specific update causing the issue.

jcrawford
Level 3
Partner

I'm closing this thread.

I uninstalled the above mentioned updates and also C++ redis updates and restarted the computer. Installed all the updates again one at a time to see which one breaks NBU again but even after installing all the updates, bpdbjobs still now works. I am not sure what happened.. but thanks for your input.

mph999
Level 6
Employee Accredited
ightly Hmm, how odd. So you appear to have taken off the patches and put them back on, so you are back where you started, but something clearly is slightly different. Could be anything, perhaps the reboot after you took the patches off, perhaps they went back on in a slightly different order. No matter, you have it working now, so panic over. Many thanks for the solution. Martin

mph999
Level 6
Employee Accredited
ightly Hmm, how odd. So you appear to have taken off the patches and put them back on, so you are back where you started, but something clearly is slightly different. Could be anything, perhaps the reboot after you took the patches off, perhaps they went back on in a slightly different order. No matter, you have it working now, so panic over. Many thanks for the solution. Martin