04-02-2016 10:39 PM
04-04-2016 01:02 AM
I assume you already checked the logging level from the host properties from NetBackup console, if yes then check using the below command :
vxlogcfg -p 51216 -o Default -l > to print the config
It should show you debug level at 1 and diagnostic level at 0 if not then you need to change using below command:
vxlogcfg -a -p 51216 -o Default -s DebugLevel=1 -s DiagnosticLevel=0
Let me know how it goes.
04-04-2016 10:25 AM
# To reset all logging levels for vxlog on the master
vxlogcfg -a -p 51216 -o ALL -s DebugLevel=0 -s DiagnosticLevel=0
04-04-2016 02:16 PM
Yet one of the clients logs keeps filling up.
NetBackup Management > Host Properties > Clients > (select client) > Properties > Logging
also under Windows Client > Client Settings > Additional Logging Levels
04-13-2016 01:37 AM
Hi Mujtaba,
The print showed DiagnosticLevel at 6.
I changed it to 0. Will check and confirm if it works out.
Regards.
04-13-2016 02:31 AM
DiagnosticLevel SHOULD be 6 - that is default.
DebugLevel should be 1 - that is default.
04-21-2016 06:53 AM
Hi Mujtaba,
Your solution did not work as the logs are still filling up. I have multiple huge files in bpbkar folder. For now I have deleted this folder to check how it goes.
Regards.
04-21-2016 07:30 AM
bpbkar is not a unified log, so is unaffected by the vxlogcfg commands.
The verbose level is controlled by a VERBOSE setting in either bp.conf (unix) or registry (windows)
04-21-2016 08:43 PM
Hi AAK,
I am guessing this is a Windows client - if so:
This controls the Registry setting Martin is referring to. The location in the Registry that this setting modifies is:
Hope this helps,
Steve