Forum Discussion

nasahasha's avatar
nasahasha
Level 5
10 years ago

Unified logs on client server

Netbackup 7.6.0.3 (Master, media and client)

OS:Linux (Master, media and client)

I have enabled resilient network on one of clients and its creating unified "nbrntd" logs, I can disable it by set logging to zero on media and master server, but how to do it on client?

also

On client I see few unified logs getting created, starting with 51216-112, I checked in nblog.conf, I didnt find any name associated with ID 112. will by default any unified logs get created on clients?

I need to know how to manage unified logging on clients.

7.6
Backing Up
Backup and Recovery
Basics
Best Practice
Linux
NetBackup
  • inn_kam's avatar
    inn_kam
    10 years ago

    Hello,

    NBTNTD is a part of unified logging . You can change the debug level of this by going the Tech note at :

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

    The OID for NBRNTD is 387 product ID will be 51216 only

    I quote:

    "The vx  logs are created in the /usr/openv/logs directory by default, they have the following format, the first and second fields representing the -p and -o options used in the vx... commands.

    51216-111-2201603439-080923-0000000000.log

    To enable these logs, set the DebugLevel and DiagnosticLevel using the vxlogcfg command:

    For example, to increase the 111 verbose level,

    vxlogcfg -a -p 51216 -o 387 -s DebugLevel=1 -s DiagnosticLevel=6

    The setting change can be confirmed with the following command:

    vxlogcfg -l -p 51216 -o 111

    The default logging levels for vx logs are as follows: DebugLevel = 1  DiagnosticLevel = 6"

     


    https://www-secure.symantec.com/connect/forums/how-disable-nbrntd-logs

  • inn_kam's avatar
    inn_kam
    Level 6
    10 years ago

    DOCUMENTATION: How to configure Veritas NetBackup (tm) to write Unified and Legacy log files to a different directory

    Article:TECH45907  |  Created: 2006-01-11  |  Updated: 2013-05-29  | 

    Article URL http://www.symantec.com/docs/TECH45907

     

    for debugging purposes so as not to fill your filesystem with large log files.

    However, with the advent of unified logging from NB6.0 there are only a few processes that still utilise legacy logging:

    DOCUMENTATION: A comprehensive list of NetBackup (tm) 6.0 directories and commands relating to Unified Logging. 
    http://seer.entsupport.symantec.com/docs/278572.htm
    "...
    A listing of daemons that use Legacy logging include, but are not limited to:

    • NetBackup Master Server daemons (bprd, bpdbm, bpjobd, bpdbjobs, admin)
    • NetBackup Media Server daemons (bpbrm, bptm, bpdm)
    • NetBackup Robotic daemons (vmd, avrd, ltid and robotic daemons)
    • NetBackup Client daemons (bpcd, bpbkar, tar)

    ..."

    Also of interest may be:
    DOCUMENTATION: Best Practice recommendations for enabling and gathering NetBackup (tm) logging 
    http://seer.entsupport.symantec.com/docs/282865.htm

    & this is how it used to be before unified logging:
    DOCUMENTATION: A comprehensive list of VERITAS NetBackup (tm) 3.4, 4.5, 5.x directories, touch files, and commands relating to logging 
    http://seer.entsupport.symantec.com/docs/243778.htm

    As far as mklogdir is concerned this only seems to appear (for us anyway) on our Windows clients (bat file) & Solaris Master/Media (shell script) - it does not appear on any of our Solaris or Linux clients - not sure if there is a valid reason for this "discrimination" or not!

    Regards Andy

    taking from https://www-secure.symantec.com/connect/forums/how-activate-logs-client

     

  • inn_kam's avatar
    inn_kam
    Level 6
    10 years ago

    Quick Guide to Setting up logs in NetBackup

    https://www-secure.symantec.com/connect/articles/quick-guide-setting-logs-netbackup

  • nasahasha's avatar
    nasahasha
    Level 5
    10 years ago

    On all these technotes I dont see anything about managing unified logging on client, I didnt create any directory, Enabled resilent network and "nbrntd" directory got created itself on /usr/openv/logs and started logging. I want this to be stopped on client.

  • inn_kam's avatar
    inn_kam
    Level 6
    10 years ago

    Hello,

    NBTNTD is a part of unified logging . You can change the debug level of this by going the Tech note at :

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

    The OID for NBRNTD is 387 product ID will be 51216 only

    I quote:

    "The vx  logs are created in the /usr/openv/logs directory by default, they have the following format, the first and second fields representing the -p and -o options used in the vx... commands.

    51216-111-2201603439-080923-0000000000.log

    To enable these logs, set the DebugLevel and DiagnosticLevel using the vxlogcfg command:

    For example, to increase the 111 verbose level,

    vxlogcfg -a -p 51216 -o 387 -s DebugLevel=1 -s DiagnosticLevel=6

    The setting change can be confirmed with the following command:

    vxlogcfg -l -p 51216 -o 111

    The default logging levels for vx logs are as follows: DebugLevel = 1  DiagnosticLevel = 6"

     


    https://www-secure.symantec.com/connect/forums/how-disable-nbrntd-logs