Forum Discussion

baba20009's avatar
baba20009
Level 4
12 years ago

how to stop netbackup log creation

I open a case with Symantec netbackup on 10/18/12 to troubleshoot renaming medias.  The tech enabled logging not sure where. 

Now there is a daily 4 files of 51,200KB under \Veritas\netbackup\logs folder. 

Can you tell me where to disable this logging?  We are using netbackup 6.5.6

 

Thank you

7 Replies

  • Thanks Martin.

    I ran the comand shwowing "The configuration settings were added successfully". 

    I will check tomorrow morning hopefully no log will be there.

    Do you see any problem with me deleting current logs in above location?

     

    Thanks

     

  • Depends if the files are open ..  If they are then deleting them will not release the disk space - safer to stop NBU, delete them and restart.

    You should not be so low on disk space that these files are an issue - thesystem should be designed to have a 'generous' amount of space for logs.  If log levels need to be turned up and cannot, due to disk space, it can be impossible to fix issues.

    Martin

  • On Monday i was able to manually delete all the log files.

    Today i still see there is a daily 4 files of 51,200KB under \Veritas\netbackup\logs folder for last three days.

    Apparently the command did not make any change!

    Any Ideas?

     

    Thanks

  • i even set command to 0 and 0 and how come it is still not working?

     

  • I think some logs are on by default, can't be turned off completely.

    If you look in .../netbackup folder, there is a file nblog.conf

    Look in this (do NOT manually edit) and you will see the section for each oid number

     

    # 111. Enterprise Media Manager
    111.L10nResource=nbemm
    111.OIDNames=nbemm
    111.LogDirectory=nbemm
    111.DebugLevel=0
    111.DiagnosticLevel=0
    111.AppMsgLogging=ON
     
    You can see the settings.
     
    As you can see, I set the EMM log (111) to 0 and 0 
     
    I looked in the EMM log, and I still have lines being added, for example
     
    11/08/12 21:30:47.307 [Debug] NB 51216 mds 143 PID:27317 TID:12 File ID:111 [No context] 1 [getUnloadDrivesList] EXIT STATUS = 0 (EMM_ERROR_Success, Success)
     
    We see that this line is 'File ID: 111' so it is the EMM log, but the 'process' is 143 (which is mds), so even with EMM at 0/0 the mds lines are still added.  Looking at the 143 bit of nblog.conf I see it has never been changed:
     
    # 143. EMM Media and Device Selection
    143.L10nResource=mds
    143.OIDNames=mds
     
    So it is at default values.
     
    So yes, some logging is on by default.  I am not sure if it is even possible to turn it all off completely, you could try setting debug/ diag to 0 for everything.
     
    I am not sure why a small amount of logging is an issue - the system should have been  designed to cope with this.
     
    martin
     
     
     
     
     
     
     
     
     
     
  •  

    my nblog.conf file show below:

    I did ran the 0 and 0 this morning but nothing got changed.

    My E: drive where netbackup database is shows

    57 GB total 17 GB free

    last week it had 1.5 GB free due to 10 days worth of logs!!

    this was not like this two weeks ago before i open a support ticket with Symantec netbackup.

    i guess i could call and open another ticket.  i thought it would be easy to fix this here.

     

    Thanks Martin for responding.

    *************

    #$Id: nblog.conf.nt,v 1.45 2005/08/04 21:11:56 $
    #$VRTScprght: Copyright 1993 - 2005 VERITAS Software Corporation, All Rights Reserved $
    #PLEASE DO NOT EDIT THIS FILE MANUALLY. USE COMMAND LINE INTERFACE
    #vxlogcfg INSTEAD.
    #Please do not edit the L10nResource related settings.

    Default.LogDirectory=E:\PROGRA~1\VERITAS\NetBackup\logs
    Default.DebugLevel=1
    Default.DiagnosticLevel=1
    Default.LogToStdout=false
    Default.LogToStderr=false
    Default.LogToOslog=false
    Default.L10nLib=E:\Program Files\VERITAS\NetBackup\bin\vxextwincat_1.dll
    Default.L10nResourceDir=E:\PROGRA~1\VERITAS\NetBackup\resources
    Default.RolloverMode=FileSize
    Default.RolloverAtLocalTime=00.00
    Default.NumberOfLogFiles=3
    Default.MaxLogFileSizeKB=51200
    Default.LogFilePermissions=664
    Default.SyslogIdent=VRTS-NB
    Default.SyslogOpt=0
    Default.SyslogFacility=LOG_LOCAL5


    #Message catalogs
    #Services
    102.L10nResource=nbwrg
    102.NtEventLogSourceName=nbwrg
    102.OIDNames=nbwrg

    111.L10nResource=emm
    111.NtEventLogSourceName=emm
    111.OIDNames=nbemm
    111.DebugLevel=1
    111.DiagnosticLevel=1

    113.L10nResource=nbcim
    113.NtEventLogSourceName=nbcim
    113.OIDNames=nbcim

    116.L10nResource=nbpem
    116.NtEventLogSourceName=nbpem
    116.OIDNames=nbpem

    117.L10nResource=nbjm
    117.NtEventLogSourceName=nbjm
    117.OIDNames=nbjm

    118.L10nResource=nbrb
    118.NtEventLogSourceName=nbrb
    118.OIDNames=nbrb

    119.L10nResource=bmrd
    119.NtEventLogSourceName=bmrd
    119.OIDNames=bmrd,bmrbd

    121.L10nResource=bmrsavecfg
    121.NtEventLogSourceName=bmrsavecfg
    121.OIDNames=bmrsavecfg

    122.L10nResource=bmrc
    122.NtEventLogSourceName=bmrc
    122.OIDNames=bmrc

    123.L10nResource=bmrs
    123.NtEventLogSourceName=bmrs
    123.OIDNames=bmrs

    124.L10nResource=bmrmedia
    124.NtEventLogSourceName=bmrmedia
    124.OIDNames=bmrcreatefloppy

    125.L10nResource=bmrsrt
    125.NtEventLogSourceName=bmrsrt
    125.OIDNames=bmrsrtadm

    126.L10nResource=bmrprep
    126.NtEventLogSourceName=bmrprep
    126.OIDNames=bmrprep

    127.L10nResource=bmrsetup
    127.NtEventLogSourceName=bmrsetup
    127.OIDNames=bmrsetupmaster,bmrsetupboot

    128.L10nResource=bmrcommon
    128.NtEventLogSourceName=bmrcommon
    128.OIDNames=bmrcommon,bmrlibs,bmrmisc             

    129.L10nResource=bmrconfig
    129.NtEventLogSourceName=bmrconfig
    129.OIDNames=bmrconfig

    130.L10nResource=bmrpkg
    130.NtEventLogSourceName=bmrpkg
    130.OIDNames=bmrcreatepkg

    131.L10nResource=bmrrestore
    131.NtEventLogSourceName=bmrrestore
    131.OIDNames=bmrrestore

    132.L10nResource=nbsl
    132.NtEventLogSourceName=nbsl
    132.OIDNames=nbsl

    134.L10nResource=ndmpagent
    134.NtEventLogSourceName=ndmpagent
    134.OIDNames=ndmpagent

    137.L10nResource=libraries
    137.NtEventLogSourceName=libraries

    140.L10nResource=mmui
    140.NtEventLogSourceName=mmui
    140.OIDNames=mmui

    142.L10nResource=bmrepadm
    142.NtEventLogSourceName=bmrepadm
    142.OIDNames=bmrepadm

    143.L10nResource=emm
    143.DebugLevel=2
    143.NtEventLogSourceName=emm
    143.OIDNames=mds

    144.L10nResource=emm
    144.NtEventLogSourceName=da
    144.OIDNames=da

    151.L10nResource=ndmp
    151.NtEventLogSourceName=ndmp
    151.OIDNames=ndmp

    153.L10nResource=nbgenjob
    153.NtEventLogSourceName=nbgenjob
    153.OIDNames=nbgenjob

    154.L10nResource=bmrovradm
    154.NtEventLogSourceName=bmrovradm
    154.OIDNames=bmrovradm

    #TAO debug level
    156.DebugLevel=0

    157.L10nResource=nbnos
    157.NtEventLogSourceName=nbnos
    157.OIDNames=nbnos

    163.L10nResource=nbsvcmon
    163.NtEventLogSourceName=nbsvcmon
    163.OIDNames=nbsvcmon

    166.L10nResource=nbvault
    166.NtEventLogSourceName=nbvault
    166.OIDNames=nbvault
    178.L10nResource=dsm
    178.NtEventLogSourceName=dsm
    178.OIDNames=dsm
    199.L10nResource=ftservices
    199.NtEventLogSourceName=FATServer
    199.OIDNames=FATServer
    200.L10nResource=ftservices
    200.NtEventLogSourceName=FATClient
    200.OIDNames=FATClient
    201.L10nResource=ftservices
    201.NtEventLogSourceName=FSM
    201.OIDNames=FSM
    219.L10nResource=rsrcevtmgr
    219.NtEventLogSourceName=emm
    219.OIDNames=rem
    220.L10nResource=dps
    220.NtEventLogSourceName=dps
    220.OIDNames=dps
    221.L10nResource=nbrmms
    221.NtEventLogSourceName=nbrmms
    221.OIDNames=mpms
    222.L10nResource=nbrmms
    222.NtEventLogSourceName=nbrmms
    222.OIDNames=nbrmms
    226.L10nResource=nbstserv
    226.NtEventLogSourceName=nbstserv
    226.OIDNames=nbstserv
    230.L10nResource=rdsm
    230.NtEventLogSourceName=rdsm
    230.OIDNames=rdsm
    231.L10nResource=nbevtmgr
    231.NtEventLogSourceName=nbevtmgr
    231.OIDNames=nbevtmgr
    248.L10nResource=bmrlaunch
    248.NtEventLogSourceName=bmrlaunch
    248.OIDNames=bmrlaunch
    254.L10nResource=SPSV2RecoveryAsst
    254.NtEventLogSourceName=SPSV2RecoveryAsst
    254.OIDNames=SPSV2RecoveryAsst
    261.L10nResource=aggs
    261.OIDNames=aggs
    263.OIDNames=wingui
    271.L10nResource=nbecmsg
    271.OIDNames=nbecmsg
    272.L10nResource=expmgr
    272.NtEventLogSourceName=expmgr
    272.OIDNames=expmgr
    286.L10nResource=nbkms
    286.NtEventLogSourceName=nbkms
    286.OIDNames=nbkms