asked on

Netbackup - nbemm is not starting

We have netbackup 6.5 on a Sun Solaris 9 system that has been running for years, literally. I returned from the holiday weekend to find that it had stopped running. (Nine daemons listed as not running.) The only hint to a possible cause of the problem was an entry in the system logs stating that the partition with the database had filled up over the weekend, but it was below 90% when I checked it..

The nbemm daemon doesn't want to run. When I start it manually, "/usr/openv/netbackup/bin/nbemm", I see the following in the debug log;

13:56:31.940 PID:12595 TID:1 <1> <EMM> - NBEmmSvc::doShouldStart : Should start
13:56:32.480 PID:12602 TID:1 <7> <EMM> - EMMMain : Exception caught attempting EMM orb startup BAD_PARAM
13:56:32.483 PID:12602 TID:1 <2> <EMM> - NBEmmSvc::shutdown_i : Calling shutdown on hosted services

"tpconfig d" returns, after a long wait, "EMM interface initialization failed, status = 77"

As always, the Symantec documentation doesn't seem to be helpful. My suspicion is that the database needs cleaning up, but I can't find anything on how to do that...

SOLUTION

Naga Bhanu Kiran Kota

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

vancleef

ASKER

Well, emm.conf did not exist, so the 1% default must have been in play. However, as stated in the original post. The partition was below 90% when I discovered the problem and currently is at 87% (7Gig available). The disk full note came from the following errors in /var/adm/messages. (hostname changed)

Dec 24 22:23:45 hostname ufs: [ID 845546 kern.notice] NOTICE: alloc: /s1: file system full
Dec 24 22:23:47 hostname SQLAnywhere(nb_palsrv2): [ID 702911 user.error] Fatal error: disk full /usr/openv/db/data/NBDB.log
Dec 24 22:23:50 hostname ufs: [ID 845546 kern.notice] NOTICE: alloc: /s1: file system full

Ten PM on Christmas Eve. Could not have timed it better.

I suspect there is a database cleanup routine out there, somewhere, but I haven't found it and my Symantec support is in contract limbo.

Note: This system has been in production for over five years. This is the first problem, other than tape drive failures, that I have run into.

I attempted to follow the recovery process documented at:

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

Unfortunately, that didn't help. /usr/openv/db/bin/nbdb_ping worked before and after running the rebuild of the NBDB.log, but the nbemm daemon still doesn't start, with the same error.

08:54:46.713 PID:21081 TID:1 <1> <EMM> - NBEmmSvc::doShouldStart : Should start
08:54:47.258 PID:21083 TID:1 <7> <EMM> - EMMMain : Exception caught attempting EMM orb startup BAD_PARAM
08:54:47.261 PID:21083 TID:1 <2> <EMM> - NBEmmSvc::shutdown_i : Calling shutdown on hosted services

Naga Bhanu Kiran Kota

hi van,

refer to this update on symantec and confirm if you have already upgraded to the referred patch level.

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

the emm.conf file should be available under

/user/openv/var/global/emm.conf

regards
bhanu

ASKER CERTIFIED SOLUTION

vancleef

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

Naga Bhanu Kiran Kota

hi van,

that seems to a conflict of configuration which might have caused this, at the same time i was not aware that you had another master server. Thanks for posting back how things started working for you.

Wish you a Happy New Year

Regards
Bhanu