03-16-2011 10:23 AM
When were netbackup media manager is start the service go down
03-16-2011 10:37 AM
HI,
Does this happen on the master or media servers? Check to see if the EMM DB is running on the master (emm) server using nbdb_ping NBDB
If its not running, start it with nbdb_admin -start NBDB
Or restart all the services.
03-16-2011 10:40 AM
It on master server and service and server is restarted , need to check with nbdb_ping
03-16-2011 10:43 AM
Hi,
Do that. If its on the master then its should not be related to comms. What OS?
03-16-2011 10:44 AM
nbdb_admin -start NBDB
error starting NBDB
03-16-2011 10:47 AM
it windows 2003 std
03-16-2011 10:49 AM
What does nbdb_ping show?
Do you have space left on the drive hosting Netbackup?
03-16-2011 10:52 AM
Ping did happen
free space is around 300GB of drive hosting Netbackup
03-16-2011 10:52 AM
Also check <Install_Path>\VERITAS\NetBackupDB\log\server.log
03-16-2011 10:55 AM
Log file is 2GB
03-16-2011 10:59 AM
Please post the output from nbdb_ping
and also nbemmcmd -listhosts
and bpclntcmd -self
and bptestbpcd (without any options)
and bpps
03-16-2011 11:01 AM
What is free space like on the volume that contains the NetBackup installation? Often times, we'll see logs or the images database filling up the volume, causing NetBackup to kill NBDB as a failsafe to not corrupt the database.
You can free up some disk space, then run nbdb_admin -start if that is the problem.
Check out this technote that outlines what I was talking about...
http://www.symantec.com/docs/TECH48381
Most of the time you'll see 93s rather than 77s and Emm interface initilization failed, status = 334 errors, but I've seen it both ways. Just a quick thing you can check out.
EDIT: Looks like I'm late on the free space possibility.
03-16-2011 11:03 AM
Try running the following command and see what it does...
nbdb_upgrade
03-16-2011 11:04 AM
I have 300 GB disk space on NetBackup installation folder
03-16-2011 11:23 AM
Microsoft Windows [Version 5.2.3790]
(C) Copyright 1985-2003 Microsoft Corp.
D:\Program Files\Veritas\NetBackup\bin>bpclntcmd.exe -self
gethostname() returned: bglbg1erbkp1
host bglbg1erbkp1: bglbg1erbkp1.mydom.LOCAL at 172.26.65.57 (0x39411aac)
aliases:
D:\Program Files\Veritas\NetBackup\bin>cd admincmd
D:\Program Files\Veritas\NetBackup\bin\admincmd>bptestbpcd.exe
1 1 1
172.26.65.57:3220 -> 172.26.65.57:13724
172.26.65.57:3221 -> 172.26.65.57:13724
D:\Program Files\Veritas\NetBackup\bin\admincmd>bpps
'bpps' is not recognized as an internal or external command,
operable program or batch file.
D:\Program Files\Veritas\NetBackup\bin\admincmd>cd..
D:\Program Files\Veritas\NetBackup\bin>bpps.exe
* BGLBG1ERBKP1 3/16/11 23:46:24.408
COMMAND PID LOAD TIME MEM START
bpcompatd 2172 0.000% 1.828 9.6M 3/16/11 23:36:16.750
bpinetd 2232 0.000% 1.031 6.3M 3/16/11 23:36:24.343
bpjava-msvc 2456 0.000% 0.765 5.0M 3/16/11 23:36:25.953
bpdbm 2680 0.000% 0.406 13M 3/16/11 23:36:32.562
nbevtmgr 2836 0.000% 0.234 18M 3/16/11 23:36:34.187
bpjobd 2844 0.000% 0.015 12M 3/16/11 23:36:34.421
nbjm 2896 0.000% 0.078 14M 3/16/11 23:36:35.328
bprd 2948 0.000% 0.156 11M 3/16/11 23:36:35.796
nbsvcmon 3036 0.000% 0.109 14M 3/16/11 23:36:36.578
nbstserv 1104 0.000% 0.093 18M 3/16/11 23:36:36.812
vmd 3340 0.000% 1.500 12M 3/16/11 23:36:38.828
ltid 3660 0.000% 0.062 13M 3/16/11 23:36:44.296
nbpem 3704 0.000% 0.046 17M 3/16/11 23:36:44.734
nbrmms 3792 0.000% 0.250 23M 3/16/11 23:36:45.218
nbproxy 3812 0.000% 0.015 13M 3/16/11 23:36:45.453
nbproxy 3832 0.000% 0.015 13M 3/16/11 23:36:45.718
nbproxy 3852 0.000% 0.000 13M 3/16/11 23:36:45.765
nbproxy 3872 0.000% 0.375 16M 3/16/11 23:36:45.828
nbsl 3936 0.000% 0.046 18M 3/16/11 23:36:46.531
dbsrv9 4464 0.000% 0.031 16M 3/16/11 23:40:13.119
bpps 1656 0.000% 0.000 3.6M 3/16/11 23:46:23.237
D:\Program Files\Veritas\NetBackup\bin>nbdb_ping.exe
Database [NBDB] is not available.
D:\Program Files\Veritas\NetBackup\bin\admincmd>nbemmcmd.exe -listhosts
NBEMMCMD, Version:6.5
Failed to initialize EMM connection. Verify that network access to the EMM serv
er is available and that the services nbemm and pbx_exchange are running on the
EMM server. (195)
Command did not complete successfully.
03-16-2011 11:24 AM
D:\Program Files\Veritas\NetBackup\bin>nbdb_upgrade.exe
Verifying the running version of NBDB ...
Verification Failed.
03-16-2011 11:39 AM
Only other thing I can think of is to check that the EMM server name is correctly specified in the registry.
Did anything change prior to this issue? Name change, DNS update, IP Address change?
And up the logging for emm
install_path\veritas\
03-16-2011 01:18 PM
Check if Symantec Private Branch Exchange service is running.
Please try the following:
From cmd, stop all NBU services - bpdown
Go to Services and stop PBX (Symantec Private Branch Exchange)
Move/rename server.log.
Start PBX
From cmd, start NBU services: nbup
Run bpps to check if emm is started.
If still not, please check Event Viewer System and Application log for errors. Also check if new server.log is created.
03-17-2011 07:45 AM
service still not come up
03-17-2011 07:56 AM
Service still not come up hence not going down,
Symantec Private Branch Exchange not stoping