Logging on Media server

[Learning_Everyd]

NBU Master = Win 2008 R2 Enterprise, NBU 7.1.0.3

NBU Media = same as above

The ndmpagent on a media server keeps filling up.  Everwhere I check for logging with this logfile it's set to global 0.  Looking for a CMD to show me what the logging levels are for a system.

Thanks

[Marianne · Accepted solution]

Use vxlogcfg to reduce all logging to 0. It will not really disable logging, just turn it down to minimum.

It can be turned up 'un the fly' if needed for troubleshooting.

vxlogcfg -a -p 51216 -o Default -s DebugLevel=0 -s DiagnosticLevel=0

I have attached a Unified Logging Reference Card for NBU 6.x.
The principals remain the same.

[Learning_Everyd]

Marianne thanks for the CMD, but is there one just to view what the logs for that system are currently set at?

[revarooo]

Learning Everyday, for unified logs you can check in the netbackup/nblog.conf file. Please note, you should NEVER Edit this file manually.

If you want to view one specific oid, for example, NDMP you can use this command:

vxlogcfg -l -o 134 -p NB

[Marianne]

In addition to revaroo's suggestion, you can also check global logging level with vxlogcfg.

Extract from the doc that I've posted above:

After setting these options run
vxlogcfg -p 51216 -o Default -l
to verify the change is in place. No process restart is needed for changes to Unified Logging to take affect.

Or specific originator id (as per revaroo's suggestion) - list can be found in doc.

[Nicolai]

Adittion to both Revaroo & Marianne posts:

DOCUMENTATION: How to manage logs using robust logging via the command line

http://www.symantec.com/docs/TECH125990

[Learning_Everyd]

UPDATE -

Noticed logging is still active on this media server, but can't see why.  See vxlogcfg -a -p 51216 -o Default -l results:

C:\Program Files\Veritas\NetBackup\bin>vxlogcfg -a -p 51216 -o Default -s Debug
The configuration settings were added successfully.

C:\Program Files\Veritas\NetBackup\bin>vxlogcfg -a -p 51216 -o Default -l
Configuration settings for originator 112, of product 51,216...
LogDirectory = C:\Program Files\Veritas\NetBackup\logs\
DebugLevel = 0
DiagnosticLevel = 0
DynaReloadInSec = 0
LogToStdout = False
LogToStderr = False
LogToOslog = False
RolloverMode = FileSize | LocalTime
LogRecycle = False
MaxLogFileSizeKB = 51200
RolloverPeriodInSeconds = 43200
RolloverAtLocalTime = 0:00
NumberOfLogFiles = 3
OIDNames =
AppMsgLogging = ON
L10nLib = C:\Program Files\Veritas\NetBackup\bin\vxextwincat
L10nResourceDir = C:\Program Files\Veritas\NetBackup\resources
NtEventLogSourceName = Application
NtEventLogCategory = 0
LogFileSDDL = (null)

C:\Program Files\Veritas\NetBackup\bin>dir /p
 Volume in drive C has no label.
 Volume Serial Number is CA6C-45B0

From console the master and media server are also set to global = 0

Any idea what would cause this to still be active?

[mph999]

Following the above excellent posts, a detailed TN on logs

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

Martin

[Learning_Everyd]

C:\Program Files\Veritas\NetBackup\bin>vxlogcfg -l -o 134 -p NB
Configuration settings for originator 134, of product 51,216...
LogDirectory = C:\Program Files\Veritas\NetBackup\logs\ndmpagent\
DebugLevel = 1
DiagnosticLevel = 1
DynaReloadInSec = 0
LogToStdout = False
LogToStderr = False
LogToOslog = False
RolloverMode = FileSize | LocalTime
LogRecycle = False
MaxLogFileSizeKB = 51200
RolloverPeriodInSeconds = 43200
RolloverAtLocalTime = 0:00
NumberOfLogFiles = 3
OIDNames = ndmpagent
AppMsgLogging = ON
L10nLib = C:\Program Files\Veritas\NetBackup\bin\vxextwincat
L10nResource = ndmpagent
L10nResourceDir = C:\Program Files\Veritas\NetBackup\resources
NtEventLogSourceName = ndmpagent
NtEventLogCategory = 0
LogFileSDDL = (null)

I see Debug and Diagnostic are set to =1 even after setting all logging to =0.  Should vxlogcfg to set logging be done on the Master and Media?  I only ran it on the Media in question.