Forum Discussion

Eshwar99's avatar
Eshwar99
Level 2
12 months ago

nbdb_admin -validate is successful but bptest or nbemmcmd.exe -getemmserver are failing.

nbdb_admin -validate is successful but bptest or nbemmcmd.exe -getemmserver are failing. Failed to get the configuration for the host "XXXXXX". no entity was found(227).

D:\veritas\NetBackup\bin\admincmd>nbemmcmd.exe -getemmserver
NBEMMCMD, Version: 8.2
These hosts were found in this domain: XXXXXX, XXXXX, XXXXX

Checking with the host "XXXXXXX"...
Checking with the host "XXXXXXX"...
Checking with the host "XXXXXXX"...
Checking with the host "XXXXXXX"...
Checking with the host "XXXXXXX"...
Checking with the host "XXXXXXX"...
Checking with the host "XXXXXXX"...
Checking with the host "XXXXXXX"...

Server Type     Host Version         Host Name                      EMM Server
<unknown>       UNKNOWN RELEASE (-2) XXXXXXX <unknown> *Failed to get the configuration for the host "XXXXXXX". no entity was found(227)
<unknown>       UNKNOWN RELEASE (-2) XXXXXXX <unknown> *Failed to get the configuration for the host "XXXXXXX". no entity was found(227)
<unknown>       UNKNOWN RELEASE (-2) XXXXXXX <unknown> *Failed to get the configuration for the host "XXXXXXX". no entity was found(227)
<unknown>       UNKNOWN RELEASE (-2) XXXXXXX <unknown> *Failed to get the configuration for the host "XXXXXXX". cannot connect on socket(25)
<unknown>       UNKNOWN RELEASE (-2) XXXXXXX <unknown> *Failed to get the configuration for the host "XXXXXXX". no entity was found(227)
MASTER          8.2                  XXXXXXX                  XXXXXXX
<unknown>       UNKNOWN RELEASE (-2) XXXXXXX                      <unknown> *Failed to get the configuration for the host "XXXXXXX". no entity was found(227)
MASTER          8.2                  XXXXXXX                   XXXXXXX

One or more hosts had mismatched EMM Servers.
There were problems getting information on one or more hosts.
The consistency check either failed or was incomplete.
Command did not complete successfully.

 

Any help is greatly appreciated.

5 Replies

  • Can you confirm if this is a cluster as that would be the only reason for multiple masters, if so fail it over to the other node and see if that fixes it...  If it does it means that your cluster configs are not correct.

     

  • Have you confirmed that all of your media servers have the correct EMM entry in the bp.conf/Registry? 

  • What has changed recently in your environment? Have you done upgrades, a migration, a DR recovery of the catalog  or something like that?  I've only ever seen these issues when Media servers are moved to different masters and the PBX communication is not working correctly, or if upgrades are done in the wrong order.

    I also notice that  getemmserver output shows 2 MASTERS I'm guessing this is a cluster?    Has the cluster failed over recently is that the cause?  If so maybe there is a configuration issue with the clustering and some shared volumes are not shared, or some config has not been kept in sync between them...

    In my experience an UNKNOWN RELEASE often means that the Version is HIGHER than the master..   if you have been doing upgrades you need to make sure that the MASTER is upgraded first.




    • Eshwar99's avatar
      Eshwar99
      Level 2

      Hi 

      Due to Microsoft  issue over the weekend, servers got impacted and as part of fixing the issue, servers were rebooted. Post reboot, we observed disconnect between master and media servers. 

      All configurations were checked. nbdb test, emm listhosts,. telnet all are successful and for bptest have been getting this below listed error.  

      D:\veritas\NetBackup\bin\admincmd>bptestbpcd.exe -client XXXXXXXX -verbose
      PEER_NAME = XXXXXXX
      HOST_NAME = XXXXXXXX
      <16>bptestbpcd main: Function ConnectToBPCD(XXXXXXXX) failed: 227
      <16>bptestbpcd main: no entity was found
      <16>bptestbpcd main: Unable to perform peer host name validation. Curl error has occurred for peer name: XXXXXXXX, self name: XXXXXXXX: 0
              [PROXY] Encountered error (VALIDATE_PEER_HOST_PROTOCOL_RUNNING) while processing(ValidatePeerHostProtocol).: 1
      no entity was found