NetBackup Request Manager, NetBackup Database Manager, and NetBackup Volume Manager services automatically exit after a restart.
| Article:TECH23081 | | | Created: 2002-01-29 | | | Updated: 2009-01-09 | | | Article URL http://www.symantec.com/docs/TECH23081 |
Problem
NetBackup Request Manager, NetBackup Database Manager, and NetBackup Volume Manager services automatically exit after a restart.
Error
<16>bp_getservbyname: getservbyname() failed after 3 attempts for bpdbm/tcp
<16> bp_getservbyname: winsock failure - No entry in IP host database.
<32> bprd: cannot contact database daemon...exiting
Solution
For VERITAS NetBackup to function as expected, all its
necessary services need to be running and to stay running. The issue described
here is that these services automatically exit after attempts to restart them,
hence backups, restores, etc could not even begin to be launched.
The bprd log under <install_path>\VERITAS\netbackup\logs shows the following error messages:
16:14:40 [960.968] <2> bprd: Created terminate event:"NetBackup Terminate Event, pid: 960"
16:14:40 [960.968] <4> bprd: INITIATING bprd: NetBackup 3.4GA 2000062208 on ca68app01
16:14:40 [960.968] <4> bprd: commandline: "C:\Program Files\VERITAS\NetBackup\bin\bprd.exe"
16:14:40 [960.968] <2> bprd: initiate dbm daemon...
16:14:49 [960.968] <16> bp_getservbyname: getservbyname() failed after 3 attempts for bpdbm/tcp
16:14:49 [960.968] <16> bp_getservbyname: winsock failure - No entry in IP host database.
16:14:49 [960.968] <16> getsockconnected: cannot find Internet service bpdbm/tcp
16:14:49 [960.968] <16> db_dbm_alive: getsockconnected() failed: The operation completed successfully. (0)
16:14:49 [960.968] <32> bprd: cannot contact database daemon...exiting
The bprd log under <install_path>\VERITAS\netbackup\logs shows the following error messages:
16:14:40 [960.968] <2> bprd: Created terminate event:"NetBackup Terminate Event, pid: 960"
16:14:40 [960.968] <4> bprd: INITIATING bprd: NetBackup 3.4GA 2000062208 on ca68app01
16:14:40 [960.968] <4> bprd: commandline: "C:\Program Files\VERITAS\NetBackup\bin\bprd.exe"
16:14:40 [960.968] <2> bprd: initiate dbm daemon...
16:14:49 [960.968] <16> bp_getservbyname: getservbyname() failed after 3 attempts for bpdbm/tcp
16:14:49 [960.968] <16> bp_getservbyname: winsock failure - No entry in IP host database.
16:14:49 [960.968] <16> getsockconnected: cannot find Internet service bpdbm/tcp
16:14:49 [960.968] <16> db_dbm_alive: getsockconnected() failed: The operation completed successfully. (0)
16:14:49 [960.968] <32> bprd: cannot contact database daemon...exiting
The Request
Manager daemon (bprd) attempts to initiate the Database Manager daemon
(dbm / bpdbm). As there is no bpdbm service entry in the IP host
database, it cannot connect to it successfully, resulting in the
NetBackup Request Manager daemon exiting.
To fix this
issue, and for NetBackup to start up properly, ensure that the
C:\WINNT\system32\drivers\etc\services file has not been corrupted and
that it contains at least the following entries:
bprd
13720/tcp
bpdbm
13721/tcp
bpcd
13782/tcp
vmd
13701/tcp
vopied
13783/tcp
The following
entries may also be required for the Media Manager Services (NetBackup Device
Manager Service), depending on what tape library has been configured:
acsd
13702/tcp
tl8cd
13705/tcp
odld
13706/tcp
ts8d
13709/tcp
tldcd
13711/tcp
tl4d
13713/tcp
tsdd
13714/tcp
tshd
13715/tcp
tlmd
13716/tcp
tlhcd
13717/tcp
lmfcd
13718/tcp
rsmd
13719/tcp
|
|
Legacy ID
252253
Article URL http://www.symantec.com/docs/TECH23081
Terms of use for this information are found in Legal Notices
Thank you.