Forum Discussion

24 Replies

Show More
  • Chris_Morris's avatar
    Chris_Morris
    Level 3
    15 years ago

    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.

  • jyothish_b's avatar
    jyothish_b
    Level 4
    15 years ago

    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.

  • jyothish_b's avatar
    jyothish_b
    Level 4
    15 years ago

    D:\Program Files\Veritas\NetBackup\bin>nbdb_upgrade.exe
    Verifying the running version of NBDB ...
    Verification Failed.

  • RiaanBadenhorst's avatar
    RiaanBadenhorst
    Level 6
    15 years ago

    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\

    netbackup\bin\vxlogcfg -a -p 51216 -o 111 -s DebugLevel=6 -s DiagnosticLevel=6

     
    Then restart the emm service and check the log
     
    install_path\veritas\netbackup\bin\vxlogview -p 51216 -o 111 -t 00:05:00

  • Marianne's avatar
    Marianne
    Level 6
    15 years ago

    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.

  • jyothish_b's avatar
    jyothish_b
    Level 4
    15 years ago

    Service still not come up hence not going down,

    Symantec Private Branch Exchange not stoping

  • Marianne's avatar
    Marianne
    Level 6
    15 years ago

    As per Riaans post - check the emm log after trying to start it:

     
    install_path\veritas\netbackup\bin\vxlogview -p 51216 -o 111 -t 00:05:00
     
     
    This command will report on the last 5 minutes (-t 00:05:00)
     
    If the output is quite large, please redirect output to a file an post as attachment.
     
    *******
     
    Private Branch Echange not stopping?
     
    Seems that's where the problem is.
     
    Have you checked Event Viewer System and Application logs?