Forum Discussion

ichi-the-one's avatar
ichi-the-one
Level 3
6 years ago

Newbie to netbackup needs help: server name not found

Hello there, I'm a newbie to netbackup. Actually we have inherited a netbackup appliance after an acquisition that my company did. We have a netbackup appliance 5420 and a VM which has the console of...
7.7
windows server 2012
  • Marianne's avatar
    Marianne
    6 years ago

    This seems to be the problem :

    SERVER = mad-nbms-01

    Do you know what this server is en where it is? 

    This 1st entry in bp.conf says that mad-nbms-01 is the master server, and 2nd entry
    SERVER = cri-nb-01
    means that cri-nb-01 is considered a 'secondary' or media server.

    The fact that EMMSERVER is defined as cri-nb-01, says to me that the Appliance is supposed to be the master.

    Oh, and this:
    NETBACKUP_APPLIANCE_MODE = MANUAL_MASTER_APPLIANCE

    Someone must've (accidently) clicked on mad-nbms-01 name in the GUI and selected 'Make Master'. 
    This would've changed the order of SERVER entries in bp.conf.
    Master server daemons will not start.

    Change 1st SERVER entry in bp.conf on the Appliance to cri-nb-01 and stop/start NBU. 

    Server and EMM entries on the Console should NOT point to itself.
    It can have itself as secondary Server entry. 

Marianne's avatar
Marianne
Level 6

ichi-the-one

You firstly need to determine the actual NetBackup role for the VM and the Appliance.

Is the Appliance master/media server or just media server? 
If nbemm, bpdbm and other master server processes are not running, chances are that the Appliance is media server only.

Is the VM maybe the master server and not only Admin Console? 
Can you check Registry entries on the VM and tell us what you see next to 'Server' under :
HKEY_LOCAL_MACHINE\SOFTWARE\VERITAS\NetBackup\CurrentVersion\Config

If you know how to get into command line on the Appliance, please check contents of /usr/openv/netbackup/bp.conf and tell us what you see at the top of the file for SERVER entries and EMMSERVER entry. 

 

ichi-the-one's avatar
ichi-the-one
Level 3
6 years ago

Hello Marianne, thank you for your time.

I'll try to answer your questions in the best way I can. I have included a simplified schema of what we have. The netbackup appliance have the role of a media server as it is indicated in the left corner of the console.I can changed it all according to your suggestion. Our objective is to have a functionning backup plateforme for our VMware plateform.

By the way, is there a way to check the roles of the appliance from command line?(just to be sure)

== > services which are not running are below

cri-nb-01 bpdbm Disabled null
cri-nb-01 nbvault Disabled null
cri-nb-01 NB_dbsrv Disabled null
cri-nb-01 bmrd Disabled null
cri-nb-01 bpinetd Disabled null
cri-nb-01 nbevtmgr Disabled null
cri-nb-01 bprd Disabled null
cri-nb-01 nbstserv Disabled null
cri-nb-01 nbkms Disabled null
cri-nb-01 nbars Disabled null
cri-nb-01 nbaudit Disabled null
cri-nb-01 nbim Disabled null
cri-nb-01 nbwmc Disabled null
cri-nb-01 nbemm Disabled null
cri-nb-01 nbjm Disabled null
cri-nb-01 nbpem Disabled null
cri-nb-01 nbrb Disabled null

>>Is the VM maybe the master server and not only Admin Console?

  I guess that since the netbackup appliance is a media server only, then the VM should be the master server. But again, if you say the best architecture is to configure both master and media server on the appliance I can do that.


>>Can you check Registry entries on the VM and tell us what you see next to 'Server' under :
>>HKEY_LOCAL_MACHINE\SOFTWARE\VERITAS\NetBackup\CurrentVersion\Config

the registry key show the following configuration:

browsersrvcry-sccm01.domain.com
client namesrvcry-sccm01.domain.com
emmserver10.216.0.16
server10.216.0.16 SRVCRY-SCCM1.domain.com

 

>>>If you know how to get into command line on the Appliance, please check contents of /usr/openv/netbackup/bp.conf >>and tell us what you see at the top of the file for SERVER entries and EMMSERVER entry. 

***content of the bp.conf

SERVER = mad-nbms-01
SERVER = cri-nb-01
SERVER = cri-nb-01.domain
SERVER = 10.216.0.16
SERVER = SRVCRY-sccm01.domain
SERVER = SRVCRY-SCCM01.domain
SERVER = mad-nbms-01.domain
SERVER = mad-nbms-01.domain
CLIENT_NAME = cri-nb-01
USE_VXSS = PROHIBITED
VXSS_SERVICE_TYPE = INTEGRITYANDCONFIDENTIALITY
EMMSERVER = cri-nb-01
VXDBMS_NB_DATA = /usr/openv/db/data
ENABLE_ROBUST_LOGGING = NO
VERBOSE = 1
PREFERRED_NETWORK = 192.168.229.0/24 MATCH 10.15.70.1
NETBACKUP_APPLIANCE_MODE = MANUAL_MASTER_APPLIANCE
IP_ADDRESS_FAMILY = AF_UNSPEC
BPCD_WHITELIST_PATH = /config/MIGRATION
JOB_PRIORITY = 0 0 90000 90000 90000 90000 85000 85000 80000 80000 80000 80000 75000 75000 70000 70000 50000 50000 45000 0 0 0 0 0
VM_PROXY_SERVER = srvgs-omtvc.domain
TELEMETRY_UPLOAD = NO
"bp.conf" [readonly] 25L, 861C

 

NB: As I said in the begnning of my request: we enherited this backup solution. So there might be wrong information in the configuration files. This is why I have shared with you guy our current architecture. We're ready to embrace your suggestions if they mean that we can have at the end a functionning backup plateforme. Please don't hesitate to share your taughts with me. I'll be very happy to read them and to learn from you all.

 

Thank you :)

  • Marianne's avatar
    Marianne
    Level 6
    6 years ago

    This seems to be the problem :

    SERVER = mad-nbms-01

    Do you know what this server is en where it is? 

    This 1st entry in bp.conf says that mad-nbms-01 is the master server, and 2nd entry
    SERVER = cri-nb-01
    means that cri-nb-01 is considered a 'secondary' or media server.

    The fact that EMMSERVER is defined as cri-nb-01, says to me that the Appliance is supposed to be the master.

    Oh, and this:
    NETBACKUP_APPLIANCE_MODE = MANUAL_MASTER_APPLIANCE

    Someone must've (accidently) clicked on mad-nbms-01 name in the GUI and selected 'Make Master'. 
    This would've changed the order of SERVER entries in bp.conf.
    Master server daemons will not start.

    Change 1st SERVER entry in bp.conf on the Appliance to cri-nb-01 and stop/start NBU. 

    Server and EMM entries on the Console should NOT point to itself.
    It can have itself as secondary Server entry. 

    • ichi-the-one's avatar
      ichi-the-one
      Level 3
      6 years ago

      Thank you Marianne for the suggestion.

       

      I did as you suggested. Actually the mad-nbms-01 has been retrieved from the console. I tried to ping it from both the console and appliance and I failed.

      the bp.conf looks like this now:

      SERVER = cri-nb-01
      SERVER = cri-nb-01.backup.omt.local
      SERVER = 10.216.0.16
      SERVER = SRVCRY-sccm01.intelcia.com
      SERVER = SRVCRY-SCCM01.intelcia.com
      CLIENT_NAME = cri-nb-01
      USE_VXSS = PROHIBITED
      VXSS_SERVICE_TYPE = INTEGRITYANDCONFIDENTIALITY
      EMMSERVER = cri-nb-01
      VXDBMS_NB_DATA = /usr/openv/db/data
      ENABLE_ROBUST_LOGGING = NO
      VERBOSE = 1
      PREFERRED_NETWORK = 192.168.229.0/24 MATCH 10.15.70.1
      NETBACKUP_APPLIANCE_MODE = MANUAL_MASTER_APPLIANCE
      IP_ADDRESS_FAMILY = AF_UNSPEC
      BPCD_WHITELIST_PATH = /config/MIGRATION
      JOB_PRIORITY = 0 0 90000 90000 90000 90000 85000 85000 80000 80000 80000 80000 75000 75000 70000 70000 50000 50000 45000 0 0 0 0 0
      VM_PROXY_SERVER = srvgs-omtvc.intelcia.com
      TELEMETRY_UPLOAD = NO
      MAX_LOGFILE_SIZE = 50
      MAX_NUM_LOGFILES = 50
      VXMS_VERBOSE = 1

       I have also changed the regestry keys as you suggested and made both the server and emmserver point to the appliance:

      browsersrvcry-sccm01.domain.com
      client namesrvcry-sccm01.domain.com
      emmserver10.216.0.180
      server10.216.0.180 cri-nb-01.domain.com

       

      I stop/start NBU services:

       

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

      NetBackup 7.7.3 -- Shutdown Utility

      Shutting down services
      > NetBackup Indexing Manager
      > NetBackup Indexing Manager -- DISABLED
      > NetBackup Service Monitor
      > NetBackup Service Monitor -- STOPPED
      > NetBackup Storage Lifecycle Manager
      > NetBackup Storage Lifecycle Manager -- DISABLED
      > NetBackup Vault Manager
      > NetBackup Vault Manager -- DISABLED
      > NetBackup Service Layer
      > NetBackup Service Layer -- STOPPED
      > NetBackup Policy Execution Manager
      > NetBackup Policy Execution Manager -- DISABLED
      > NetBackup Job Manager
      > NetBackup Job Manager -- DISABLED
      > NetBackup Request Daemon
      > NetBackup Request Daemon -- STOPPED
      > NetBackup Compatibility Service
      > NetBackup Compatibility Service -- DISABLED
      > 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 Event Manager
      > NetBackup Event Manager -- DISABLED
      > 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 -- DISABLED
      > 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

      Shutdown completed successfully.

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

      NetBackup 7.7.3 -- 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 -- DISABLED
      > NetBackup Discovery Framework
      > NetBackup Discovery Framework -- STARTED
      > NetBackup Deduplication Multi-Threaded Agent
      > NetBackup Deduplication Multi-Threaded Agent -- STARTED
      > NetBackup Event Manager
      > NetBackup Event Manager -- DISABLED
      > 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 Compatibility Service
      > NetBackup Compatibility Service -- DISABLED
      > NetBackup Request Daemon
      > NetBackup Request Daemon -- NOT STARTED
      > NetBackup Job Manager
      > NetBackup Job Manager -- DISABLED
      > NetBackup Policy Execution Manager
      > NetBackup Policy Execution Manager -- DISABLED
      > NetBackup Service Layer
      > NetBackup Service Layer -- STARTED
      > NetBackup Vault Manager
      > NetBackup Vault Manager -- DISABLED
      > NetBackup Storage Lifecycle Manager
      > NetBackup Storage Lifecycle Manager -- DISABLED
      > NetBackup Service Monitor
      > NetBackup Service Monitor -- STARTED
      > NetBackup Indexing Manager
      > NetBackup Indexing Manager -- DISABLED
      Start up of one or more services failed.

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

       

       

      After doing this, I made some progress actually. Since I can see now the lists of the previous jobs which i couldn't see before.

      Yet, when I try to go to server groups under devices so to add the vmware server It fails. the error server name not found in the netbackup configuration(254).

      Any hints plz?

      Thank you a thousand.

       

      • ichi-the-one's avatar
        ichi-the-one
        Level 3
        6 years ago

        I would like to add also, that in the left corner of the console. I can see that the appliance has been defined as master server now. NBEMM service is still down. 

        I took a deeper look at the console. and under host properties I found master server pointing to my appliance and marked as check.

        under media servers I have selected the appliance.

        when I double click on Master server I have a new windows in which I have selected vmware access hosts and added my vcenter server. What can I do next please? In order to configure backup for my VMs