Video Screencast Help

Unable to start BPRD

Created: 01 Apr 2013 • Updated: 28 Aug 2014 | 36 comments
This issue has been solved. See solution.

Hi All,

I have a Windows 2003 Master Server with NBU 7.1.0.2 on it. Netbackup Request Daemon (followed by bpdbm,nbjm and nbpem) are stopped. Any attempts to start them throws an error "Service did not respond in a timely fashion".

Please advise.

Thanks.

Operating Systems:

Comments 36 CommentsJump to latest comment

Dan@NB's picture

Preethi,

You might need to check on the below link:

http://www.symantec.com/business/support/index?pag...

Please check which account Netbackup Services are using. It should be Local System account.

Best Regards,
Dan

Preethi S's picture

Hi Dan,

Yes, It uses Local System account only.

Thanks.

inn_kam's picture

bpdown.exe -f -v 

then 

bpup.exe -f -v 

 

and then check

inn_kam's picture

Hi

do you check after restarting the services

Preethi S's picture

Yes, Netbackup services were restarted. Still, no luck.

Will Restore's picture

Recent changes?  Patches?  Updates?

Maybe best to open support ticket.

Will Restore -- where there is a Will there is a way

Marianne's picture

Please stop all services again with bpdown, then create bprd log folder in <install-path>\veritas\netbackup\logs. Start NBU with bpup.

Copy log file in logs folder to bprd.txt and post here as file attachment.

Things to check before doing the above: 

Compare output of 'hostname' with output of <install-path>\veritas\netbackup\bin\bpclntcmd -self.
Are they the same?
Also check NBU Server entries in registry (using regedt32, not regedit):  

HKEY_LOCAL_MACHINE\SOFTWARE\Veritas\NetBackup\CurrentVersion\Config\Server

Does first Server entry correspond with 'hostname' output and bpclntcmd output?
If not - has master server hostname been changed?
 

Supporting Storage Foundation and VCS on Unix and Windows as well as NetBackup on Unix and Windows
Handy NBU Links

SOLUTION
Nicolai's picture

Reboot ?

Assumption is the mother of all mess ups.

If this post answered your'e qustion -  Please mark as a soloution.

Preethi S's picture

All the entries are appropriate. No bprd logs are getting created on the server.

Dan@NB's picture

Preethi,

You will have to check the logging levels. 5 to capture it all. Give it try and post the logs (as Marianne suggested) captured here for further analysis.

+Dan

Preethi S's picture

Verbose is set to 5, logging location was verified, server rebooted..but, no logs were created to verify.

Dan@NB's picture

Try this:

1. Bring NBU services down.
2. Check task manager for any hung NBU processes (Multiple instances can be one of the reason for such issue)
3. Kill any hung NBU processes.
4. Bring NBU back UP.

Let us know.

+Dan

Dan@NB's picture

just to add to that could you please check nbsvcmon is running..

+Dan

Marianne's picture

No bprd logs are getting created on the server. 

If you are 100% sure that there is no typo error in folder name and you are 100% sure that folder is in the correct, then something is seriously wrong here...

Please show us output of bpup.exe -f -v (after bpdown and killing left-over processes).
Also check Event Viewer Application and System logs for errors.

In the meantime - log Sev 1 call with Symantec Support.

Supporting Storage Foundation and VCS on Unix and Windows as well as NetBackup on Unix and Windows
Handy NBU Links

Preethi S's picture

nbsvcmon is running, no hung processes detected and no relevant logs in Event Viewer. Case has been logged with Symantec.

Marianne's picture

Repeat of previous request:

Please show us output of bpup.exe -f -v (after bpdown and killing left-over processes).
Also check Event Viewer Application and System logs for errors.

Supporting Storage Foundation and VCS on Unix and Windows as well as NetBackup on Unix and Windows
Handy NBU Links

Preethi S's picture

 
NetBackup 7.1 -- Startup Utility
 
Starting services
> NetBackup Legacy Network Service
> NetBackup Legacy Network Service -- STARTED
> NetBackup Legacy Client Service
> NetBackup Legacy Client Service -- STARTED
> NetBackup Client Service
> NetBackup Client Service -- STARTED
> NetBackup SAN Client Fibre Transport Service
> NetBackup SAN Client Fibre Transport Service -- STARTED
> NetBackup Event Manager
> NetBackup Event Manager -- STARTED
> NetBackup Relational Database Manager
> NetBackup Relational Database Manager -- STARTED
> NetBackup Enterprise Media Manager
> NetBackup Enterprise Media Manager -- STARTED
> NetBackup Resource Broker
> NetBackup Resource Broker -- STARTED
> NetBackup Volume Manager
> NetBackup Volume Manager -- STARTED
> NetBackup Device Manager
> NetBackup Device Manager -- STARTED
> NetBackup Remote Manager and Monitor Service
> NetBackup Remote Manager and Monitor Service -- STARTED
> NetBackup Authentication
> NetBackup Authentication -- NOT STARTED
> NetBackup Authorization
> NetBackup Authorization -- NOT STARTED
> NetBackup Audit Manager
> NetBackup Audit Manager -- STARTED
> NetBackup Database Manager
> NetBackup Database Manager -- NOT STARTED
> NetBackup Compatibility Service
> NetBackup Compatibility Service -- STARTED
> NetBackup Request Daemon
> NetBackup Request Daemon -- NOT STARTED
> NetBackup Job Manager
> NetBackup Job Manager -- NOT STARTED
> NetBackup Policy Execution Manager
> NetBackup Policy Execution Manager -- NOT STARTED
> NetBackup Service Layer
> NetBackup Service Layer -- STARTED
> NetBackup Vault Manager
> NetBackup Vault Manager -- NOT STARTED
> NetBackup Key Management Service
> NetBackup Key Management Service -- STARTED
> NetBackup Storage Lifecycle Manager
> NetBackup Storage Lifecycle Manager -- NOT STARTED
> NetBackup Agent Request Server
> NetBackup Agent Request Server -- STARTED
> NetBackup Service Monitor
> NetBackup Service Monitor -- STARTED
> NetBackup Bare Metal Restore Master Server
> NetBackup Bare Metal Restore Master Server -- STARTED
> NetBackup Bare Metal Restore Boot Server
> NetBackup Bare Metal Restore Boot Server -- STARTED
Start up of one or more services failed.

revaroo's picture

Let's see the contents of your reg entry: HKEY_LOCAL_MACHINE\SOFTWARE\Veritas\NetBackup\CurrentVersion\Config\Server

 

Then lets see output of:

ipconfig

hostname

bpclntcmd -hn <hostname of master>

 

 

Marianne's picture

Seems the problem starts first of all with NBU Database Manager not starting:

NetBackup Database Manager
> NetBackup Database Manager -- NOT STARTED

Do you have bpdbm log folder?

Anything logged there?

What about Event viewer logs?

 

Supporting Storage Foundation and VCS on Unix and Windows as well as NetBackup on Unix and Windows
Handy NBU Links

Preethi S's picture

Nothing logged in bpdbm or Event Viewer

Marianne's picture

Have you logged that Sev 1 call with Symantec yet as suggested over the weekend?

Have you checked that bpdbm.exe and bprd.exe binaries are present and correct file size?

 

Supporting Storage Foundation and VCS on Unix and Windows as well as NetBackup on Unix and Windows
Handy NBU Links

Preethi S's picture

Yes, I did log a call with Symantec. They are still investigating. No clue so far !

revaroo's picture

Preethi, let's see the contents please of those outputs I posted?

Also have you checked your license hasn't expired

mph999's picture

What is the Symantec case number ?

 

Regards,  Martin
 
Setting Logs in NetBackup:
http://www.symantec.com/docs/TECH75805
 
Marianne's picture

Something has probably gone wrong with NBU installation - perhaps corrupt binaries?
When did the problem start?
I can hardly believe that there is NOTHING in Event Viewer System or Application logs...

Do you have recent catalog backup so that you can completely uninstall NBU, reinstall and recover catalogs?

It may even be possible to uninstall NBU, while leaving NBU catalogs intact, reinstall NBU 7.1, followed by patch. This will certainly fix corrupt binaries.

Another option is to patch with NBU 7.1.0.4 which should also fix corrupt binaries.

Supporting Storage Foundation and VCS on Unix and Windows as well as NetBackup on Unix and Windows
Handy NBU Links

Mark_Solutions's picture

How is your disk space on the server?

It does sound more serious than that but just wondering...

Also, have you been using a full license key? - again in case a temporary / evaluation key has run out

Authorised Symantec Consultant

Don't forget to "Mark as Solution" if someones advice has solved your issue - and please bring back the Thumbs Up!!.

Preethi S's picture

There is enough disk space on the server and we do have active permanent license in place.

Mark_Solutions's picture

Anything in the admin log?

Does anything log at all? bpcd, nbpem, nbrb?

Show us what ever you can from the server please

Authorised Symantec Consultant

Don't forget to "Mark as Solution" if someones advice has solved your issue - and please bring back the Thumbs Up!!.

Will Restore's picture

OK, thought maybe April Fools joke if Symantec priority 1 case open & they cannot figure it out. :)

Will Restore -- where there is a Will there is a way

revaroo's picture

It's not a priority 1 in the system. It should be though.

Marianne's picture

Curious to know if there is any update on this?

Supporting Storage Foundation and VCS on Unix and Windows as well as NetBackup on Unix and Windows
Handy NBU Links

revaroo's picture

Restart NetBackup, when bprd fails to start send the Symantec engineer working on your case the following logs.

bprd

admin

Event Application Logs

 

These should be the only logs needed if bprd is failing to start.

 

Marianne's picture

More than a year later....

Found out today that this issue was eventually resolved:

https://www-secure.symantec.com/connect/forums/netbackup-volume-managerrequest-daemondevice-manager-services-are-not-coming#comment-10046491

Solution: USE_VXSS = Automatic -  deleted the key

(Seems the OP totally forgot to tell us that VxSS/NBAC config was attempted?)

Supporting Storage Foundation and VCS on Unix and Windows as well as NetBackup on Unix and Windows
Handy NBU Links