We have a Master in 126.96.36.199 with a Media Server (same version) which backup a filer in Remote NDMP.
Backups are doing well but generate logs growing very much (260 Go on a full backup from 14 To) each week.
I've tried to run following commands on Master server :
vxlogcfg -a -p 51216 -o 134 -s DebugLevel=0
vxlogcfg -a -p 51216 -o 134 -s DiagnosticLevel=0
Even if I try with -g instead of -a
I've found the following technote : http://www.symantec.com/docs/TECH157017
but it doesn't resolve anything.
Does someone have an idea?
Solved! Go to Solution.
Interesting that - perhaps NDMP logging relates only to the Master Server - dont see why though off hand
The error not accepting the -a is strange unless it is not permitted on the media server (justtryied one and it did not allow logging to be setup - but different error to yours)
My other thoughts is that it needs a patch to log to (-c) or the correct license installed on the Media Server itself
Otherthan that have you tried using ndmpagent rathe than 134?
Don't know if any of this helps - just ideas that may point somewhere
Odd. NDMP logging is ok on media, might need a license, not sure.
But it's complaining about te command, not the log
v 1-8-0-5 An unknown argument -a was passed
Can you try the same command but on a different log
vxlogcfg -a -p 51216 -o 222 -s DebugLevel 0
If you do the same command for other Netbackup process, such as -o 200 (nbrmms) or others, does it work?
When running vxlog* type of command, it always check and update this file: nblog.conf
Make sure the following is in nblog.conf:
# 134. NDMP Agent
Here is the Media Server's nblog.conf file contents :
# 134. NDMP Agent
I will try with another process to check if I get the same issue.