NetBackup™ Logging Reference Guide
- Using logs
- About logging
- Logging levels
- Log retention and log size
- Changing the logging levels
- 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
- 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
- Limit the size and retention of legacy logs
- Accessibility of the legacy logs
- Setting retention limits for logs on clients
- UNIX logging with syslogd
- Logging options with the Windows Event Viewer
- 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
- Storage lifecycle policy (SLP) and Auto Image Replication (A.I.R.) logging
- NetBackup secure communication logging
- About NetBackup secure communication logging
- Tomcat logging
- NetBackup web services logging
- Command-line logging
- NetBackup cURL logging
- Java logging
- Embeddable Authentication Client (EAT) logging
- Authentication Services (AT) logging
- vssat logging
- NetBackup proxy helper logging
- NetBackup proxy tunnel logging
- PBX logging
- Sending secure communication logs to Veritas Technical Support
- Snapshot technologies
- Locating logs
- Overview of NetBackup log locations and processes
- acsssi logging
- bpbackup logging
- bpbkar logging
- bpbrm logging
- bpcd logging
- bpcompatd logging
- bpdbm logging
- bpjobd logging
- bprd logging
- bprestore logging
- bptestnetconn logging
- bptm logging
- daemon logging
- ltid logging
- nbemm logging
- nbjm logging
- nbpem logging
- nbproxy logging
- nbrb logging
- NetBackup Vault logging
- NetBackup web services logging
- NetBackup web server certificate logging
- PBX logging
- reqlib logging
- Robots logging
- tar logging
- txxd and txxcd logging
- vnetd logging
- NetBackup Administration Console logging
- NetBackup Administration Console logging process flow
- Enabling detailed debug logging for the NetBackup Administration Console
- Setting up a secure channel between the NetBackup Administration Console and bpjava-*
- Setting up a secure channel between the NetBackup Administration Console and either nbsl or nbvault
- NetBackup Administration Console logging configuration on NetBackup servers and clients
- Logging Java operations for the NetBackup Remote Administration Console
- Configuring and gathering logs when troubleshooting NetBackup Administration Console issues
- Undo logging
- Using the Logging Assistant
PBX logging
The Private Branch Exchange (PBX) logs are located at the following location on any master, media or client server:
UNIX: /opt/VRTSpbx/log
Windows: C:\Program Files (x86)\VERITAS\VxPBX\log
The PBX log files can be critical when you troubleshoot secure communication issues. In these cases, you may have to increase the size and the number of log files as the defaults are to retain 5 log files at 1MG each. To increase the size of the log files to 50000 KB and number of log files to 20, use the vxlogcfg command, as follows:
Windows (in HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Veritas\VxICS\logcfg\103):
C:\Program Files (x86)\VERITAS\VxPBX\bin\vxlogcfg - a - p 50936 - s "MaxLogFileSizeKB=50000" - o 103 C:\Program Files (x86)\VERITAS\VxPBX\bin\vxlogcfg - a - p 50936 - s "NumberOfLogFiles=20" - o 103
This lets you capture 20 log files at 50 mg each.
UNIX:
Use the vxlogcfg command to increase the size of the log files to 51200 KB and the number of log files to 10 as follows:
UNIX (in /etc/vx/VxICS/icsul.conf):
/opt/VRTSpbx/bin/vxlogcfg - a - p 50936 - s "MaxLogFileSizeKB=51200" - o 103 /opt/VRTSpbx/bin/vxlogcfg - a - p 50936 - s "NumberOfLogFiles=10" - o 103
Change directories using the
cd /opt/VRTSpbx/logcommand. Verify that the log files are increasing in size to more than 1 mg (it should read the change within 1 minute).To verify the PBX log settings, the configuration file can be viewed as follows:
Change your directory to
/etc/vx/VxICS.Use the
cat icsul.confcommand and verify that the changes were made.
See the following example:
cat icsul.conf ############################################### # Caution! Do not update/modify file by hand. # Use vxlogcfg tool to update/modify this file ############################################### 103.DebugLevel=6 103.AppMsgLogging=ON 103.LogToOslog=false 103.LogDirectory=/var/log/VRTSpbx/ 103.L10nResourceDir=/opt/VRTSpbx/resources 103.L10nLib=/optVRTSpbx/lib/libvxexticu.so.3 103.L10nResource=VxPBX 103.MaxLogFileSizeKB=51200 103.RolloverMode=FileSize 103.NumberOfLogFiles=10 103.LogRecycle=true