Veritas NetBackup™ Logging Reference Guide
- Using logs
- About logs
- About UNIX system logs
- About log retention in NetBackup
- About limiting the size of unified and legacy logs
- About unified logging
- Gathering unified logs for NetBackup
- Types of unified logging messages
- File name format for unified logging
- Originator IDs for the entities that use unified logging
- About changing the location of unified log files
- About rolling over unified log files
- About recycling unified log files
- About using the vxlogview command to view unified logs
- About query strings used with the vxlogview command
- Examples of using vxlogview to view unified logs
- Examples of using vxlogmgr to manage unified logs
- Examples of using vxlogcfg to configure unified logs
- About legacy logging
- UNIX client processes that use legacy logging
- PC client processes that use legacy logging
- File name format for legacy logging
- Directory names for legacy debug logs for servers
- Directory names for legacy debug logs for media and device management
- How to control the amount of information written to legacy logging files
- About limiting the size and the retention of legacy logs
- Configuring the legacy log rotation
- About global logging levels
- Setting retention limits for logs on clients
- Logging options with the Windows Event Viewer
- Troubleshooting error messages in the NetBackup Administration Console
- Backup process and logging
- Media and device processes and logging
- Restore process and logging
- Advanced Backup and Restore Features
- Storage logging
- NetBackup Deduplication logging
- OpenStorage Technology (OST) logging
- Snapshot technologies
- Locating logs
- acsssi logging
- bpbackup logging
- bpbkar logging
- bpbrm logging
- bpcd logging
- bpcompatd logging
- bpdbm logging
- bpjobd logging
- bprd logging
- bprestore logging
- bptm logging
- daemon logging
- ltid logging
- nbemm logging
- nbjm logging
- nbpem logging
- nbproxy logging
- nbrb logging
- NetBackup web services logging
- NetBackup web server certificate logging
- PBX logging
- reqlib logging
- robots logging
- tar logging
- txxd and txxcd logging
- vnetd logging
- Java-based administration console logging
- About the Java-based administration console logging
- Java-based administration console logging process flow
- Setting up a secure channel between the Java-based administration console and bpjava-*
- Setting up a secure channel between the Java-based administration console and either nbsl or nbvault
- Java-based administration console logging configuration on NetBackup servers and clients
- Java-based remote administration console logging on a Windows computer where NetBackup is not installed
- Configuring and gathering logs when troubleshooting Java GUI issues
- Undo logging
Java-based remote administration console logging on a Windows computer where NetBackup is not installed
If the NetBackup Remote Administration Console Installation (x64 only) option is used when installing, NetBackup is not installed on the host and the Java activity is not logged by default.
You must make changes to the setconf.bat file to ensure that Veritas Technical Support can successfully log the Java operations; that is, %nbjLogFileName%.
The following changes to the setconf.bat file are required as there is no active path set against NB_INSTALL_PATH on the target host. The procedure is as follows:
Make a copy of your existing
setconf.batfile (fileC:\Program Files\Veritas\java\setconf.bat) before you edit it.To edit the file, use Notepad or another text editor and scroll down to the following line:
SET HIDE_LOGGING_ASSISTANT=0 if "[%NB_INSTALL_PATH%]"=="[]" goto skip if NOT EXIST "%NB_INSTALL_PATH%" goto skip @REM generate a unique file name ... for /f "tokens=5-8 delims=:. " %%a in ('echo.^|time') do set thh=%%a&set tmm=%%b&set tss=%%c&set ths=%%dChange the previous lines to the following:
SET HIDE_LOGGING_ASSISTANT=0 @REM if "[%NB_INSTALL_PATH%]"=="[]" goto skip @REM if NOT EXIST "%NB_INSTALL_PATH%" goto skip @REM generate a unique file name ... for /f "tokens=5-8 delims=:. " %%a in ('echo.^|time') do set thh=%%a&set tmm=%%b&set tss=%%c&set ths=%%dScroll down to the following lines:
set nbjLogFileName=jbp.%dyyyy%%dmm%%ddd%%thh%%tmm%%tss%%ths%.log set logFile=%NB_INSTALL_PATH%\logs\user_ops\nbjlogs\%nbjLogFileName% :skip
Change these lines to the following:
set nbjLogFileName=jbp.%dyyyy%%dmm%%ddd%%thh%%tmm%%tss%%ths%.log set logFile=%INSTALL_PATH%\logs\user_ops\nbjlogs\%nbjLogFileName% :skip
Save the new
setconf.batfile.To manually create the path directory, do the following:
%INSTALL_PATH%\logs\user_ops\nbjlogs\
That is, the file
C:\Program Files\Veritas\java\logs\user_ops\nbjlogs.Reopen the Java-based administration console and capture the Java logs on the host:
C:\Program Files\Veritas\java\logs\user_ops\nbjlogs\%nbjLogFileName%