Unable to start bprd service, stops after 5 seconds

Thinking about it, it is possible that ccleaner has removed some of your catalog meta data, and without a log file you'll never know.  When was ccleaner run?  Did you have a successful catalog backup before ccleaner was run?

Got a DR plan?

If you're on v6.x and above - then do you have your DR file for your last successful catalog backups stored safely off-host, or were these deleted too?

The catalogs backup to disk and to tape. I don't have a log of what the ccleaner removed since another person ran it and it doesn't save a log.  Where is the catalog meta data stored so I can check if something might be missing?

While the issue was already occuring, I upgraded to 5.1 MP7 from 5.1 MP2.  Same issue resulted but it appears that the upgrade to 5.1 MP7 was successful.

Thank you.

Performed some more testing after importing the server into a VMware Virtual Machine for testing...  If I perform a repair or modify, the service will still not run for longer then a few seconds. 

If I completely uninstall and reinstall Netbackup the service works fine, but of courses, I loose all my settings.

Any futher ideas?  No sugguestion will be turned down, I can just revert to a VM snapshot if it makes it worse. I'm getting deseprate here! lol

Also can't seem to ruin a bpverify or the verify_images under the goodies directory, returns:

verify not allowed: network read failed (42)

Wonder if it's not working because the I can't start the that NetBackup Request Manager or if it's something else.

truwarrior22 wrote:

 Also right before the issue occured I noticed that one of the tape drives where down so I rebooted the server.  Ever since the reboot and the ccleaner, I'm unable to start the bprd service and the console won't open because of it.  I tried uninstalling McAfee 8.0i antivirus and the issue is still occuring.

A tape drive being down won't stop "bprd" which is the Request Manager Daemon.

We now that bprd won't stay up, but there's no indication yet of why.  It could be seriously fundamental or just a simple fix required.  I'd call Symentec Support if you don't want to un-install and re-install and then perform a catalog recovery (which BTW will recover the entire catalog, EMM dtabase, policies, and device configuration) - and see if they can help you find out what is missing or corrupted.

Have you tried looking in latest log file in:

   \NetBackup\logs\bprd\*.log

...to see if bprd is even logging why it is failing. 

If you do decide to un-install and re-install, then you will need to re-install the master server software to the patch level/version that ran the catalog backup.  So, if your catalog backup media was written with v5.1 MP2, then don't go patching to MP7.

Before installing, you need to aware that you will loose any site specific modifications, so... things to save beforehand:

1) Save a copy of your vm.conf from volmgr.

2) Try saving your master server "bp.conf" settings from the Windows registry with:

    bpgetconfig -M $master > old.lis               (but if this requires bprd, you won't be able to).

3) Save a copy of any "notify" scripts that you may have customized in:

    \NetBackup\bin

4) Look for any SIZE_DATA_BUFFERS*, NET_BUFFER_SZ*, NUMBER_DATA_BUFFERS* files - I use a "*" here to indicate that you may also find the "restore" counterparts to these tuning files.

5) Save these files:

     \Java\Debug.Properties

     \Java\auth.conf

     \NetBackup\db\altnames\*.*      (i.e. all files in this folder)

6) Also, any other fully CAPITILIZED files without a file name extension in:

     \NetBackup

     \NetBackup\db

     \NetBackup\db\config

     \NetBackup\bin

     \Volmgr

     \Volmgr\config

...as these may be other touch files that your require.

7) Try to save your cold catalog information (if you need to):

    bpsyncinfo -L > old-bpsyncinfo.lis

8) Try to save some of the basic config details:

   bpconfig -L > old-bpconfig.lis

If you do go ahead with a catalog recovery... when done, I suggest:

1) Carefully check the recovery wizard GUI screen log to be sure that it actually has worked.

2) De-activate all policies immediately after the successful recovery (if the GUI will let you).

3) Compare and amend the new vm.conf with your old copy.

4) Take another listing of the master server settings with:

    bpgetconfig -M $master > new.lis

..and compare old.lis to new.lis and see what else you need.

HTH.

After uninstalling a Kaseya agent, it resolved the issue.  It must conflict with one of the ports Netbackup uses...  Thanks for the help everyone!  Now I just have to fix the SL500 with 1 of the 2 drive in a downed state :/

Thanks again!