unable to get the EMMSERVER name

[RohitNayal]

Hi All ,

I am getting below error while running the command "nbemmcmd -getemmserver" because of this I am unable to load my java console as I suspect because its unable to get the emmserver name , the device manger got hung .

[root@XXXXXXXXXX admincmd]# ./nbemmcmd -getemmserver

NBEMMCMD, Version: 7.5.0.5

The function returned the following failure status:

CORBA communication error (195)

Command did not complete successfully.

[root@buk003bkup001p admincmd]#

Attaching the bp.conf  /server.conf / databases.conf / servername / vxdbms.conf information in the txt file also attching the host file information also . 

Master Server / EMM Server / Media Server are hosted on same server having NBU Version 7.5.0.5

Server running on  Red Hat Enterprise Linux Server release 5.8 (Tikanga)

Adding unified logging of NBEMM also

Regards ,

Rohit

[Marianne]

Are all NBU processes up and running?

Please post output of:

bpps -x 

[Dyneshia]

also check the bp.conf and makre sure it is correct.

Once we get the output fo what is running we can determine what to focus on.

Last, make sure you have at least 10% free space where NBU is installed at.

[RohitNayal]

[root@xxxxxxp bin]# ./bpps -x

NB Processes

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

root     18652     1  0 13:20 ?        00:00:00 /usr/openv/netbackup/bin/vnetd -standalone

root     18657     1  0 13:20 ?        00:00:00 /usr/openv/netbackup/bin/bpcd -standalone

root     18735     1  0 13:20 ?        00:00:08 /usr/openv/db//bin/NB_dbsrv @/usr/openv/var/global/server.conf @/usr/openv/var/global/databases.conf -hn 7

root     18782     1  0 13:20 ?        00:00:00 /usr/openv/netbackup/bin/nbaudit

root     18894     1  0 13:20 ?        00:00:06 /usr/openv/netbackup/bin/nbemm

root     18904     1  0 13:20 ?        00:00:00 /usr/openv/netbackup/bin/nbrb

root     18926     1  0 13:20 pts/3    00:00:00 /usr/openv/netbackup/bin/bprd

root     18933     1  0 13:20 ?        00:00:00 /usr/openv/netbackup/bin/bpcompatd

root     18938     1  0 13:20 pts/3    00:00:00 /usr/openv/netbackup/bin/bpdbm

root     18946     1  0 13:20 ?        00:00:01 /usr/openv/netbackup/bin/nbjm

root     18952 18938  0 13:20 pts/3    00:00:00 /usr/openv/netbackup/bin/bpjobd

root     18972     1  0 13:20 ?        00:00:01 /usr/openv/netbackup/bin/nbpem

root     19006     1  0 13:20 ?        00:00:04 /usr/openv/netbackup/bin/nbrmms

root     19087     1  0 13:20 ?        00:00:00 /usr/openv/netbackup/bin/nbsl

root     19167     1  0 13:20 pts/3    00:00:00 /usr/openv/netbackup/bin/nbcssc -a NetBackup

root     19191     1  0 13:20 ?        00:00:00 /usr/openv/netbackup/bin/nbsvcmon

root     19225 18946  0 13:20 ?        00:00:00 /usr/openv/netbackup/bin/nbproxy dblib nbjm

root     19287 18972  0 13:20 ?        00:00:02 /usr/openv/netbackup/bin/nbproxy dblib nbpem

root     19953 18972  0 13:40 ?        00:00:00 /usr/openv/netbackup/bin/nbproxy dblib nbpem_cleanup

root     19961 18972  0 13:40 ?        00:00:00 /usr/openv/netbackup/bin/nbproxy dblib nbpem_cleanup

root     19969 18972  0 13:40 ?        00:00:00 /usr/openv/netbackup/bin/nbproxy dblib nbpem_cleanup

root     19975 18972  0 13:41 ?        00:00:00 /usr/openv/netbackup/bin/nbproxy dblib nbpem_cleanup

root     19983 18972  0 13:41 ?        00:00:00 /usr/openv/netbackup/bin/nbproxy dblib nbpem_cleanup

MM Processes

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

root     18909     1  0 13:20 pts/3    00:00:00 /usr/openv/volmgr/bin/ltid

root     18918     1  0 13:20 pts/3    00:00:00 vmd

root     19230 18909  0 13:20 pts/3    00:00:00 tldd

root     19231 18909  0 13:20 pts/3    00:00:00 avrd

root     19234     1  0 13:20 pts/3    00:00:00 tldcd

Shared Symantec Processes

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

root     18622     1  0 13:19 ?        00:00:00 /opt/VRTSpbx/bin/pbx_exchange

[root@xxxx bin]#

[Mark_Solutions]

This line looks to be your issue: EMMSERVER = 10.25.211.10
 

Note sure if a setemmserver using its name will sort this - Marianne will be along shortly!

[RohitNayal]

Bp.conf and all info is already attached in the forum below is space info as requested by you .

df -h /usr/openv

Filesystem            Size  Used Avail Use% Mounted on

/dev/mapper/VolGroup00-LogVol01

                      9.7G  7.8G  1.5G  85% /usr

[RohitNayal]

Hi Mark ,

Could you please let me know where you find this , also I am unable to run the exact command "setemmserver"   

rohit

[Mark_Solutions]

It is in you bp.conf file - so maybe just worth editing that and see if it helps - may need to re-start NetBackup afetrwards:

[root@buk003bkup001p support]# cat /usr/openv/netbackup/bp.conf
SERVER = BUK003BKUP001P
CLIENT_NAME = BUK003BKUP001P
CONNECT_OPTIONS = localhost 1 0 2
USE_VXSS = PROHIBITED
VXSS_SERVICE_TYPE = INTEGRITYANDCONFIDENTIALITY
EMMSERVER = 10.25.211.10
HOST_CACHE_TTL = 3600
VXDBMS_NB_DATA = /usr/openv/db/data
TELEMETRY_UPLOAD = YES
VERBOSE = 5
[root@buk003bkup001p support]#

 

[RohitNayal]

Hi Mark,

Current bp.conf entries restarted all services including pbx , still facing the same issue .

[root@buk003bkup001p netbackup]# cat bp.conf

SERVER = BUK003BKUP001P

CLIENT_NAME = BUK003BKUP001P

CONNECT_OPTIONS = localhost 1 0 2

USE_VXSS = PROHIBITED

VXSS_SERVICE_TYPE = INTEGRITYANDCONFIDENTIALITY

EMMSERVER = BUK003BKUP001P

HOST_CACHE_TTL = 3600

VXDBMS_NB_DATA = /usr/openv/db/data

VERBOSE = 5

TELEMETRY_UPLOAD = YES

[root@buk003bkup001p netbackup]# cat bp.conf

SERVER = BUK003BKUP001P

CLIENT_NAME = BUK003BKUP001P

CONNECT_OPTIONS = localhost 1 0 2

USE_VXSS = PROHIBITED

VXSS_SERVICE_TYPE = INTEGRITYANDCONFIDENTIALITY

EMMSERVER = BUK003BKUP001P

HOST_CACHE_TTL = 3600

VXDBMS_NB_DATA = /usr/openv/db/data

VERBOSE = 5

TELEMETRY_UPLOAD = YES

[Mark_Solutions]

Have you rebooted to try and clear anything that is locking the system?

[Nicolai · Accepted solution]

Is this a new installation ?.

In general raw IP addresses is not supported in Netbackup - the use of name resolution either via host files  or DNS is required. If you want to avoid trouble, use the fully qualified domain name e.g srv1.acme.com instead of just "srv1".

If it's a brand new installation I will recommend to do a re-install rather than edit and "hope".

Just me 0.2 USD  

Best Regrads

Nicolai

[Nicolai]

Be aware of UPPER and lower case host names. UNIX is case sensitive. It best practice to use lower case host names on UNIX systems.

[RohitNayal]

Hi All ,

Thanks for your suggestion issue is resolved after making changes in the host file as suggested by Nicoli using the FQDN name in the host file and configured all backup environment with the FQDN  .