cancel
Showing results for 
Search instead for 
Did you mean: 

NBEMM error 77

Jacob_Ruben
Level 4
Certified

In our oeganisation, we have installed a new master server version 7.6. it installed well and we had configured the storage deavices and also created policy.

It was working well but all of a sudden am getting this NMEBB error (77). Tried restarting servive but got an error message "The NBEMM service on local computer started and then stopped. Some services stop automatically if they are not in use by other services or programs"

I tried stopping netbackup and start again. No change.

Doing my R&D but if any one has any suggestion please advice.

10 REPLIES 10

Marianne
Moderator
Moderator
Partner    VIP    Accredited Certified

Has anything changed at OS or network level?
DNS, hostname, IP, etc?

Please try to stop and start once more as follows and post output of commands:

Stop all NetBackup services from cmd (<install_path>\NetBackup\bin) :
 bpdown -f -v
Confirm that all NBU processes are down with 
bpps 
 
If not, run bpdown again.
 
 Stop and restart PBX (Symantec Private Branch Exchange) in Services
 
Create 'admin' folder under <install_path>\NetBackup\logs
(This will help with troubleshooting if needed.)
 
 Start all NetBackup services:
From same cmd, run 
bpup -f -v

Run 'bpps' again to check that services/processes are up.

Please post output of commands. 

RiaanBadenhorst
Moderator
Moderator
Partner    VIP    Accredited Certified

Hi,

 

Check the EMM logs with vxlogview -a -o 111 -t 00:05

 

Do this after restarting the service.

 

Also check that the database server is up using nbdb_ping

 

And make sure you have enough free space on the drive netbackup is installed on.
 

Jacob_Ruben
Level 4
Certified

Hi Marrian,

Below is the output..

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

NetBackup 7.6 -- Shutdown Utility

Shutting down services
> NetBackup Bare Metal Restore Master Server
> NetBackup Bare Metal Restore Master Server -- STOPPED
> NetBackup Web Management Console
> NetBackup Web Management Console -- STOPPED
> NetBackup Indexing Manager
> NetBackup Indexing Manager -- STOPPED
> NetBackup Service Monitor
> NetBackup Service Monitor -- STOPPED
> NetBackup Agent Request Server
> NetBackup Agent Request Server -- STOPPED
> NetBackup Storage Lifecycle Manager
> NetBackup Storage Lifecycle Manager -- STOPPED
> NetBackup Key Management Service
> NetBackup Key Management Service -- STOPPED
> NetBackup Vault Manager
> NetBackup Vault Manager -- STOPPED
> NetBackup Service Layer
> NetBackup Service Layer -- NOT STOPPED
> NetBackup Policy Execution Manager
> NetBackup Policy Execution Manager -- STOPPED
> NetBackup Job Manager
> NetBackup Job Manager -- STOPPED
> NetBackup Request Daemon
> NetBackup Request Daemon -- STOPPED
> NetBackup Compatibility Service
> NetBackup Compatibility Service -- STOPPED
> NetBackup Database Manager
> NetBackup Database Manager -- STOPPED
> NetBackup Audit Manager
> NetBackup Audit Manager -- STOPPED
> NetBackup Authorization
> NetBackup Authorization -- DISABLED
> NetBackup Authentication
> NetBackup Authentication -- STOPPED
> NetBackup CloudStore Service Container
> NetBackup CloudStore Service Container -- STOPPED
> NetBackup Deduplication Engine
> NetBackup Deduplication Engine -- DISABLED
> NetBackup Deduplication Manager
> NetBackup Deduplication Manager -- DISABLED
> 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
> NetBackup Relational Database Manager
> NetBackup Relational Database Manager -- STOPPED
> NetBackup Event Manager
> NetBackup Event Manager -- STOPPED
> NetBackup Deduplication Multi-Threaded Agent
> NetBackup Deduplication Multi-Threaded Agent -- STOPPED
> NetBackup Discovery Framework
> NetBackup Discovery Framework -- STOPPED
> NetBackup SAN Client Fibre Transport Service
> NetBackup SAN Client Fibre Transport Service -- STOPPED
> NetBackup Client Service
> NetBackup Client Service -- STOPPED
> NetBackup Legacy Client Service
> NetBackup Legacy Client Service -- STOPPED
> NetBackup Legacy Network Service
> NetBackup Legacy Network Service -- STOPPED

Shutting down robot control daemons
Calling nbproxyreq to cleanup nbproxy processes.

Shutdown completed successfully.


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

-------------------

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

NetBackup 7.6 -- 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 -- NOT STARTED
> NetBackup Discovery Framework
> NetBackup Discovery Framework -- STARTED
> NetBackup Deduplication Multi-Threaded Agent
> NetBackup Deduplication Multi-Threaded Agent -- 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 Deduplication Manager
> NetBackup Deduplication Manager -- DISABLED
> NetBackup Deduplication Engine
> NetBackup Deduplication Engine -- DISABLED
> NetBackup CloudStore Service Container
> NetBackup CloudStore Service Container -- STARTED
> NetBackup Authentication
> NetBackup Authentication -- STARTED
> NetBackup Authorization
> NetBackup Authorization -- DISABLED
> NetBackup Audit Manager
> NetBackup Audit Manager -- STARTED
> NetBackup Database Manager
> NetBackup Database Manager -- STARTED
> NetBackup Compatibility Service
> NetBackup Compatibility Service -- STARTED
> NetBackup Request Daemon
> NetBackup Request Daemon -- STARTED
> 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
> 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 Indexing Manager
> NetBackup Indexing Manager -- STARTED
> NetBackup Web Management Console
> NetBackup Web Management Console -- STARTED
> NetBackup Bare Metal Restore Master Server
> NetBackup Bare Metal Restore Master Server -- STARTED
Start up of one or more services failed.
--------------------------------------------

the nbemm shows as started , but when we see it in the services. it is not started. I have also attached the admin log.

Thanks for support Marianne.


===================================================================

Hi Riaan

dtabase is alive.

C:\Program Files\Veritas\NetBackup\bin>nbdb_ping
Database [NBDB] is alive and well on server [NB_InChnM02].
===================================================================

Michael_G_Ander
Level 6
Certified

the server.log under the ../backupdb/log directory might hold some clues to why the EMM database stops

The standard questions: Have you checked: 1) What has changed. 2) The manual 3) If there are any tech notes or VOX posts regarding the issue

Marianne
Moderator
Moderator
Partner    VIP    Accredited Certified

No errors in admin log.

This output is missing from Riaan's request:

Check the EMM logs with vxlogview -a -o 111 -t 00:05

Do this after restarting the service.

The EMM log should tell us why nbemm is starting and stopping again.

The value specified with '-t' option needs to be big enough to include the last startup attempt, that is why Riaan has asked for 5 minutes provided you issued the command directly after the last startup attempt.

If startup attempt was 30 minutes ago, use command as follows (adjust as needed):

vxlogview -a -o 111 -t 00:30:00

Please post this output.

Pangal
Level 5

whether netbackup was upgraded ?? if yes it mite be nbdb ugrade issue.

kindly refer this technote to upgrade nbdb

http://www.symantec.com/business/support/index?page=content&id=TECH182266

 

 

 

 

Marianne
Moderator
Moderator
Partner    VIP    Accredited Certified

No reply from this user since 30 June and no reply to my PM.

Hopefully issue is resolved by now! frown

mph999
Level 6
Employee Accredited

If you do post emm log please also use the -d all option as without it you cannot follow the different threads ...

vxlogview -a -o 111 -d all -t 00:30:00

Jaime_Vazquez
Level 6
Employee


The proable cause is for what is called "Endpoint Selection" process.
This I believe can be seen in the log file snippet:

=====
(from submitted file at 7.6.?):
13:38:12.519 [10244.10216] <2> Orb::init: initializing ORB Default_CLIENT_Orb with: Unknown -ORBSvcConfDirective "-ORBDottedDecimalAddresses 0" ........
----
(from my test server at 7.6.0.2):
8/7/2014 19:08:47.798 [Orb::init] endpointvalue is : pbxiop://1556:EMM(Orb.cpp:809)
8/7/2014 19:08:47.798 [Orb::init] initializing ORB EMM with: EMM -ORBSvcConfDirective "-ORBDottedDecimalAddresses 0" .......
=====

The area of concern is in bold.  The values of "Default_CLIENT_Orb" and "Unknown" are problemtic.

Do an "ipconfig /all" on the Master. For each IP, do a "nslookup" of that IP. Ensure it has a valid response. Verify DNS if need be.

The debug level of the submitted log appears to be too low and should be set higher. For diagnostic purposes, I would be doing this:

bpdown -v -f   (down services)
vxlogmgr -d -o 111  (reply with yes and delete the old log files)
vxlogcfg -a -p 51216 -o 111 -s DebugLevel=5    (elevate debug level)
bpup -v -f     (start services)
bpps (check for nbemm)
vxlogview -i 111 > $PATH\emmlog111.txt   (extract debug statement from log to a file)
vxlogcfg -a -p 51216 -o 111 -s DebugLevel=1   (reset debug level to default)

Look at the file created for information.  Submit with new comment if possible.

Marianne
Moderator
Moderator
Partner    VIP    Accredited Certified

Jacob_Ruben stopped responding on 30 June..............