Solved
Question regarding logging levels
Hi guys,
I took a look at the logging levels in the admin guide, but I couldn't find what's included on each logging level for a client.
I have a client that behaves erratically when backing up the DFSR folders. It works just fine most of the time, but once every now and then it decides to skip them (job finishes successfully but it backs up 2 files and 0KB) or take a full backup even if it's actually run as CINC.
I want to gather a bit more info about this because it's very weird. The problem is that I barely have space on my drives, and last time I enabled logs for this server, they grew to 1-3GB per day as it is a file server with tons of files
I know there is a command to change the location of the logs, but I already have too much on my plate and was wondering if maybe logging level 1 or 2 would suffice to point me in the right direction of troubleshooting.
Thanks
Level 3 should/may show you enough.
You might have to invest in re-directing logs.
.
Here's some notes:
.
NetBackup Logs Re-Direction =========================== Tested using: NetBackup Server v7.7 ...on: Windows Server 2012 R2 Related Tech Notes ================== DOCUMENTATION: How to manually change the path where NetBackup log files are located: https://support.symantec.com/en_US/article.TECH15567.html aka: http://www.veritas.com/docs/000011402 Default Locations ================= Default Location Used By Type ---------------- ------- ---- C:\Program Files (x86)\VERITAS\VxPBX\log\ For VxPBX only, aka product: 50936 VxUL C:\Program Files\Veritas\NetBackup\logs\ For NetBackup Server logs VxUL and classic C:\Program Files\Veritas\NetBackup\logs\user_ops\nbjlogs\ NetBackup Java Admin Console classic C:\Program Files\Veritas\NetBackupDB\log\ server.log for Sybase ASA classic C:\Program Files\Veritas\pdde\log\ MSDP (i.e. PureDisk) classic C:\Program Files\Veritas\Volmgr\debug\ For NetBackup Volume Manager logs classic A Handy Command To List Current Log Locations (does not show if symlinks are in place) ====================================================================================== nbcplogs --list-products Where Are Locations Specified ============================= Area Location Manipulated ---- -------------------- VxPBX logs "C:\Program Files (x86)\VERITAS\VxPBX\bin\vxlogcfg.exe" NetBackup classic logs Registry key: HKLM\Software\Veritas\NetBackup\CurrentVersion /v "Log Directory" NetBackup VxUL logs "C:\Program Files\Veritas\NetBackup\bin\vxlogcfg.cmd" Volume Manager logs (by hand - as there is no pointer) Java Admin Console logs "C:\Program Files\Veritas\NetBackup\Java\setconf.bat" see: set logFile= Sybase server log "C:\Program Files\Veritas\NetBackupDB\CONF\server.conf" In This Example - Redirected Logging ==================================== In the examples below: - NetBackup was already installed on D: - And we are going to re-direct all major logging to the following folders: F:\NBU_LOGS\msdp for MSDP Deduplication Engine (spoold) and Manager (spad) F:\NBU_LOGS\netbackup for NetBackup traditional logs and VxUL logs F:\NBU_LOGS\netbackupdb for the Sybase ASA server.log file F:\NBU_LOGS\pdde for the PDDE logs F:\NBU_LOGS\volmgr for the Volume Manager "debug" logs F:\NBU_LOGS\vxpbx for Veritas PBX unified logs The reason we don't have a sub-folder named '\logs' is because such a name would not convey the source of the logs... ...i.e. which component of NetBackup the logs are from. NetBackup Classic Logging ========================= Capture Current Defaults ------------------------ > reg query "HKLM\Software\Veritas\NetBackup\CurrentVersion" /v "Log Directory" HKEY_LOCAL_MACHINE\Software\Veritas\NetBackup\CurrentVersion Log Directory REG_SZ D:\Program Files\Veritas\\NetBackup\logs > reg query "HKLM\Software\Veritas\NetBackup\CurrentVersion\Paths" /v "BP_LOGS" ERROR: The system was unable to find the specified registry key or value. ...list the installed products: > "D:\Program Files\Veritas\NetBackup\bin\vxlogcfg.cmd" -l > "C:\Program Files (x86)\VERITAS\VxPBX\bin\vxlogcfg.exe" -l -p 50936 -o 103 | find /i "LogDirectory" LogDirectory = C:\Program Files (x86)\VERITAS\VxPBX\log\ > "D:\Program Files\Veritas\NetBackup\bin\vxlogcfg.cmd" -l -p 51216 -o Default | find /i "LogDirectory" LogDirectory = D:\Program Files\Veritas\NetBackup\logs\ > find /i "LogFile=" "D:\Program Files\Veritas\NetBackup\Java\setconf.bat" ---------- D:\PROGRAM FILES\VERITAS\NETBACKUP\JAVA\SETCONF.BAT set logFile=%NB_INSTALL_PATH%\logs\user_ops\nbjlogs\%nbjLogFileName% > find /i "-o" "D:\Program Files\Veritas\NetBackupDB\CONF\server.conf" ---------- D:\PROGRAM FILES\VERITAS\NETBACKUPDB\CONF\SERVER.CONF -o "D:\Program Files\Veritas\NetBackupDB\log\server.log" -os 1M -ti 0 -wc- -x tcpip(LocalOnly=YES;ServerPort=13785) > dir "D:\Program Files\Veritas\Volmgr" ...the default is that the \debug sub-folder does not exist, but we may create that later... > reg query "HKLM\Software\Symantec" /s | find /i "log" > reg query "HKLM\Software\Veritas" /s | find /i "log" Now Make Changes ---------------- ...N.B: The two different sets of VxUL logs, i.e. VxPBX and NetBackup, are manipulated using different commands !! ...firstly, stop all NetBackup processes: > bpps > bpdown -f -v > bpps > net stop "NetBackup BMR PXE Service" > net stop "NetBackup BMR MTFTP Service" > net stop "Symantec Private Branch Exchange" > bpps -i ALL_PROCESSES | SORT > net start | findstr /i "netbackup symantec veritas" The Section Makes Changes ========================= ...first, create a target top logging folder: > mkdir F:\NBU_LOGS ...the Java admin console requires this registry value to exist: > reg add "HKLM\Software\Veritas\NetBackup\CurrentVersion\Paths" /v "BP_LOGS" /t REG_SZ /d "F:${_ps}NBU_LOGS${_ps}netbackup${_ps}" The operation completed successfully. ...now amend NetBackup VxUL Unified Logging: > "C:\Program Files (x86)\VERITAS\VxPBX\bin\vxlogcfg.exe" -a -p 50936 -o 103 -s LogDirectory="F:\NBU_LOGS\vxpbx" The configuration settings were added successfully. > "D:\Program Files\Veritas\NetBackup\bin\vxlogcfg.cmd" -a -p 51216 -o Default -s LogDirectory="F:\NBU_LOGS\netbackup" The configuration settings were added successfully. ...now check to make sure that no OIDs have been specifically set to log elsewhere: > for /f "tokens=1" %a in ('vxlogcfg -l -p 51216') do (vxlogcfg -p 51216 -o %a -l | find /i "LogDirectory") | find /i /v "F:\NBU_LOGS" ...if any LogDirectory entries are seen, then they will need to be individually adjusted... ...now re-direct the NetBackup Java log file location... > notepad "D:\Program Files\Veritas\NetBackup\Java\setconf.bat" ...search for the line beginning with: set logFile= ...and change the whole line to: set logFile=F:\NBU_LOGS\netbackup\user_ops\nbjlogs\%nbjLogFileName% ...save and close... ...now re-direct the NetBackup Sybase ASA service log file... > notepad "D:\Program Files\Veritas\NetBackupDB\CONF\server.conf" ...search for the text beginning with: -o ...and change the log file name to: -o "F:\NBU_LOGS\netbackupdb\server.log" ...now move and symlink the existing legacy and unified log folders and files: > mkdir "F:\NBU_LOGS\netbackup\" > xcopy /s /e /h "D:\Program Files\Veritas\NetBackup\logs\*.*" "F:\NBU_LOGS\netbackup\" > rmdir /s "D:\Program Files\Veritas\NetBackup\logs\" > mklink /d "D:\Program Files\Veritas\NetBackup\logs" "F:\NBU_LOGS\netbackup" ...now move and symlink the Veritas PBX log folder: > mkdir "F:\NBU_LOGS\vxpbx\" > xcopy /s /e /h "C:\Program Files (x86)\VERITAS\VxPBX\log\*.*" "F:\NBU_LOGS\vxpbx\" > rmdir /s "C:\Program Files (x86)\VERITAS\VxPBX\log\" > mklink /d "C:\Program Files (x86)\VERITAS\VxPBX\log" "F:\NBU_LOGS\vxpbx" ...now move and symlink the database server log folder and files: > mkdir "F:\NBU_LOGS\netbackupdb\" > xcopy /s /e /h "D:\Program Files\Veritas\NetBackupDB\log\*.*" "F:\NBU_LOGS\netbackupdb\" > rmdir /s "D:\Program Files\Veritas\NetBackupDB\log\" > mklink /d "D:\Program Files\Veritas\NetBackupDB\log" "F:\NBU_LOGS\netbackupdb" ...now move and symlink the PDDE log folders and files: > mkdir "F:\NBU_LOGS\pdde\" > xcopy /s /e /h "D:\Program Files\Veritas\pdde\log\*.*" "F:\NBU_LOGS\pdde\" > rmdir /s "D:\Program Files\Veritas\pdde\log\" > mklink /d "D:\Program Files\Veritas\pdde\log" "F:\NBU_LOGS\pdde" ...now move and symlink the MSDP log folders and files: > mkdir "F:\NBU_LOGS\msdp\" > xcopy /s /e /h "H:\MSDP_data\log\*.*" "F:\NBU_LOGS\msdp\" > rmdir /s "H:\MSDP_data\log\" > mklink /d "H:\MSDP_data\log" "F:\NBU_LOGS\msdp" ...IF the Volume Manager "debug" log folder already exists then... > mkdir "F:\NBU_LOGS\volmgr\" > xcopy /s /e /h "D:\Program Files\Volmgr\debug\*.*" "F:\NBU_LOGS\volmgr\" > rmdir /s "D:\Program Files\Volmgr\debug\" > mklink /d "D:\Program Files\Volmgr\debug" "F:\NBU_LOGS\volmgr" ...IF the Volume Manager logs do NOT already exists... then now symlink and create the Volume Manager logs: > mkdir "F:\NBU_LOGS\volmgr" > mklink /d "D:\Program Files\Veritas\Volmgr\debug" "F:\NBU_LOGS\volmgr" > mkdir "D:\Program Files\Veritas\Volmgr\debug\acsd" > mkdir "D:\Program Files\Veritas\Volmgr\debug\acssi" > mkdir "D:\Program Files\Veritas\Volmgr\debug\daemon" > mkdir "D:\Program Files\Veritas\Volmgr\debug\ltid" > mkdir "D:\Program Files\Veritas\Volmgr\debug\oprd" > mkdir "D:\Program Files\Veritas\Volmgr\debug\reqlib" > mkdir "D:\Program Files\Veritas\Volmgr\debug\robots" > mkdir "D:\Program Files\Veritas\Volmgr\debug\tpcommand" > mkdir "D:\Program Files\Veritas\Volmgr\debug\vmscd" > copy nul "D:\Program Files\Veritas\Volmgr\database\DEBUG" > copy nul "D:\Program Files\Veritas\Volmgr\AVRD_DEBUG" > copy nul "D:\Program Files\Veritas\Volmgr\DRIVE_DEBUG" > copy nul "D:\Program Files\Veritas\Volmgr\NDMP_DEBUG" > copy nul "D:\Program Files\Veritas\Volmgr\ROBOT_DEBUG" > copy nul "D:\Program Files\Veritas\Volmgr\SOCKET_DEBUG" > copy nul "D:\Program Files\Veritas\Volmgr\SSO_DEBUG" > copy nul "D:\Program Files\Veritas\Volmgr\TLD_RS232_DEBUG" > copy nul "D:\Program Files\Veritas\Volmgr\VM_MQ_DEBUG" > dir "D:\Program Files\Veritas\Volmgr\*_DEBUG" > dir "D:\Program Files\Veritas\Volmgr\debug" ...check to see whether VERBOSE logging is already enabled for Volume Manager... ...and enabled/add if desired: > type "D:\Program Files\Veritas\Volmgr\vm.conf" > (echo VERBOSE) >>"D:\Program Files\Veritas\Volmgr\vm.conf" > (echo DAYS_TO_KEEP_LOGS=10) >>"D:\Program Files\Veritas\Volmgr\vm.conf" > type "D:\Program Files\Veritas\Volmgr\vm.conf" ...now list the log folder tree: > dir /s /b "F:\NBU_LOGS" > reg query "HKLM\Software\Symantec" /s | find /i "log" > reg query "HKLM\Software\Veritas" /s | find /i "log" # to completely clean out logs folder: del /s "F:\NBU_LOGS\*.j" del /s "F:\NBU_LOGS\*.log" del /s "F:\NBU_LOGS\*.slg" del /s "F:\NBU_LOGS\*.tmp" del /s "F:\NBU_LOGS\*.xml" del /s "F:\NBU_LOGS\*.1" del /s "F:\NBU_LOGS\*.pcb_std" dir /s /b "F:\NBU_LOGS" | find "." ...now restart NetBackup... > bpps -i ALL_PROCESSES | SORT > net start | findstr /i "netbackup symantec veritas" > net start "Symantec Private Branch Exchange" > net start "NetBackup BMR MTFTP Service" > net start "NetBackup BMR PXE Service" > bpup -f -v > bpps -i ALL_PROCESSES | SORT > net start | findstr /i "netbackup symantec veritas" How to Search Drives for SymLinks ================================= > for /f "tokens=1,2 skip=1" %a in ('wmic logicaldisk list brief') do (if %b==3 dir /s /a:l "%a\Program Files (x86)") > for /f "tokens=1,2 skip=1" %a in ('wmic logicaldisk list brief') do (if %b==3 dir /s /a:l "%a\Program Files") ...but the above won't find the symlinked MSDP data log folder... ...but if one searches all folders on all drives using the DIR /A:L switch, then all the Window OS junction points will also be found. [end]
