My all NBU services are stopped

[Zahid_Haseeb]

NBU 6.5.4
OS of NBU is win2003 R2

My all Netbackup Services are stopped. I shutdown my NBU server yesterday but today when i opened my NBU server its giving me error and no service is started even i restarted my NBU server twice....:(

Below snap for information

[Andy_Welburn]

Event Viewer?

[Zahid_Haseeb]

Thanks for your kind reply

i think my NBU is expired. I have also new keys. would you please help me to add new license keys in NBU

[Andy_Welburn]

Was it an evaluation license key that's expired?

You should just be able to open the Admin Console & go to Help > License Keys to add your new license(s). [I think, never had an occasion to do this on an effectively 'dead' system]

For info:

Frequently asked questions about license keys

[sdo]

If admin console won't connect, then use the command line to add keys:
$ bpminlicense -add_keys XXXX-XXXX-XXXX-...

[sdo]

You check whether an expired license really is the problem:
$ cd <install-path>\VERITAS\NetBackup\logs\bpdbm
$ find /i "lice" 050510.log
 

[Zahid_Haseeb]

Thanks sdw303 ....i have already add the license key. But still when i open the NBU. i faced the below error

[Andy_Welburn]

http://seer.entsupport.symantec.com/docs/297548.htm

[sdo]

You need to bounce services:
$ bpdown -f -v
...and:
$ bpup -f -v
...for the newly added license keys to take effect.

[Zahid_Haseeb]

Andy:-  in your document i did not find any thing which i can apply. Yes i tried to bpup command which i think UP all the services but i still face same problem


sdw303:-  i am still facing the same error after doing what you have sugessted.
sdw303 the command which you suggested given me the below result

C:\Program Files\Veritas\NetBackup\bin>bpdown -f -v

NetBackup 6.5 -- Shutdown Utility

Shutting down services
> NetBackup Service Monitor
> NetBackup Service Monitor -- STOPPED
> NetBackup Storage Lifecycle Manager
> NetBackup Storage Lifecycle Manager -- STOPPED
> NetBackup Key Management Service
> NetBackup Key Management Service -- STOPPED
> BMR Master Service
> BMR Master Service -- STOPPED
> NetBackup Vault Manager
> NetBackup Vault Manager -- STOPPED
> NetBackup Service Layer
> NetBackup Service Layer -- STOPPED
> NetBackup Policy Execution Manager
> NetBackup Policy Execution Manager -- STOPPED
> NetBackup Job Manager
> NetBackup Job Manager -- STOPPED
> NdmpMoverListener
> NetBackup Request Daemon
> NetBackup Request Daemon -- STOPPED
> NetBackup Compatibility Service
> NetBackup Compatibility Service -- STOPPED
> NetBackup Database Manager
> NetBackup Database Manager -- STOPPED
> NetBackup Remote Manager and Monitor Service
> NetBackup Remote Manager and Monitor Service -- STOPPED
> NetBackup Device Manager
> NetBackup Device Manager -- STOPPED
> NetBackup Volume Manager
> NetBackup Volume Manager -- STOPPED
> NetBackup Resource Broker
> NetBackup Resource Broker -- STOPPED
> NetBackup Enterprise Media Manager
> NetBackup Enterprise Media Manager -- STOPPED
> ASANYs_VERITAS_NB
> ASANYs_VERITAS_NB -- STOPPED
> NetBackup Event Manager
> NetBackup Event Manager -- STOPPED
> NetBackup Notification Service
> BMR Boot Service
> NetBackup SAN Client Fibre Transport Service
> NetBackup SAN Client Fibre Transport Service -- STOPPED
> NetBackup INET Daemon
> NetBackup INET Daemon -- STOPPED

Shutdown completed successfully.

C:\Program Files\Veritas\NetBackup\bin>bpup -f -v

NetBackup 6.5 -- Startup Utility

Starting services
> NetBackup INET Daemon
> NetBackup INET Daemon -- STARTED
> NetBackup SAN Client Fibre Transport Service
> NetBackup SAN Client Fibre Transport Service -- STARTED
> BMR Boot Service
> NetBackup Notification Service
> NetBackup Event Manager
> NetBackup Event Manager -- STARTED
> ASANYs_VERITAS_NB
> ASANYs_VERITAS_NB -- 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 Database Manager
> NetBackup Database Manager -- STARTED
> NetBackup Compatibility Service
> NetBackup Compatibility Service -- STARTED
> NetBackup Request Daemon
> NetBackup Request Daemon -- STARTED
> NdmpMoverListener
> NetBackup Job Manager
> NetBackup Job Manager -- STARTED
> NetBackup Policy Execution Manager
> NetBackup Policy Execution Manager -- STARTED
> NetBackup Service Layer
> NetBackup Service Layer -- STARTED
> NetBackup Vault Manager
> NetBackup Vault Manager -- STARTED
> BMR Master Service
> BMR Master Service -- STARTED
> NetBackup Key Management Service
> NetBackup Key Management Service -- STARTED
> NetBackup Storage Lifecycle Manager
> NetBackup Storage Lifecycle Manager -- STARTED
> NetBackup Service Monitor
> NetBackup Service Monitor -- STARTED

Start up completed successfully.

C:\Program Files\Veritas\NetBackup\bin>

[Andy_Welburn]

was merely an aid so you could check which ones needed to be running - I know it's pretty obvious once you get in to Services but sometimes things are missed. e.g. Symantec PBX as it doesn't begin with "NetBackup"!!

Can you confirm that the Request Manager is running? Your error indicates it isn't but it could be lying!

Again, any errors logged in Event Viewer? Maybe only recourse would be to restart the physical server?

[Zahid_Haseeb]

Andy i restarted the server but still facing same error

Yes Resource Broker is running.

i also attached the services snapshot below

[Zahid_Haseeb]

I am also attaching the event viewer two snaps

[Andy_Welburn]

is running from your output!

Have you tried to manually start those services that are listed as not running? Not ideal but it may help or give an indication of any issues.

Again, any errors in Event Viewer? ***EDIT*** I see you've posted something now!

[Andy_Welburn]

Troubleshooting Guide:

"...
Media Manager status code: 58
Message: daemon cannot obtain socket
Explanation: vmdcannot bind to its socket. (vmd is the NetBackup Volume Manager daemon on UNIX and the NetBackup Volume Manager service on Windows.) When vmdattempts to bind to its configured port number, system call fails. The call fails usually because another process having acquired the port before the vmd daemon or service started.
Recommended action:
■Examine the daemon debug log for a more detailed message on the system error.
■If another process has the port, use other system commands to determine the process. Based on the result, either change the port number in your services file or map, or terminate the process that has acquired the port.
..."

[Marianne]

The source of the error code is 'NetBackup Key Management Service'.
You might not have valid license keys for all the features you have configured. For example - you need Library Based Tape Drive license if you have a robot and tape drives.
Please post output of bpminlicense -list_keys -verbose

[sudu_mlk]

with an error 58, indicates that vmd can either not find the services entry for vmd, or the port is already in use.

Please check services files under drivers\etc\ folder and if vmd port is unavalable, add the port number.

stop and start the NB services and post results.

--SUDU

[sdo]

bprd seems to be running from the list above.
If you are not performing LTO media encryption then ignore the Key Management Server.
If you do not have SAN/FT clients then ignore the SAN Client FT Service.
If you do not have tape and only have one DSU, for example on a test/dev instance of NetBackup, then ignore the Device Manager.

The two issues that I see are "bpdbm" and "vmd" not running.


To get to the bottom of the VMD (i.e. Volume Manager Daemon) issues you may need to do the following:
1) Create the "debug" folder under "<install-path>\Volmgr"  - this is the logging folder, i.e. as you have "logs" under \NetBackup, you need "\debug" under "\Volmgr" to collect logging for VMD.
2) Now under the "\debug" folder create the following seven sub-folders
    daemon
    dqts
    ltid
    reqlib
    robots
    tpcommand
    tpreq
3) Now add the line:
VERBOSE
...to your vm.conf file in "<install-path>\Volmgr"
4) Restart NetBackup (i.e. bpdown -f-v followed by bp -f -v).
5) Then look for anything indicative of a problem in the log files in the folders under \Volmgr\debug.


For "bpdbm" NetBackup Database Manager:
1) Under "<install-path>\NetBackup\logs"   run the "mklogdir.bat" file.
2) And then restart NetBackup again - and then look in the "\NetBackup\logs\bpdbm" folder at the end of the latest log file, to see if there's anything indicative of a problem too.


Good luck.

[Zahid_Haseeb]

Sudu.mlk   what would be the pattern to add the vmd service in services file under etc folder

[Zahid_Haseeb · Accepted solution]

Thanks to all my friends and Symantec as well. My problem is resolved after following the below symantec document.
http://seer.entsupport.symantec.com/docs/252253.htm

I add the below in the /etc/services

bprd 13720/tcp
bpdbm 13721/tcp
bpcd 13782/tcp
vmd 13701/tcp
vopied 13783/tcp

Resolution BLOG
https://www-secure.symantec.com/connect/blogs/netbackup-does-not-have-service-bprd-operatingerror-25