cancel
Showing results for 
Search instead for 
Did you mean: 

Log Files on the Master

Learning_Everyd
Level 5

Master = WIN2003 ENT. w/SP2, NBU 6.5.6

Three questions:

1. In the Netbackup\logs directory I am seeing a large amount of log files being written.  If turned on were these logs not to be directed to a specific logfile directory and not write to the root of the "logs" folder?

2. How can I track down where these are being written from?

3. Some I can not delete, "It is being used by another program."  These are on much older log files which should not be used by NBU.

LE

1 ACCEPTED SOLUTION

Accepted Solutions

MKT
Level 5
Employee Accredited

51216-xxx logs are VxUL logs.  51216 is the NetBackup product and the xxx is the component logging the information.  nblog.conf in the \netbackup directory will detail which xxx component is responsible for writing the logs (don't edit this file directly but you can 'review' it)

If you upgrade to 7.x, the logs are moved to the subfolders to make this easier to determine which component is writing.

View solution in original post

4 REPLIES 4

Omar_Villa
Level 6
Employee

What type of logs you are seeing? there are different ways to redirect logs, but will help to know what kind they are.

 

MKT
Level 5
Employee Accredited

51216-xxx logs are VxUL logs.  51216 is the NetBackup product and the xxx is the component logging the information.  nblog.conf in the \netbackup directory will detail which xxx component is responsible for writing the logs (don't edit this file directly but you can 'review' it)

If you upgrade to 7.x, the logs are moved to the subfolders to make this easier to determine which component is writing.

Learning_Everyd
Level 5

Here is one of them.

jcrowley
Level 2
Employee Certified

Unless you're collecting logs for a particular issue you can disable all VxUL Logging by running the following command from \NetBackup\Bin

From a command prompt:

vxlogcfg -a --prodid 51216 --orgid ALL -s DebugLevel=0 DiagnosticLevel=0

 

You can delete all that are not active by running the following:

 

vxlogmgr -d