Problem
DOCUMENTATION: How to configure Veritas NetBackup (tm) to write Unified and Legacy log files to a different directory
Solution
Manual:
Veritas NetBackup (tm) 6.0 Troubleshooting Guide for UNIX and Windows, Page: 75-76
Veritas NetBackup (tm) 6.5 Troubleshooting Guide for UNIX, Linux, and Windows, Page: 82-83
Veritas NetBackup (tm) 7.0 Troubleshooting Guide for UNIX, Linux, and Windows, Page: 85-86
Modification Type: Addition
Modification:
NetBackup 6.x introduced a new type of logging, referred to as unified logging. This style of logging is used by new NetBackup daemons, such as the Intelligent Resource Manager (IRM) and the Enterprise Media Manager (EMM) daemons. Unified logs are written to the /usr/openv/logs directory on UNIX systems or the <install_path>NetBackuplogs directory on Windows systems. An example of a log file that would be generated would be: 51216-111-990921226-060318-0000000000.log
By default, the maximum log file size in unified logging is 5120 KB. After a log file reaches 5120 KB, the file is closed and a new log file is opened. NetBackup will also keep 28 days of logging, by default. As such, the logs folder can quickly fill up and absorb all available drive space. In this condition it may be necessary to change the default log location to a volume or drive with more available disk space.
Note: This process does not affect legacy log files stored in the /usr/openv/netbackup/logs on UNIX systems or the<install_path>NetBackuplogs<process> directories on Windows systems. In legacy debug logging, each logging directory must be manually created for each process. For example, the bpsched process is logged in /usr/openv/netbackup/logs/bprd on UNIX or <install_path>NetBackuplogsprd on Windows.
Procedure to change the location where unified log files are written:
1. On a volume or drive with sufficient free space to store unified logging, it will be necessary to create a new directory in which to store the new log files.
Veritas NetBackup (tm) 6.0 Troubleshooting Guide for UNIX and Windows, Page: 75-76
Veritas NetBackup (tm) 6.5 Troubleshooting Guide for UNIX, Linux, and Windows, Page: 82-83
Veritas NetBackup (tm) 7.0 Troubleshooting Guide for UNIX, Linux, and Windows, Page: 85-86
Modification Type: Addition
Modification:
NetBackup 6.x introduced a new type of logging, referred to as unified logging. This style of logging is used by new NetBackup daemons, such as the Intelligent Resource Manager (IRM) and the Enterprise Media Manager (EMM) daemons. Unified logs are written to the /usr/openv/logs directory on UNIX systems or the <install_path>NetBackuplogs directory on Windows systems. An example of a log file that would be generated would be: 51216-111-990921226-060318-0000000000.log
By default, the maximum log file size in unified logging is 5120 KB. After a log file reaches 5120 KB, the file is closed and a new log file is opened. NetBackup will also keep 28 days of logging, by default. As such, the logs folder can quickly fill up and absorb all available drive space. In this condition it may be necessary to change the default log location to a volume or drive with more available disk space.
Note: This process does not affect legacy log files stored in the /usr/openv/netbackup/logs on UNIX systems or the<install_path>NetBackuplogs<process> directories on Windows systems. In legacy debug logging, each logging directory must be manually created for each process. For example, the bpsched process is logged in /usr/openv/netbackup/logs/bprd on UNIX or <install_path>NetBackuplogsprd on Windows.
Procedure to change the location where unified log files are written:
1. On a volume or drive with sufficient free space to store unified logging, it will be necessary to create a new directory in which to store the new log files.
On UNIX systems:
# mkdir <new_log_dir>
On Windows systems:
% mkdir <new_log_dir>
Where: <new_log_dir> is the name of the directory where the unified logs will be moved to, and new unified logs will be written to.
2. The NetBackup daemons will need to be stopped before making any changes to the default log directory. This should be done when there are no active jobs running. This will ensure no daemons are writing to existing log files when they are being moved. To shut down NetBackup:
On UNIX systems:
# /usr/openv/netbackup/bin/goodies/netbackup stop
On Windows systems:
% <install_path>NetBackupinpdown.exe
3. Move the existing unified logs to the new location. This will preserve existing unified log files. Once the log files have been moved, verify the files exist in the new path. Note: This will only move the *.log files related to unified logging. For Windows, it will not move any legacy process directories that have been created.
To move the log files,
On UNIX systems:
# mv /usr/openv/logs/*.log <new_log_dir>
# mv /usr/openv/logs/*.log <new_log_dir>
On Windows systems:
% move <install_path>NetBackuplogs*.log <new_log_dir>
To verify the logs have been successfully moved,
On Unix systems:
# ls <new_log_dir>
On Windows systems:
% dir <new_log_dir>
4. Set the new log directory location for NetBackup unified log originators.
The vxlogcfg command is used to set the default log directory for all NetBackup originators. It is also possible to configure log locations for specific originators. Refer to the Veritas NetBackup (tm) Troubleshooting Guide in the "Related Documents" section, found below, for additional details on these options.
On UNIX systems:
# /usr/openv/netbackup/bin/vxlogcfg -a -p 51216 -o Default -s "LogDirectory=<new_log_dir>"
For Windows systems:
% <install_path>NetBackupinvxlogcfg -a -p 51216 -o Default -s "LogDirectory=<new_log_dir>"
For Windows systems use the 8.3 format for LogDirectory=<new_log_dir> directory names. This is the format that any of the default values will use.
Example: "C:PROGRA~1VERITAS..." instead of "C:Program FilesVERITAS..".
5. Verify the settings in the nblog.conf file.
For NetBackup 7.0 the fundamental principles for how the LogDirectory are outlined below:
a) The Default.LogDirectory setting represents the base logging directory for unified log. On unix this is /usr/openv/logs. On windows it is <install path>NetBackuplogs.
b) Daemons will log to subdirectories under the base logging directory. These subdirectories are automatically created with the name defined in nblog.conf for each originator id.
For example, EMM has originator 111. The LogDirectory for EMM is set to "nbemm", with the following line in the nblog.conf file:
111.LogDirectory=nbemm
Thus, EMM will log to /usr/openv/logs/nbemm on Unix, and <install path>NetBackuplogs
bemm on Windows.
c) By convention, all originators LogDirectory settings will match the setting for OIDNames which will also match the daemon name.
d) If the user chooses to create a new base log directory on another drive or partition where more space exists for the logs, they need only create the base logging directory as described in this TN. Unified logging will automatically create the subdirectories.
The nblog.conf file will contain unified log settings for the Default.LogDirectory and may contain additional pointers for each NetBackup originator. This TechNote does not address all available resources for unified logging and is only concerned with moving the Default.LogDirectory resource.
Verify that the Default.LogDirectory now displays the correct path to the new log directory. At this time also check for any overrides that have been set for individual originators. It is not required to change other originators to match the default setting. This step just highlights what other directories are being used to write unified log files. Other Symantec products such as the NetBackup Operations Manager (NOM) will have different log directories set for it's own originators (146, 147, 148). By default, these log files are written to other directories.
On UNIX systems:
# grep LogDirectory /usr/openv/netbackup/nblog.conf
Default.LogDirectory=new_log_dir
146.LogDirectory=/var/VRTSnomweb/log/
147.LogDirectory=/var/VRTSnomweb/log/
148.LogDirectory=/opt/VRTSnom/logs/
For Windows systems:
Open <install_path>NetBackup
blog.conf and search for any LogDirectory entries to verify the settings.
6. Restart the NetBackup daemons for the changes to take effect. Once NetBackup is restarted it will begin writing unified log files in the new directory.
On UNIX systems:
# /usr/openv/netbackup/bin/goodies/netbackup start
On Windows systems:
% <install_path>VERITASNetBackupinpup.exe
7. Verify that vxlogview is able to process the log files in their new location.
The example below will display all the unified log entries that have been generated in the last five minutes.
On UNIX systems:
# cd /usr/openv/netbackup/bin
# ./vxlogview -p 51216 -t 00:05:00
# ./vxlogview -p 51216 -t 00:05:00
For Windows systems:
% cd install_pathNetBackupin
% vxlogview -p 51216 -t 00:05:00
Note: Unlike the files written in legacy logging, unified logging files cannot be easily read with a text editor. The unified logging files store messages in a codified format that needs to be interpreted with vxlogview. The vxlogview command must be used to assemble and display the complete log information correctly.
Procedure to change the location where the legacy log files are written:
NOTE: for either Unix or Windows systems, this procedure should be followed after stopping NetBackup daemons/services. Also, previously written log files will reside in their original location following this procedure. The logs may remain in this location, deleted, or moved to the new log location.
For Unix systems: The standard hard coded logs path Netbackup writes the logs to is /usr/openv/netbackup/logs, and it cannot be changed.
If /usr/openv is filling up, it is often desirable to change the log directory to a different file system.
Procedure to change the location where the legacy log files are written:
NOTE: for either Unix or Windows systems, this procedure should be followed after stopping NetBackup daemons/services. Also, previously written log files will reside in their original location following this procedure. The logs may remain in this location, deleted, or moved to the new log location.
For Unix systems: The standard hard coded logs path Netbackup writes the logs to is /usr/openv/netbackup/logs, and it cannot be changed.
If /usr/openv is filling up, it is often desirable to change the log directory to a different file system.
1. Create the new log directory
# mdkir -p /new_filesystem/netbackup/logs
2) Give the directory 755 permissions
# chmod 755 /new_filesystem/netbackup/logs
3) Navigate to /usr/openv/netbackup/ and rename the existing logs directory
# mv logs logs_old
4) Create the symbolic link to the new legacy log location
# ln -s /new_filesystem/netbackup/logs logs
5) Verify the link was created successfuly
# ls -l /usr/openv/netbackup/logs
lrwxrwxrwx 1 root root 25 Apr 6 14:31 logs -> /new_filesystem/netbackup/logs
6) Verify that legacy logs are being written to the new location. This can be done by creating commonly used log directories (such as bpcd, vnetd, bpbkar) under /new_filesystem/netbackup/logs, starting NetBackup, and running a test backup. Then inspect the log directories to ensure a new log file is created.
For Windows systems:
1. Edit the Log Directory registry key
- Open the registry by running regedit
- Navigate to HKLMSoftwareVeritasNetBackupCurrentVersion
- On the right pane double click on "Log Directory" and specify the path to the new log directory, e.g. E:NBULogs. The folder must already exist.
- On the right pane double click on "Log Directory" and specify the path to the new log directory, e.g. E:NBULogs. The folder must already exist.
The steps above will redirect where the client based logs will go, e.g. bpbkar, bpcd, inetd, etc. To have all the logs redirected to a new location, perform the following actions:
2. Add the following value within the registry to make sure all the (master and media process) log directories, as made by the batch file, are correctly written Within the VERITASNetBackupCurrentVersionPaths key, add a string value called "BP_LOGS". The value does not exist by default, so it will have to be created. Its value will be a string directory path. The following format must be deployed when entering this type of string value:
Actual path to the logs directory:
D:Logs
Path to enter into the string value:
D:${_PS.EN_US}Logs
2. Add the following value within the registry to make sure all the (master and media process) log directories, as made by the batch file, are correctly written Within the VERITASNetBackupCurrentVersionPaths key, add a string value called "BP_LOGS". The value does not exist by default, so it will have to be created. Its value will be a string directory path. The following format must be deployed when entering this type of string value:
Actual path to the logs directory:
D:Logs
Path to enter into the string value:
D:${_PS.EN_US}Logs
The new log directory will also have to be manually created in the new location. If NetBackup's mkdir.bat file (the batch file that creates all of the log directories) is used, it will have to be moved to the new location and executed there. Additionally, the ALTPATH directory within <Install_Path>
etbackuplogs should remain in the original location.
Once the Log Directory key is modified and NetBackup is restarted, legacy logs will be written to this location.
Once the Log Directory key is modified and NetBackup is restarted, legacy logs will be written to this location.
Note: Incorrect use of the Windows Registry Editor can have disastrous results on a server operating system. Great care should be taken when making changes to a Windows Registry. Registry modifications should only be carried out by persons experienced in the use of the Registry Editor application.